Repository navigation
Conversation
flux-plunger records the revision it is about to reclaim in its processed-version annotation before it deletes that storage Secret, so a write that fails never lets a later pass delete the next revision. The recovery diagram still showed the Secret deleted first. Assisted-by: LLM Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
scooby87
marked this pull request as ready for review
October 15, 2026 08:06
scooby87
requested review from
Andrei Kvapil (kvaps),
Timofei Larkin (lllamnyp),
myasnikovdaniil and
Timur Tukaev (tym83)
as code owners
October 15, 2026 08:07
This branch has not been deployed
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.
Since cozystack/cozystack#4293, flux-plunger records the revision it is about to reclaim in its processed-version annotation before it deletes that storage Secret, so a write that fails never lets a later pass delete the next revision. The recovery diagram in the trunk's concepts guide still shows the earlier order; this swaps the two steps.
Do not merge before v1.7.0 is released and
next/is re-initialized. cozystack/cozystack#4293 is not part of release-1.7, so this order is wrong for v1.7, andmake release-nextwould copy it intov1.7/;make init-nextwould then rebuildnext/fromv1.7/. Rebase onto the re-initializednext/and merge after that.The chart README carries the same correction in cozystack/cozystack#4914.