fix(build): use published QQQ 0.40.0 BOM on release line #24

Merged

KofTwentyTwo merged 2 commits from feature/restore-release-0.4-bom into release/0.4 2026-10-21 17:56:06 +00:00

Conversation 0 Commits 2 Files Changed 2

+2 -2

KofTwentyTwo commented 2026-10-21 17:37:36 +00:00 (Migrated from github.com)

Copy link

Copy source

Release/0.4 cannot build because its QQQ 0.40.0-SNAPSHOT BOM no longer exists in the snapshot repository. Pin the published matching 0.40.0 BOM instead of moving this historical release line to a newer QQQ API.

Verification: Java21/Maven3.9.11 full verify against the same release source using the replacement BOM passed all 18 tests with zero failures, errors or skips. The failing hosted job101 resolves no application dependencies; this repairs that prerequisite for migration PR23.

This is an application dependency repair, not CI-only maintenance. Its normal release-branch merge may publish an RC through the existing pipeline. After successful repair and publication, refresh PR23 on the resulting release head and re-prove its maintenance-only behavior.

Hosted verification exposed an interactive needrestart dialog in the old orb installer. Update only the orb pin to published, verified0.7.15 so its shared unattended installer runs. Existing workflow/job arguments and publication filters remain unchanged; canonical graph conversion stays in the separate migration PR. The repaired application and this orb update must pass hosted checks together.

Release/0.4 cannot build because its QQQ 0.40.0-SNAPSHOT BOM no longer exists in the snapshot repository. Pin the published matching 0.40.0 BOM instead of moving this historical release line to a newer QQQ API. Verification: Java21/Maven3.9.11 full verify against the same release source using the replacement BOM passed all 18 tests with zero failures, errors or skips. The failing hosted job101 resolves no application dependencies; this repairs that prerequisite for migration PR23. This is an application dependency repair, not CI-only maintenance. Its normal release-branch merge may publish an RC through the existing pipeline. After successful repair and publication, refresh PR23 on the resulting release head and re-prove its maintenance-only behavior. Hosted verification exposed an interactive needrestart dialog in the old orb installer. Update only the orb pin to published, verified0.7.15 so its shared unattended installer runs. Existing workflow/job arguments and publication filters remain unchanged; canonical graph conversion stays in the separate migration PR. The repaired application and this orb update must pass hosted checks together.

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

bug

Something isn't working

dependencies

Pull requests that update a dependency file

documentation

Improvements or additions to documentation

duplicate

This issue or pull request already exists

enhancement

New feature or request

good first issue

Good for newcomers

help wanted

Extra attention is needed

invalid

This doesn't seem right

java

Pull requests that update java code

question

Further information is requested

release:rc

Merging this develop PR cuts the next release candidate

wontfix

This will not be worked on

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

forge-recovery (Forge Recovery) james.maes (James Maes)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-customizable-table-views#24