Add safe upstream release sync for Strata - #289
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
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.
What this does
Adds safe upstream-release syncing for Strata without leaving its embedded build commit stuck on the original v0.8.0 SHA.
vX.Y.ZGitHub releasesSTRATA_BUILD_COMMITfrom the pinned archive during the buildThe recipe moves from
0.8.0-1to0.8.0-2because the build inputs changed. A future version bump will resetpkgrelto 1 normally.Current release
v0.8.1 is the newest release, but it is still inside the 24-hour quarantine. This PR deliberately does not bypass that window. Once it clears, the scheduled sync will open the normal version-bump PR.
I tested both paths: scheduled mode leaves v0.8.1 alone today, while an explicit bypass updates a disposable checkout to v0.8.1 with the independently reproduced SHA-256 and exact tag commit.
Validation
61b4b0bc74a5b8ca262c7c080e9fea57bba65ff5pkgrel=1, and source SHA-256dca3b6af063f5d49257d27b61be1fa2dfffb1d9998c295382e564ce8e995de71a2ebf1b820acacbd9b55ffe0e0f204175a613104