Repository navigation
chore(release): v2.1.5 - #52
Merged
Merged
Conversation
Consumers pin the devkit submodule to a release TAG, and the BDD suite config (which is where the surviving retain-on-failure default lived) ships inside that submodule. So the trace fix only reaches the fleet once this tag exists — the workflow half flows immediately via @main, the config half does not.
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
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.
Changelog-only. Cuts the release that carries the DEC-073 completion (#51).
Consumers pin the devkit submodule to a release tag, and the BDD suite config — where the surviving
retain-on-failuredefault lived — ships inside that submodule. So the trace fix only reaches the fleet once this tag exists. The workflow half flows immediately via@main; the config half does not.Going through a PR rather than pushing to
maindirectly:enforce_adminsis false here, so the previous release commit bypassed the PR requirement. That shouldn't be the habit.