QRun-IO/qbit-quick-search
3
0 Fork 0
Code Issues 2 Pull Requests 4 Actions Packages Projects Releases 14 Wiki Activity

fix(build): restore historical release BOM resolution #78

Merged
KofTwentyTwo merged 2 commits from feature/restore-release-0.1.0-bom into release/0.1.0 2026-10-21 18:05:14 +00:00
Conversation 0 Commits 2 Files Changed 2
+2 -2
KofTwentyTwo commented 2026-10-21 17:41:43 +00:00 (Migrated from github.com)
Copy link
Copy source

Release/0.1.0 cannot resolve its vanished QQQ 0.40.0-SNAPSHOT BOM. Pin the published matching 0.40.0 release, retaining this historical API line.

Local Java21/Maven3.9.11 verification with the replacement BOM returned success: 174 unit tests passed without failures or skips. Five integration tests skipped because local Docker was unavailable. Hosted verification must prove these integration tests execute before merge; local success alone is insufficient.

This application dependency repair is separate from CI migration PR74. A normal merge may publish an RC via the existing release pipeline. After repair/publication, refresh PR74 against the resulting release head and prove the CI-only maintenance contract again.

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.1.0 cannot resolve its vanished QQQ 0.40.0-SNAPSHOT BOM. Pin the published matching 0.40.0 release, retaining this historical API line. Local Java21/Maven3.9.11 verification with the replacement BOM returned success: 174 unit tests passed without failures or skips. Five integration tests skipped because local Docker was unavailable. Hosted verification must prove these integration tests execute before merge; local success alone is insufficient. This application dependency repair is separate from CI migration PR74. A normal merge may publish an RC via the existing release pipeline. After repair/publication, refresh PR74 against the resulting release head and prove the CI-only maintenance contract again. 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
architecture
Architecture review: coupling, cohesion, UI API
 bug
Something isn't working
 dependencies
documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 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
 secuurity
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
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QRun-IO/qbit-quick-search#78