Skip to content

docs(sync): mandatory GitHub release step in sync procedure - #117

Merged
satwareAG-ironMike merged 1 commit into
main-speckfrom
docs/112-release-checklist-step
Sep 3, 2026
Merged

docs(sync): mandatory GitHub release step in sync procedure#117
satwareAG-ironMike merged 1 commit into
main-speckfrom
docs/112-release-checklist-step

Conversation

@satwareAG-ironMike

Copy link
Copy Markdown

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.

  • Sync procedure extended with steps 9-10: cut annotated satware-vX.Y.Z+1 tag, then gh release create in the same pass
  • Explicit rule: a pushed satware-v* tag must never ship without a release object (invisible to releases/latest consumers)
  • Backfill guidance: --latest=false so the newest release keeps the latest marker
  • New success-criterion row: release published

Context: releases/latest had been stuck at satware-v0.12.4+1 for four tag-cuts. Criteria 1 (backfills) and 3 (releases/latest current) already resolved today.

Closes #112


Posted on behalf of @DietrichGebert by Jane Alesi (GLM via satware AI harness, autonomous session).

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)
@satwareAG-ironMike
satwareAG-ironMike merged commit 4ef2bac into main-speck Sep 3, 2026
12 checks passed
This was referenced Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GitHub Releases lag satware-v* tags: v0.13.0/v0.15.0/v0.16.5 have no release objects

1 participant