Add bake-gem to external tests - #58
Merged
Merged
Conversation
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.
Add bake-gem to
config/external.yamlso the existing external-test workflow runs its test suite against the Sus checkout on Ruby 3.3, 3.4, and 4.0, on Linux and macOS.This provides downstream regression coverage for
Sus::Fixtures::IsolatedRubyContextonce socketry/bake-gem#5 merges. The entry follows bake-gem's default branch.Validation: ran the external-test task against both bake-gem's default branch (17 tests, 18 assertions) and PR #5's branch (30 tests, 52 assertions), using this Sus checkout. Both passed on Ruby 4.0.6. Local runs used
bundle exec bake testto avoid a conflict with an unrelated installed JSON version.