noop change to buildroot to create a new snapshot - #170
Merged
Jakob-Naucke merged 1 commit intoSep 2, 2026
Conversation
Signed-off-by: Jakob Naucke <jnaucke@redhat.com>
iroykaufman
approved these changes
Sep 2, 2026
Contributor
Author
|
thanks @iroykaufman -- there is a snapshot on the merge commit of this PR so it really was Konflux bugging out |
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
2 participants
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.
We need a buildroot with Rust 1.92, and it must be a released one. Usually, a release can be created from a snapshot based on a merge commit based on this repo, but no such snapshot was created for the merge of #169 even though one was created for #165 (merged before) and #169 (merged after, but did not touch buildroot, thus no buildroot release can be created from it).
Retry to trigger snapshot creation by making a no-op change to buildroot (newline at the end of file).
If the absence of this snapshot turns out to be explained by something else, I'm really sorry for the noise to reviewers, but right now this is what I'd most rather try.