release: v0.6.0 - #426
Open
github-actions[bot] wants to merge 2 commits into
Open
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.
Machine-generated release PR for v0.6.0, base commit A =
8195a40ee0aa982d3002e783ad34ab6221f90b89,opened by release-build run 32661789098. Process:
docs/ai/design/release-process.md.Two machine-written commits:
d18fe5967a7407035fd17909abf14dc60ef125a7-- commit B, the tag target: the binary-default releasePackage.swift(asset URL + checksum of the built XCFramework) plusrelease-manifest.json, the provenance record that release-publishre-verifies at tag time. Review it here: 8195a40...d18fe59
Package.swiftto A's copy verbatim, so every tipof
mainstays a source-only package. The PR's net diff isrelease-manifest.jsononly.To ship v0.6.0:
rebase. Only a true merge preserves B in main's ancestry; publish
refuses the tag otherwise. If it was squashed or rebased anyway, recover
with a history-only merge:
git fetch origin && git checkout main && git pull && git merge -s ours origin/release-prep/v0.6.0 && git push origin main,then push the tag.
the only trigger for publishing:
Do not tag before merging: publish requires B to be an ancestor of main.
release-publish then re-verifies everything in
release-manifest.json(checks 1-6) and publishes the GitHub Release with the already-built,
already-checksummed artifacts. No rebuild.
Notes:
whose events GitHub never lets trigger other workflows. CI validated
A on its own PR, and release-build built and checksummed A.
retention); after that, re-dispatch release-build for a fresh B.
from main and from the tag.