Invoke release tasks directly with Bake - #6
Merged
Merged
Conversation
samuel-williams-shopify
changed the title
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
1 participant
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.
Release subprocesses logged roughly 13 KB per invocation because the command contained an embedded Ruby program and copied dependency paths.
Invoke
bakedirectly withchdir:set to the worktree. This removes the generated Ruby bootstrap, manual task registry, copied load paths, and environment overrides. The child uses Bake's normal executable and inherits the bundle environment and coverage hooks. Task results continue to use Bake's JSON output.The concise command uses the existing info-level logging. Add a regression test for the direct invocation and its working directory.
Validation: 41 tests / 95 assertions pass with parallel execution and a fresh coverage run on Ruby 4.0.7, including building the committed version when the parent has an older version loaded, release regeneration, signing, and publication against a local Git remote. RuboCop passes, and the changed executable line is covered. Overall coverage is 90.52%; the existing global 100% coverage gate is unchanged.