Conversation
Add --ignore-packages shells flag to prevent multi-semantic-release from treating the shells/ directory as a package to be released. The shells/ directory contains devbox environment configurations (devbox.json files), not npm packages, so it should be excluded from the release process. Multi-semantic-release aggressively scans all directories for potential packages, not just those in the workspaces field. When it encounters shells/, it expects a package.json and fails with ENOENT. Changes: - Add --ignore-packages shells to release script in package.json - Add --ignore-packages shells to both release and release-dry-run scripts in shells/devbox-fast.json This fixes the release dry-run workflow failure. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
MichaelGHSeg
approved these changes
Mar 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add --ignore-packages shells flag to prevent multi-semantic-release from treating the shells/ directory as a package to be released.
The shells/ directory contains devbox environment configurations (devbox.json files), not npm packages, so it should be excluded from the release process.
Multi-semantic-release aggressively scans all directories for potential packages, not just those in the workspaces field. When it encounters shells/, it expects a package.json and fails with ENOENT.
Changes:
This fixes the release dry-run workflow failure.