Prepare v0.3.0 release - #214
Merged
Merged
Conversation
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
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
1 participant
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.
Release
Prepare
github-deliveryv0.3.0 from the current protectedmainlineage.package.jsonfrom0.2.0to0.3.0.0.3.0changelog section for the watchdog activation work from PR Configure Codex watchdog on install and add protected streaming launcher #213.Unreleasedsection untouched because those entries are not part of the source diff fromv0.2.0to this release candidate.After this release-prep change lands, tag the resulting protected-main commit as
v0.3.0. The existing Release workflow will rebuild and verify the tagged source, run the repository checks, generate deterministic archives/checksums/SBOM/release notes, attest the release subjects, and publish through the protectedreleaseenvironment.