Repository navigation
chore(release): CI release design B (release kit) - #4
Merged
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.
The release kit for the CI-built release (design B), revision
4e6cf28: the kit opencode-gws v0.0.1 was released with (9f3168a, gws PR #34), plus gws PR #36, which only builds the kit test's path fixtures at run time so the family'scheck-forbiddenpasses. A release no longer needs anyone's laptop or signing key.What it does:
masterwith the sha CI passed (and, for a native plugin, thenative.ymlrun id):gh workflow run release.yml --ref master -f sha=<sha> [-f native_run=<id>]. The tag-push trigger is gone.master, a sha that is not master's head, no greenci.ymlpush run on it, a version or CHANGELOG not ready, a release that does not move forward from the published Releases, a leftoverrelease/v<version>branch, a wrong native run or manifest.contents: readonly; jobs that use the API run only the kit's scripts on a fresh checkout, after checking thatscripts/and.github/are the parent's.release/v<version>branch, made throughcreateCommitOnBranchwith the workflow token (authorgithub-actions[bot], verified); its tree is checked against the files.releaseapproval: identity, one parent on master, exactpackage.json, allowed paths, a byte-for-byte independent rebuild,plugin addon every tested host, the pack stage, attested native files,SHA256SUMSand notes, shown in the run summary with the sha256 ofSHA256SUMS.SHA256SUMShas the approved digest (and native files match the release commit's manifest), then creates the tag and the Release.Also:
scripts/check-icons.mjsrevision 2 (backward compatible; the vendor-mark mode is opt-in).This PR changes only kit files: the release scripts and their tests,
.github/workflows/release.yml, CONTRIBUTING's Releasing section and thetest:kitscript line. It passed two independent reviews and a scratch-repo rehearsal, and shipped gws v0.0.1.Repository setting (the lead does this, not this PR): the
releaseenvironment's deployment policy moves from tagv*to branchmaster.