Release qbit build parent importing QQQ 4.1 BOM #4

New Issue

2026-09-26T16:31:56Z

KofTwentyTwo commented

2026-09-26 16:31:56 +00:00

(Migrated from github.com)

Required by QRun-IO/qqq-all#10 after QQQ 4.1 GA.

Release a successor to com.kingsrook:qbit-build-parent:2.0.0 whose imported qqq-bom-pom is the published 4.1 release. Keep the existing Java 21 and qbit build behavior; do not change licensing without the separate owner decision.

Acceptance:

Start from current main; confirm QQQ 4.1 BOM is published and resolves from Maven Central.
Update the imported BOM to the exact released version; choose and document the successor parent version. Verify the published POM resolves QQQ modules without snapshot repositories.
Run parent validation and a representative qbit consumer build. Check generated POM, signatures, source/javadoc attachments, and Central publication before announcing the parent version to the eight qbit repos.
Record the tag, release artifact coordinates, and rollback/hotfix path. Do not publish before QQQ 4.1 GA and its release gates.

Required by QRun-IO/qqq-all#10 after QQQ 4.1 GA. Release a successor to `com.kingsrook:qbit-build-parent:2.0.0` whose imported `qqq-bom-pom` is the published 4.1 release. Keep the existing Java 21 and qbit build behavior; do not change licensing without the separate owner decision. Acceptance: - Start from current `main`; confirm QQQ 4.1 BOM is published and resolves from Maven Central. - Update the imported BOM to the exact released version; choose and document the successor parent version. Verify the published POM resolves QQQ modules without snapshot repositories. - Run parent validation and a representative qbit consumer build. Check generated POM, signatures, source/javadoc attachments, and Central publication before announcing the parent version to the eight qbit repos. - Record the tag, release artifact coordinates, and rollback/hotfix path. Do not publish before QQQ 4.1 GA and its release gates.

KofTwentyTwo commented

2026-09-26 18:01:57 +00:00

(Migrated from github.com)

Release-path audit: current main (aaf52d2) is qbit-build-parent:2.0.0, imports QQQ BOM 4.0.0, and uses kingsrook/qqq-orb@0.5.0. The orb pin predates the QQQ 4.1 release-path/settings fix (qqq-orb#12 / PR #13). Before cutting the successor parent, pin a tested stable orb with that fix, verify its candidate/tag version calculation and publishing behavior, and confirm the public 4.1 BOM resolves. Keep the release profile and its autoPublish behavior under deliberate release control; a merge to main is not itself the Central release trigger, but the tagged publish workflow is. No qbit parent artifact has been changed or published by this audit.

Release-path audit: current main (`aaf52d2`) is `qbit-build-parent:2.0.0`, imports QQQ BOM 4.0.0, and uses `kingsrook/qqq-orb@0.5.0`. The orb pin predates the QQQ 4.1 release-path/settings fix (qqq-orb#12 / PR #13). Before cutting the successor parent, pin a tested stable orb with that fix, verify its candidate/tag version calculation and publishing behavior, and confirm the public 4.1 BOM resolves. Keep the release profile and its `autoPublish` behavior under deliberate release control; a merge to `main` is not itself the Central release trigger, but the tagged publish workflow is. No qbit parent artifact has been changed or published by this audit.

KofTwentyTwo commented

2026-09-29 01:20:57 +00:00

(Migrated from github.com)

Bounded readiness preparation: frozen currentmain aaf52d202d. A private worktree proposes qbit-build-parent2.1.0 importing exactQQQ BOM4.1.0 (two POM value changes only). 2.1.0 is a review proposal, not a published/reserved version. Existing Java/build/release-profile/license behavior is preserved. Anonymous Central returns404 for both proposed coordinates, and a fresh private Maven model validation fails before compilation specifically on missingQQQ4.1.0. No signing/deployment/release was attempted.

The old0.5.0 orb pin is deliberately unchanged until existing qqq-orb#12/PR13 produces a reviewed stable version; PR13 is still open with no GitHub reviews returned. Do not start credential-bearing release CI with the old pin. Parent generated-POM/signature/public-consumer checks and a representative normal qBit build remain required after GA. All eight downstream candidate re-pins plus qqq-all pins are prepared locally under qqq-all#10; no duplicate orb or licensing changes, no push/publication. Workspace handoff: qqq-integration-review-evidence/public-release-chain-20260928/READINESS.md.

Bounded readiness preparation: frozen currentmain aaf52d202deafef688b242efb8ca01897a3779b0. A private worktree proposes qbit-build-parent2.1.0 importing exactQQQ BOM4.1.0 (two POM value changes only). 2.1.0 is a review proposal, not a published/reserved version. Existing Java/build/release-profile/license behavior is preserved. Anonymous Central returns404 for both proposed coordinates, and a fresh private Maven model validation fails before compilation specifically on missingQQQ4.1.0. No signing/deployment/release was attempted. The old0.5.0 orb pin is deliberately unchanged until existing qqq-orb#12/PR13 produces a reviewed stable version; PR13 is still open with no GitHub reviews returned. Do not start credential-bearing release CI with the old pin. Parent generated-POM/signature/public-consumer checks and a representative normal qBit build remain required after GA. All eight downstream candidate re-pins plus qqq-all pins are prepared locally under qqq-all#10; no duplicate orb or licensing changes, no push/publication. Workspace handoff: qqq-integration-review-evidence/public-release-chain-20260928/READINESS.md.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-bom#4