chore(eyrie): bump to v0.2.2 (deployment-retry #105) - #171
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.
Follow-up to #170 (audit remediation).
The audit-retry PR #170 was squash-merged to main with the eyrie submodule
pinned to the last published pseudo-version (v0.1.4-...026bfdd) so that the
submodule/module parity CI gate stays green. This commit advances the pin to
eyrie v0.2.2 (gitlink ed62022), which is the first tagged release
containing the deployment-retry no-repeat fix (eyrie #105).
go.sum / go.work already at v0.2.2 (from the earlier branch); this PR aligns
the gitlink + go.mod require line to the same v0.2.2 tag.
Verified locally: submodule/module parity OK, go build./..., go vet clean, and
internal/engine + internal/bench tests pass.
Blocks on eyrie having published v0.2.2 (now released). After merge the
deploy-retry fix is in-tree and ready to consume.