Conversation
Remove E2E workflow files and simplify publish workflow to only use the devbox-fast shell environment. This streamlines CI until the new devbox plugins for android/ios/nodejs are approved for release. Changes: - Delete .github/workflows/ci-e2e-full.yml - Delete .github/workflows/ci-e2e-latest.yml - Update publish.yml to remove e2e-ios and e2e-android jobs - Update publish job to only depend on fast-checks - Update devbox-fast.json to include update-apps script - Keep ci-fast.yml unchanged (already using devbox-fast) The ci-fast shell now handles all CI tasks: - Building packages - Publishing to npm - Linting with treefmt - Basic Node.js/Yarn tooling Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Update packages to resolve security vulnerabilities and deprecation warnings identified by yarn npm audit. Package updates: - @babel/runtime: ^7.23.2 → ^7.26.10 (fixes moderate severity RegExp inefficiency vulnerability GHSA-968p-4wvh-cqc8) - eslint: ^8.56.0 → ^8.57.1 (latest v8 release, addresses deprecation warning) Remaining deprecation warnings (non-security): - eslint v8 is EOL (will migrate to v9 separately if needed) - metro-react-native-babel-preset deprecation (React Native ecosystem) All build and lint checks pass after these updates. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Add optional dry-run mode to the publish workflow for testing releases without actually publishing to npm or creating GitHub releases. Changes: - Add 'dry-run' boolean input to publish workflow (default: false) - Add conditional logic to run release-dry-run script when enabled - Add 'release-dry-run' script to devbox-fast.json that runs multi-semantic-release with --dry-run flag - Existing 'release' script continues to work for production releases Usage: - Production release: trigger workflow with dry-run unchecked (default) - Test release: trigger workflow with dry-run checked Both modes use the devbox-fast environment for consistency. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Split single publish workflow into two distinct workflows to prevent accidental production releases. Users now explicitly choose which workflow to run from the Actions UI. Changes: - Create release-dry-run.yml: Safe testing workflow - No secrets required - Read-only permissions - Runs multi-semantic-release with --dry-run flag - Shows what would be released without publishing - Create release-production.yml: Production release workflow - Requires GH_TOKEN and NPM_TOKEN secrets - Write permissions for GitHub releases - Publishes to npm and creates GitHub releases - Uses "Publish" environment protection Benefits: - No risk of forgetting to check a dry-run flag - Clear intent when triggering workflows - Separate workflows appear as distinct options in Actions UI - Production workflow can use environment protection rules Both workflows use devbox-fast environment for consistency. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
wenxi-zeng
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.
Uh oh!
There was an error while loading. Please reload this page.