ci: enroll shared Gitea Android lifecycle #11

Merged

forge-recovery merged 1 commits from ci/qrun-android-publisher-main-20261102 into main 2026-11-02 21:25:13 +00:00

Conversation 0 Commits 1 Files Changed 1

+13

forge-recovery commented 2026-11-02 19:58:12 +00:00

Owner

Copy link

Copy source

Add one standard readonly main-push/manual caller to the existing protected shared channel. It reuses the original qualified Android unit-test + emulator + main-only local Maven capture workflow; application/Gradle/dependency/source-version bytes remain unchanged. No registry credentials or writer in build jobs.

Current main2299 independently proves both real test families and exact two-module POM/AAR/sources/javadoc/Gradle metadata capture. The trusted publisher consumes the same existing reactor artifact schema, reads exact source gradle.properties coordinates/version and uses its existing package writer/reader. Ordinary topic/PR checks remain unchanged; this main-only producer provides historical workflow provenance missing from org-scoped REST metadata.

Merge dependency: qualified shared Android callee and compatible trusted publisher must be deployed, and existing source reader needs the separately reviewed repo114 READ enrollment. Publication policy is currently inert; no scoped-run publication or production-version change is claimed.

Add one standard readonly main-push/manual caller to the existing protected shared channel. It reuses the original qualified Android unit-test + emulator + main-only local Maven capture workflow; application/Gradle/dependency/source-version bytes remain unchanged. No registry credentials or writer in build jobs. Current main2299 independently proves both real test families and exact two-module POM/AAR/sources/javadoc/Gradle metadata capture. The trusted publisher consumes the same existing reactor artifact schema, reads exact source gradle.properties coordinates/version and uses its existing package writer/reader. Ordinary topic/PR checks remain unchanged; this main-only producer provides historical workflow provenance missing from org-scoped REST metadata. Merge dependency: qualified shared Android callee and compatible trusted publisher must be deployed, and existing source reader needs the separately reviewed repo114 READ enrollment. Publication policy is currently inert; no scoped-run publication or production-version change is claimed.

forge-recovery added 1 commit 2026-11-02 19:58:12 +00:00

ci: enroll the shared read-only Android publication producer ... 6980c4f7c3

Co-Authored-By: Codex <noreply@openai.com>

forge-recovery merged commit b75fdac881 into main 2026-11-02 21:25:13 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

bug

Something isn't working

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

question

Further information is requested

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/qqq-android#11