internal: Remove temporary sbt-airframe CI/release bootstrap#4188
Merged
Conversation
sbt-airframe 2026.2.2 (and its airframe-* deps) are now on Maven Central, so the root build's metabuild resolves the plugin normally. Remove the bootstrap-sbt-airframe composite action and its uses from the CI and 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 (which would reintroduce the release-time metabuild deadlock), same discipline as AIRSPEC_VERSION. Verified the root build resolves sbt-airframe 2026.2.2 from Central with no local publish and no bootstrap. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request removes the bootstrap configuration for sbt-airframe and updates the documentation in project/plugin.sbt to clarify that SBT_AIRFRAME_VERSION should remain pinned to a released version on Maven Central to prevent release-time deadlocks. There are no review comments, so I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
Tick the box to add this pull request to the merge queue (same as
|
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.
Why
sbt-airframe 2026.2.2and itsairframe-*dependencies are now published on Maven Central, so the root build's metabuild resolves the plugin normally. The temporarybootstrap-sbt-airframecomposite action (added to break the first-release deadlock) is no longer needed.What
.github/actions/bootstrap-sbt-airframe/.- uses:steps fromtest.yml(11),sbt-integration.yml, and the four release workflows.SBT_AIRFRAME_VERSIONstays pinned to the released2026.2.2; a comment now warns against bumping it to the in-development version (that would reintroduce the release-time metabuild deadlock) — same discipline asAIRSPEC_VERSION.Verified
Cleared the locally-published
2026.2.2artifacts and confirmed the root build resolvessbt-airframe 2026.2.2from Central (no local publish, no bootstrap):integrationTest/airframeHttpClientsresolves correctly.CI on this PR is the real end-to-end check that Central resolution works without the bootstrap.
🤖 Generated with Claude Code