Repository navigation
Record the v0.2.0 release checks and rollback drill - #64
Merged
Merged
Conversation
release.yml passed on the v0.2.0 tag and pushed ghcr.io/professor3333/triggermap@sha256:cc1578f9...76ce (publicly pullable); the attached CRF bundle is byte-identical to v0.1.0's. The local rollback drill v0.1.0 -> v0.2.0 -> v0.1.0 verified every step and kept reviews (51 s).
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.
Post-release record for v0.2.0: image digest
sha256:cc1578f9…76ce(release.yml passed: tests, build, smoke test, push; anonymous pull OK), CRF asset identical to v0.1.0, and the local rollback drill v0.1.0 → v0.2.0 → v0.1.0 (every step verified, reviews kept, 51 s). Updatesdocs/deployment.mdanddocs/release_notes/v0.2.0.md; the GitHub release body matches.