You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prepare v0.10.1, a documentation and test-infrastructure maintenance release, following RELEASE.md and the previous release PR #374. Main was verified green at 9d1581e033dabc29f7e76b4c213c13ccd99c298f before preparation:
Preparation only: no tag or GitHub release has been created. Do not merge/tag until the remaining UNVERIFIED secret-scanning section is checked or resolved by a maintainer under RELEASE.md. Notes are dated November 17, 2026; refresh that date if the actual release is later.
Changes
The audited range is v0.10.0..9d1581e, 14 commits. It contains no library source changes. Metadata-by-name lookup and the in-process simulator were already released and are not presented as new. This is not a new library-feature or runtime-bug-fix release.
Batch six accurately scoped entries with pinned changie v1.24.0. Use explicit batch v0.10.1, since the changed test/docs entries do not justify a minor SDK release.
Generate .changes/v0.10.1.md and CHANGELOG.md.
Let changie set base.DefaultUserAgent to blazer/0.10.1 and the bin/b2keys/go.mod blazer requirement to v0.10.1.
Update SECURITY.md to the supported 0.10.x line and add its maintenance to the release checklist. Root go.mod, dependencies, library behavior and published v0.10.0 notes remain unchanged.
This is a documentation and test-infrastructure maintenance release. No new SDK APIs or library runtime fixes are introduced; library source is unchanged from v0.10.0 apart from the standard release-version metadata.
The integration and Object Lock test suites honor B2_ENDPOINT on every client constructor, including low-level authorizations and scoped-key clients. TestUnknownCA uses B2_ENDPOINT_TLS, or an HTTPS B2_ENDPOINT, and skips with a reason when only plain HTTP is available. With the variables unset the existing integration-test endpoints are unchanged; this is test configuration only (test(integration): apply B2_ENDPOINT on all integration and lock clients #297).
Key-expiration wire tests now use JSON null for absent expiration timestamps and check both zero-time and set expiration results. This strengthens coverage of the existing Expires contract without changing key expiration behavior (fix: correct v0.10.0 upgrade guide count and key-expiration fixtures #392).
go run github.com/miniscruff/changie@v1.24.0 batch v0.10.1 --dry-run, batch, and merge completed. All generated version strings and the compare link use v0.10.1.
make ciPASS with B2_APPLICATION_KEY_ID, B2_APPLICATION_KEY, B2_ACCOUNT_ID, B2_ACCOUNT_KEY, B2_ENDPOINT, and B2_ENDPOINT_TLS unset: build, vet, formatting, tidy/verify, lint, race tests, b2keys, cross-compiles, changelog and script checks.
The committed make changelog-checkPASS.
Review follow-up 7c8f21f: go test ./..., go vet ./..., make changelog-check, and make ciPASS with B2 credentials and endpoints unset. The 0.10.1 note matches its changelog section; the published 0.10.0 section is unchanged.
Release-file scope, generated-note equality, unchanged root module and historical notes, and git diff --checkPASS.
Fresh-context static code/security/release-note review found no issues: verified all 14 commits, both catalog counts, version metadata, scope and historical-note preservation. It did not independently rerun tests or scanners; the executed evidence is recorded here.
No new test was needed for generated release notes/version metadata. No live B2 or simulator scenarios were rerun on the candidate: the underlying test/scenario code is unchanged by this PR, and main's live run is linked above. Local credential-free make ci passed.
Local CI output
GOTOOLCHAIN=go1.27.4 make ci: exit 0. Tail:
? github.com/Backblaze/blazer/internal/bin/cleanup [no test files]
ok github.com/Backblaze/blazer/internal/blog 3.480s
ok github.com/Backblaze/blazer/internal/retry 3.255s
ok github.com/Backblaze/blazer/x/b2sim 2.351s
ok github.com/Backblaze/blazer/x/consistent 3.826s
ok github.com/Backblaze/blazer/x/transport 3.364s
ok github.com/Backblaze/blazer/x/window 3.928s
cd bin/b2keys && go build ./... && go test ./...
? github.com/Backblaze/blazer/bin/b2keys [no test files]
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build ./...
CGO_ENABLED=0 GOOS=linux GOARCH=386 go build ./...
CGO_ENABLED=0 GOOS=linux GOARCH=arm go build ./...
CGO_ENABLED=0 GOOS=darwin GOARCH=arm64 go build ./...
CGO_ENABLED=0 GOOS=windows GOARCH=amd64 go build ./...
for t in scripts/*_test.sh; do "$t" || exit 1; done
ok comments on the workflow's own issue
ok ignores an issue with the same title opened by someone else
ok ignores a longer title that contains the phrase
ok picks the oldest matching issue
ok opens an issue when none exists
ok prints the summary to the log
ok writes the summary file too
ok prints the per-package result
ok prints the output of a failed test
ok prints only failed tests' output
ok prints the timeout reason of a cut-off test
ok skips finished tests in a failed package
ok keeps the error line after long failure output
ok keeps the last lines of long failure output
ok says how many lines were omitted
ok keeps the timeout reason above a long stack trace
ok keeps a timeout reason that follows 150 progress lines
ok keeps the failure of the first of three failing tests
ok keeps the failure of the quiet test between two noisy ones
ok keeps the failure of the last of three failing tests
Release gate
GOTOOLCHAIN=go1.27.4 make release-check: exit 0 conditional on the UNVERIFIED section, not unconditional release clearance. Code scanning, patched Dependabot findings, triage/draft advisories and reachable vulnerabilities were clear. Secret scanning returned 404 and remains a manual maintainer action. No advisory IDs or unpublished findings are disclosed.
scripts/release-check.sh
== Code scanning (CodeQL security and quality) on the default branch
none open
== Dependabot alerts
none with a patched version
== Secret scanning
UNVERIFIED: cannot read repos/Backblaze/blazer/secret-scanning/alerts?state=open&per_page=100 ({"message":"Not Found","documentation_url":"https://docs.github.com/rest/secret-scanning/secret-scanning#list-secret-scanning-alerts-for-a-repository","status":"404"}gh: Not Found (HTTP 404))
== Repository security advisories in triage or draft
none in triage or draft
== govulncheck (reachable known vulnerabilities)
.: no vulnerabilities found
bin/b2keys: no vulnerabilities found
UNVERIFIED sections above: check them on https://github.com/Backblaze/blazer/security before releasing.
Clear to release once the unverified sections are checked by hand.
Maintainer handoff
A human code owner must review the release paths and resolve the remaining gate qualification. After approval and merge, follow RELEASE.md to tag the release PR's merge commit and publish from .changes/v0.10.1.md. Those actions are deliberately not performed here. GitHub CI will run on this PR; no merge or release approval is implied by local checks.
Prepare a documentation and test-infrastructure maintenance release from the fourteen commits after v0.10.0. Record the upgrade-guide correction, strengthened repository-owned contract checks, key-expiration fixtures and retargetable integration suite without presenting existing SDK functionality as new.
Regenerate the changelog and the standard user-agent and b2keys version metadata with changie v1.24.0. No tag or GitHub release is created. Release clearance remains conditional on the unverified secret-scanning check.
Closes#423
No actionable comments were generated in the recent review.
Walkthrough
The PR adds v0.10.1 release notes and changelog entries describing test-infrastructure updates and documentation corrections. It updates DefaultUserAgent and the bin/b2keys module requirement to v0.10.1. The changes do not add SDK APIs or library runtime fixes.
Merge Risk: Minimal · up to 69584
This release-preparation change updates version metadata and documentation, with no library behavior changes. No merge-blocking risk was found; the pending code-owner approvals and the manual secret-scan check remain normal release steps.
Pre-merge checks: 4
Check name
Status
Explanation
Title check
The title "Version 0.10.1" names the release version. The changeset prepares v0.10.1: it adds the release notes, updates CHANGELOG.md, bumps base.DefaultUserAgent and the bin/b2keys/go.mod blazer requ…
Linked Issues check
Directly linked issue #423 has no library coding requirements. Its coding-relevant work is the release metadata: base/base.go sets DefaultUserAgent to blazer/0.10.1, and bin/b2keys/go.mod requ…
Out of Scope Changes check
The whole-PR diff against merge base 9d1581e changes exactly four files: .changes/v0.10.1.md (new), CHANGELOG.md, base/base.go (only the DefaultUserAgent constant), and bin/b2keys/go.mod (on…
Description check
The description follows the repository template's main sections (Motivation, Changes, Testing, Risk, How to revert, Checklist) in substance, although it does not use the template headings verbatim. Mo…
Full details: Title check
Explanation
The title "Version 0.10.1" names the release version. The changeset prepares v0.10.1: it adds the release notes, updates CHANGELOG.md, bumps base.DefaultUserAgent and the bin/b2keys/go.mod blazer requirement. The title is related to the main change but does not say what the release contains, so it is partially related and too broad to convey the nature of the release. It is not vague or generic like 'misc updates', so it does not require an inconclusive result.
Full details: Linked Issues check
Explanation
Directly linked issue #423 has no library coding requirements. Its coding-relevant work is the release metadata: base/base.go sets DefaultUserAgent to blazer/0.10.1, and bin/b2keys/go.mod requires github.com/Backblaze/blazer v0.10.1. .changes/v0.10.1.md and CHANGELOG.md contain the generated v0.10.1 entry with the compare link to v0.10.0...v0.10.1. The release notes account for all 14 commits in the audited range (#389, #390, #391, #392, #393, #394, #297, #401, #402, #403, #404, #405, #406, #408). They state that library source is unchanged and that existing features are not described as new. R1 to R3 are met, with the secret-scanning UNVERIFIED gate kept explicit in the PR description. R4 (milestone and code-owner review) and R5 (no merge, tag, or publish) are process actions that the diff cannot establish. They are not coding requirements, so they do not affect this verdict. The diff against the merge base 9d1581e lists only the four release-owned files.
Full details: Out of Scope Changes check
Explanation
The whole-PR diff against merge base 9d1581e changes exactly four files: .changes/v0.10.1.md (new), CHANGELOG.md, base/base.go (only the DefaultUserAgent constant), and bin/b2keys/go.mod (only the blazer requirement line). All four are listed as in scope by #423 and the release process. No library behavior, API, CI workflow, simulator, harness, or published v0.10.0 notes changed. The CHANGELOG.md hunk only inserts the new 0.10.1 section above 0.10.0. The content of the release notes was not compared line by line against the 14 commit contents. That check was not required to classify the scope.
Full details: Description check
Explanation
The description follows the repository template's main sections (Motivation, Changes, Testing, Risk, How to revert, Checklist) in substance, although it does not use the template headings verbatim. Motivation is clear: a documentation and test-infrastructure patch release, scoped to 14 commits, with the release-process references and the linked issue #423. Changes lists the metadata updates and the full commit audit. Testing gives the make ci tail, the changelog check, and the release-check output, and explains that no live B2 or simulator scenarios were rerun. Risk and How to revert are not separate sections, but the description states that the library source is unchanged and that no wire or API change exists, which covers most of that content. Checklist items are not ticked. The Live test field is addressed only in the Verification bullet, not as a labelled statement. The description also has a remaining gap: a secret-scanning gate is UNVERIFIED, which the author flags openly and which blocks release clearance. Overall the description is substantially complete and specific, so it passes.
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: df138eee-3473-4e39-b093-739022465916
Commits
Reviewing files that changed from the base of the PR and between 9d1581e and 6958490.
Files selected for processing: 4
.changes/v0.10.1.md
CHANGELOG.md
base/base.go
bin/b2keys/go.mod
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
What it changes. Release prep for v0.10.1 (issue #423): new .changes/v0.10.1.md, a ## [0.10.1] - 2026-11-17 section in CHANGELOG.md, base.DefaultUserAgentblazer/0.10.0 to blazer/0.10.1 (base/base.go:46) and the bin/b2keys/go.mod require to v0.10.1. The last two come from the .changie.yaml replacements. No library code changes.
Sensitive path.base/base.go is wire/auth code, so a code owner has to review it. It is a one-constant change that goes into the User-Agent of every request.
Checked and correct
The diff is exactly the 4 files, and no non-test .go file changed between v0.10.0 and the base.
The version metadata and compare link are right, and the v0.10.0 section is untouched.
The catalog counts (34 to 42 conformance, 15 to 16 resilience) match .sdkharness/tests.tsv at both tags.
The upgrade-guide claim is true: docs/upgrading.md now says three changes need a source change and adds CreateBucket, and the "before/after" arities match base/base.go:844.
The B2_ENDPOINT claim is true: no client constructor in the integration or lock tests is left without the endpoint options. The key-expiration wire tests cover both the JSON-null and zero-time cases.
go mod tidy -diff and go mod verify pass for both modules, and go.work is unchanged. There are no secrets in the diff.
Findings
Low, SECURITY.md:8,14: it still says the supported line is 0.9.x, while 0.10.0 is out and this PR publishes 0.10.1. RELEASE.md's release-commit table doesn't list the file, so nothing forces the update. Change it to 0.10.x in this PR (extending that table) or in a separate PR before tagging.
Low, CHANGELOG.md (0.10.0 section) and the new "Fixed" bullet: the 0.10.0 notes link to blob/v0.10.0/docs/upgrading.md, which is pinned to the tag and still has the error this PR fixes. The correction exists only on main/v0.10.1. Link the corrected guide from the 0.10.1 bullet (for example blob/v0.10.1/docs/upgrading.md once tagged) rather than editing the published 0.10.0 notes.
Nit, .changes/v0.10.1.md:5: the first "Changed" bullet cites no PR numbers, while the others do. The change fragments were consumed by changie batch, so reviewers can't see them.
Nit, PR body:Closes #423 closes the release task when the PR merges, before the tag and GitHub release steps (RELEASE.md steps 6 to 8). Refs #423 matches "preparation only".
Pre-existing, bin/b2keys/go.mod:5: the replace => ../.. stays, so go install github.com/Backblaze/blazer/bin/b2keys@v0.10.1 will be rejected. This PR bumps the require line but can't fix that. I confirmed it by reading, not by running go install (the tag doesn't exist yet). Worth an issue or a release-check step.
Pre-existing, 0.10.0 notes: a few documentation-consistency checks on the already-published 0.10.0 notes still fail. This release must not edit them.
Tests. The only behavioural change is the DefaultUserAgent string, and no test pins it. I reverted it to blazer/0.10.0 in a scratch tree and go test ./base ./b2 still passed. That's expected for release metadata, and the PR says no new test was needed. A cheap guard would be to assert that DefaultUserAgent matches the top changelog version.
bin/b2keys has no tests, and the bumped version is never actually resolved while the replace stays.
make changelog-check verifies the format, not that the text is true. I checked the notes by hand.
go test -race -shuffle=on -count=1 ./..., go vet, make crosscompile (including linux/386), make b2keys and .sdkharness selftest (29 passed): all exit 0.
Merge gates
Secret scanning is unverified. The API returns 404, so a maintainer has to check the Security tab by hand (RELEASE.md "Never").
area-owner-approvals is red, awaiting the code owners. All other CI is green.
make release-check reports a standard-library vulnerability on go1.27.3 and is clear on go1.27.4. It reproduces your claim, but only on 1.27.4. The CI minimum is 1.26.10/1.27.3, which is outside this PR.
Not run: live B2 tests and the new simulator-backed scenarios (they need credentials or the harness simulator), and a real 32-bit test run (cross-compile only).
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
documentationImprovements or additions to documentation
2 participants
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.
Context
Prepare v0.10.1, a documentation and test-infrastructure maintenance release, following
RELEASE.mdand the previous release PR #374. Main was verified green at9d1581e033dabc29f7e76b4c213c13ccd99c298fbefore preparation:Preparation only: no tag or GitHub release has been created. Do not merge/tag until the remaining UNVERIFIED secret-scanning section is checked or resolved by a maintainer under
RELEASE.md. Notes are dated November 17, 2026; refresh that date if the actual release is later.Changes
The audited range is
v0.10.0..9d1581e, 14 commits. It contains no library source changes. Metadata-by-name lookup and the in-process simulator were already released and are not presented as new. This is not a new library-feature or runtime-bug-fix release.batch v0.10.1, since the changed test/docs entries do not justify a minor SDK release..changes/v0.10.1.mdandCHANGELOG.md.base.DefaultUserAgenttoblazer/0.10.1and thebin/b2keys/go.modblazer requirement tov0.10.1.SECURITY.mdto the supported0.10.xline and add its maintenance to the release checklist. Rootgo.mod, dependencies, library behavior and published v0.10.0 notes remain unchanged.b2keysinstallation and release verification separately in Task: verify versioned b2keys installation during releases #427 (related to Make b2keys installable with go install and report a correct User-Agent version between releases #188).Complete commit audit
66be23984c23b4f083d5b45bdf0b01f9947b14effc9c3e65e0480eb03f5cf771ebe7e25c657e86e75c80da61d899d1581eChangelog
0.10.1 - 2026-11-17
This is a documentation and test-infrastructure maintenance release. No new SDK APIs or library runtime fixes are introduced; library source is unchanged from v0.10.0 apart from the standard release-version metadata.
Changed
B2_ENDPOINTon every client constructor, including low-level authorizations and scoped-key clients.TestUnknownCAusesB2_ENDPOINT_TLS, or an HTTPSB2_ENDPOINT, and skips with a reason when only plain HTTP is available. With the variables unset the existing integration-test endpoints are unchanged; this is test configuration only (test(integration): apply B2_ENDPOINT on all integration and lock clients #297).nullfor absent expiration timestamps and check both zero-time and set expiration results. This strengthens coverage of the existingExpirescontract without changing key expiration behavior (fix: correct v0.10.0 upgrade guide count and key-expiration fixtures #392).Fixed
(*base.B2).CreateBucket; passnilto retain the previous behavior (fix: correct v0.10.0 upgrade guide count and key-expiration fixtures #392).Verification
Go 1.27.4, darwin/arm64:
go run github.com/miniscruff/changie@v1.24.0 batch v0.10.1 --dry-run, batch, and merge completed. All generated version strings and the compare link use v0.10.1.make ciPASS withB2_APPLICATION_KEY_ID,B2_APPLICATION_KEY,B2_ACCOUNT_ID,B2_ACCOUNT_KEY,B2_ENDPOINT, andB2_ENDPOINT_TLSunset: build, vet, formatting, tidy/verify, lint, race tests, b2keys, cross-compiles, changelog and script checks.make changelog-checkPASS.7c8f21f:go test ./...,go vet ./...,make changelog-check, andmake ciPASS with B2 credentials and endpoints unset. The 0.10.1 note matches its changelog section; the published 0.10.0 section is unchanged.git diff --checkPASS.make cipassed.Local CI output
GOTOOLCHAIN=go1.27.4 make ci: exit 0. Tail:Release gate
GOTOOLCHAIN=go1.27.4 make release-check: exit 0 conditional on the UNVERIFIED section, not unconditional release clearance. Code scanning, patched Dependabot findings, triage/draft advisories and reachable vulnerabilities were clear. Secret scanning returned 404 and remains a manual maintainer action. No advisory IDs or unpublished findings are disclosed.Maintainer handoff
A human code owner must review the release paths and resolve the remaining gate qualification. After approval and merge, follow
RELEASE.mdto tag the release PR's merge commit and publish from.changes/v0.10.1.md. Those actions are deliberately not performed here. GitHub CI will run on this PR; no merge or release approval is implied by local checks.Refs #423