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
## Why
`sbt-airframe 2026.2.2` and its `airframe-*` dependencies are now
published on Maven Central, so the root build's metabuild resolves the
plugin normally. The temporary `bootstrap-sbt-airframe` composite action
(added to break the first-release deadlock) is no longer needed.
## What
- Delete `.github/actions/bootstrap-sbt-airframe/`.
- Remove its `- uses:` steps from `test.yml` (11),
`sbt-integration.yml`, and the four release workflows.
- `SBT_AIRFRAME_VERSION` stays pinned to the released `2026.2.2`; a
comment now warns against bumping it to the in-development version (that
would reintroduce the release-time metabuild deadlock) — same discipline
as `AIRSPEC_VERSION`.
## Verified
Cleared the locally-published `2026.2.2` artifacts and confirmed the
root build resolves `sbt-airframe 2026.2.2` **from Central** (no local
publish, no bootstrap): `integrationTest/airframeHttpClients` resolves
correctly.
CI on this PR is the real end-to-end check that Central resolution works
without the bootstrap.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments