Skip to content

[Backport] Prepare v4 for stable release - #4304

Merged
moskyb merged 3 commits into
v3from
backport-pr-4290-to-v3
Sep 1, 2026
Merged

[Backport] Prepare v4 for stable release#4304
moskyb merged 3 commits into
v3from
backport-pr-4290-to-v3

Conversation

@moskyb

@moskyb moskyb commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Description

Backport of #4290 to v3. This routes future v3 releases only to oldstable, enables oldstable GitHub and Homebrew publishing, removes the soft-failing Debian/RPM Buildkite Packages uploads, and makes the existing-tag guard use an exact ref match.

There are no v3 translation deviations.

Context

See #4290 for the original change and review context.

Testing

  • Release pipeline YAML parses successfully.
  • Release shell scripts pass bash -n.
  • A mocked dry run routes v3 exclusively to agent-release-oldstable.

Disclosures / Credits

Amp performed the backport and validation.

moskyb and others added 3 commits September 1, 2026 09:54
Make it so that making a v4.0.0 tag will release it to stable, and further 3.x releases will go to oldstable

(cherry picked from commit 91b4b34)
Amp-Thread-ID: https://ampcode.com/threads/T-01a055eb-f170-70eb-a61f-56000e7a2feb
Co-authored-by: Amp <amp@ampcode.com>
(cherry picked from commit fd6044d)
@moskyb
moskyb requested review from a team as code owners August 31, 2026 23:55
@moskyb moskyb added the change Not a new feature, but a user observable non-breaking behavior change. label Aug 31, 2026

@buildsworth-bk-app buildsworth-bk-app Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an exact three-commit backport of #4290; I found no backport-specific issues. I’m leaving this as comment-only because it directly changes stable/oldstable release routing and publication.

Want to dig deeper?

Paste this into your agent to explore the findings from this review's Buildkite build:

Download the buildsworth logs from build 23301, then answer my questions about the findings.

Install the reading-buildsworth-logs skill to run this.

About buildsworth

Model: gpt-5.6-sol with xhigh thinking.

How to request a review: Comment @buildsworth-bk review on the PR, or request buildsworth-bk as a reviewer.

Risk labels (how buildsworth classifies risk) — buildsworth classifies risk itself from the diff. Unless repository policy already allows L2 approval, grant it by mentioning @buildsworth-bk (see approval ceiling and L2 approval grant):

  • L1 — Low risk (dep bumps, docs/copy, lockfiles, small presentational fixes). buildsworth may approve by default.
  • L2 — Standard risk (new UI, additive API fields, refactors). Approved only when repository policy or a verified grant allows it; otherwise comment-only.
  • L3 — High risk (auth, migrations, payments, secrets, perf-critical pipeline paths). Human review always required.

@moskyb
moskyb merged commit 8107948 into v3 Sep 1, 2026
5 of 6 checks passed
@moskyb
moskyb deleted the backport-pr-4290-to-v3 branch September 1, 2026 00:37
@moskyb moskyb added internal Non-user facing, internal change. and removed change Not a new feature, but a user observable non-breaking behavior change. labels Sep 3, 2026
@moskyb moskyb changed the title [Backport] Prepare v4 for stable release Prepare v4 for stable release Sep 3, 2026
@moskyb moskyb added the change Not a new feature, but a user observable non-breaking behavior change. label Sep 3, 2026
@moskyb moskyb changed the title Prepare v4 for stable release [Backport] Prepare v4 for stable release Sep 3, 2026
@moskyb moskyb removed the internal Non-user facing, internal change. label Sep 3, 2026
@moskyb moskyb mentioned this pull request Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

change Not a new feature, but a user observable non-breaking behavior change.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants