docs(sync): mandatory GitHub release step in sync procedure - #117
Merged
Conversation
Every pushed satware-v* tag must ship with a GitHub release object in the same pass as the tag-cut (#112). Tags without releases are invisible to releases/latest consumers. Backfills use --latest=false to preserve the newest release marker. Assisted-by: Jane Alesi (GLM, autonomous)
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.
Summary
Adds the mandatory GitHub-release step to the upstream sync procedure (
specs/upstream-release-sync-strategy/spec.md), closing acceptance criterion 2 of #112.satware-vX.Y.Z+1tag, thengh release createin the same passsatware-v*tag must never ship without a release object (invisible toreleases/latestconsumers)--latest=falseso the newest release keeps thelatestmarkerContext:
releases/latesthad been stuck atsatware-v0.12.4+1for four tag-cuts. Criteria 1 (backfills) and 3 (releases/latestcurrent) already resolved today.Closes #112
Posted on behalf of @DietrichGebert by Jane Alesi (GLM via satware AI harness, autonomous session).