BEAR-120 Prepare ThreadBear v3.0.2 release - #127
Merged
Conversation
Owner
Author
|
@Mergifyio queue |
Contributor
Merge Queue Status🛑 Queue command has been cancelled |
Contributor
Merge Queue Status
This pull request spent 54 seconds in the queue, including 7 seconds running CI. Required conditions to merge
|
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
Unreleasedsectionv3.0.2 - 2026-08-13v3.0.2release tagThis is intentionally a changelog-only release-preparation diff. Product code is unchanged from protected PR #126.
Verification
python3 scripts/validate-experiments.pygit diff --checkgo test -count=1 ./...go test -race -count=1 ./...go vet ./...3.0.2THREADBEAR_SMOKE_CANDIDATE=... scripts/release-smoke.sh v3.0.2ShipCandidate hashes before the changelog-only commit:
5f05b9f872ca101f545feaca8df399d8752342fe0c7f7365e3b25da16ad0f8648647bc1ca5518dc157da5a95e248f31a22f033b9337425b5c6fffc6eab1f5a55After merge, the release tag will be created only on the exact protected merge commit. Published workflow assets, checksums, manifest, and hosted smoke must pass before BEARWEB-22 updates its immutable locks.
Linear: BEAR-120