build: QQQ 4.1.0-RC.22 from the Gitea registry; shared ci-workflows Maven pipeline; 1.1.2 #33

Merged

james.maes merged 3 commits from ci/gitea-registry-rc22-20261106 into main 2026-11-06 20:18:19 +00:00

Conversation 0 Commits 3 Files Changed 7

+36 -13

james.maes commented 2026-11-06 16:47:45 +00:00

Owner

Copy link

Copy source

Everything moves to the QRun-IO Gitea Maven registry (James, 2026-11-06). QQQ 4.1.0-RC.22 exists only there, and the protected qrun-release-v1 channel's Maven settings resolve only Maven Central (Google mirror), so this repository now builds on the shared KofTwentyTwo/ci-workflows Maven workflow (.gitea/workflows/build.yaml, @v1, -Pui-demo): every push runs verify against the registry with the job token; a vX.Y.Z tag tests once and deploys the JAR/POM under that version. The qrun-release caller and the trusted-publisher path are retired here (its cluster-gitops enrollment follows in a separate PR). PrintingContractTest keeps using the vendored protocol fixtures.

• qqq.version 4.1.0-RC.21 → 4.1.0-RC.22; version 1.1.2. No printing contract change (extension 2.4.0, wire v1, subprotocol unchanged).
• README, CHANGELOG, docs/RELEASES.md (new maintainer path), docs/SESSION-STATE.md updated.
• Remaining Central dependencies: frontend-next 1.0.0-RC.37 (ui-demo profile only; frontend lane to publish to Gitea) and third-party libraries (until the registry proxies them).

Gate: this PR's push build (-Pui-demo verify on RC.22) is the certification evidence; local verify cannot reach the registry from this PC.

🤖 Generated with Claude Code

Everything moves to the QRun-IO Gitea Maven registry (James, 2026-11-06). QQQ **4.1.0-RC.22** exists only there, and the protected `qrun-release-v1` channel's Maven settings resolve only Maven Central (Google mirror), so this repository now builds on the shared `KofTwentyTwo/ci-workflows` Maven workflow (`.gitea/workflows/build.yaml`, `@v1`, `-Pui-demo`): every push runs verify against the registry with the job token; a `vX.Y.Z` tag tests once and deploys the JAR/POM under that version. The `qrun-release` caller and the trusted-publisher path are retired here (its cluster-gitops enrollment follows in a separate PR). `PrintingContractTest` keeps using the vendored protocol fixtures. - `qqq.version` 4.1.0-RC.21 → **4.1.0-RC.22**; version 1.1.2. No printing contract change (extension 2.4.0, wire v1, subprotocol unchanged). - README, CHANGELOG, `docs/RELEASES.md` (new maintainer path), `docs/SESSION-STATE.md` updated. - Remaining Central dependencies: frontend-next 1.0.0-RC.37 (ui-demo profile only; frontend lane to publish to Gitea) and third-party libraries (until the registry proxies them). Gate: this PR's push build (`-Pui-demo verify` on RC.22) is the certification evidence; local verify cannot reach the registry from this PC. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

james.maes added 3 commits 2026-11-06 19:32:37 +00:00

build: QQQ 4.1.0-RC.22 from the Gitea registry; shared ci-workflows Maven pipeline; 1.1.2 ... 3c39a6af1b

Everything moves to the QRun-IO Gitea Maven registry. QQQ 4.1.0-RC.22 exists only
there, and the protected qrun-release channel resolves only Maven Central, so the
repository now builds on the shared KofTwentyTwo/ci-workflows maven workflow (@v1):
every push runs -Pui-demo verify against the registry with the job token; a vX.Y.Z
tag tests once and deploys the JAR/POM under that version. The qrun-release caller
and its trusted-publisher path are retired for this repository; PrintingContractTest
keeps using the vendored protocol fixtures. No printing contract change.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>

test: pin the vendored protocol fixtures README to protocol 1.1.0 (5005f3c) ... 8d5b72302c

The copied files are byte-identical between 42c0d249 and 5005f3c9; only the
documented pin moves, matching the released protocol the server pairs with.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>

docs: frontend-next 1.0.0-RC.37 is served from the Gitea registry ... c31a8f5f33

Mirrored byte-for-byte from Maven Central (verified against Central's SHA-1 and read
back from the registry), so the ui-demo profile resolves from Gitea too.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>

james.maes force-pushed ci/gitea-registry-rc22-20261106 from 8bb073b048 to c31a8f5f33 2026-11-06 19:32:37 +00:00 Compare

james.maes merged commit f5639a98be into main 2026-11-06 20:18:19 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

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

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

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-printing#33