-
Notifications
You must be signed in to change notification settings - Fork 0
fix: Resolve CI/CD errors and warnings on Windows and Release jobs #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Adding CLAUDE.md with task information for AI processing. This file will be removed when the task is complete. Issue: #49
This commit addresses three distinct CI/CD issues:
1. **Release Job Failure (ENOENT error)**
- Added `--working-dir` option support to all release scripts
- Scripts now properly change to the specified directory before
reading package.json or other files
- Affected: version-and-commit.mjs, publish-to-npm.mjs,
create-manual-changeset.mjs, instant-version-bump.mjs
2. **Windows Docker Tests Failure**
- Added `canRunLinuxDockerImages()` function to isolation.js
- Properly detects if Linux containers can run on Windows
- Tests now skip gracefully when Docker is in Windows containers mode
- Affected: isolation.js, isolation.test.js, isolation-cleanup.test.js,
docker-autoremove.test.js
3. **Windows CLI Test Timeout**
- Increased CLI operation timeout to 30s on Windows (10s on other platforms)
- Added better error handling for killed processes
- First CLI invocation on Windows CI has cold-start latency
- Affected: cli.test.js
Case study documentation added to docs/case-studies/issue-49/
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
CI Status UpdateJavaScript Workflow ✅All JavaScript CI checks are passing:
Rust Workflow
|
This reverts commit 59e0f88.
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
Now working session is ended, feel free to review and add any feedback on the solution draft. |
|
All preexisting issues must be solved, that was original requirement. |
|
🤖 AI Work Session Started Starting automated work session at 2026-01-05T22:44:26.407Z The PR has been converted to draft mode while work is in progress. This comment marks the beginning of an AI work session. Please wait working session to finish, and provide your feedback. |
The ExecutionRecord::with_options function signature was changed to take only an ExecutionRecordOptions struct parameter (which contains the command field), but the integration test was still passing the command as a separate first argument. Updated the test to pass command inside ExecutionRecordOptions struct instead of as a separate argument. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
Now working session is ended, feel free to review and add any feedback on the solution draft. |
Summary
This PR resolves all CI/CD errors and warnings found in run #20684540679.
Issues Fixed
Release Job Failure -
ENOENT: no such file or directory, open './package.json'--working-diroption support to all release scriptsWindows Docker Tests Failure -
no matching manifest for windows/amd64canRunLinuxDockerImages()function to properly detect Linux container supportWindows CLI Test Timeout -
null !== 0(process killed due to timeout)Rust Integration Test Failure -
error[E0061]: this function takes 1 argument but 2 arguments were suppliedExecutionRecord::with_options()API call in integration testsExecutionRecordOptionsstruct instead of as separate argumentFiles Changed
scripts/version-and-commit.mjs,scripts/publish-to-npm.mjs,scripts/create-manual-changeset.mjs,scripts/instant-version-bump.mjsjs/src/lib/isolation.jsjs/test/cli.test.js,js/test/isolation.test.js,js/test/isolation-cleanup.test.js,js/test/docker-autoremove.test.js,rust/tests/integration_test.rsdocs/case-studies/issue-49/README.mdTest Plan
Case Study
A detailed case study has been added to
docs/case-studies/issue-49/with:Fixes #49
🤖 Generated with Claude Code