deploy: pin rollopsd manifest to v0.28.0 - #91
Merged
Conversation
The daemon was rolled to v0.28.0 (pull-request writeback) live via kubectl to unblock protected-branch deploys, leaving the manifest pinned to v0.27.0. That is drift: re-applying rollopsd.yaml would silently downgrade the daemon and lose PR-mode. Bring the source of truth in line with what runs. Claude-Session: https://claude.ai/code/session_012qFD1UhQT9tiKkMsPAskK7
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.
The daemon was rolled to v0.28.0 live (kubectl) to unblock protected-branch deploys; the manifest still pinned v0.27.0. Re-applying it would silently downgrade rollopsd and lose PR-mode. This makes git match the running cluster.
https://claude.ai/code/session_012qFD1UhQT9tiKkMsPAskK7