Use the merged shared Gitea pipeline through repository-owned .ci.yaml. The organization bridge reads the opt-in from develop after merge; it then skips the legacy CI build jobs and requires the shared result.
The Maven verification runs once, then the existing flatten goal retains the exact tested JARs and resolved consumer POM for trusted snapshot publication. The legacy release caller stops on develop, preventing a second snapshot build/publisher. Existing RC and stable release paths remain until their migration. No application source or dependency version changes.
Configuration parsing passed against the merged shared schema. The platform implementation and opt-in bridge are merged. Keep this PR unmerged until the existing trusted publisher is ready for this enrollment; no completed end-to-end publication is claimed yet. No separate shared-delivery workflow is added.
Use the merged shared Gitea pipeline through repository-owned `.ci.yaml`. The organization bridge reads the opt-in from develop after merge; it then skips the legacy CI build jobs and requires the shared result.
The Maven verification runs once, then the existing flatten goal retains the exact tested JARs and resolved consumer POM for trusted snapshot publication. The legacy release caller stops on develop, preventing a second snapshot build/publisher. Existing RC and stable release paths remain until their migration. No application source or dependency version changes.
Configuration parsing passed against the merged shared schema. The platform implementation and opt-in bridge are merged. Keep this PR unmerged until the existing trusted publisher is ready for this enrollment; no completed end-to-end publication is claimed yet. No separate shared-delivery workflow is added.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Use the merged shared Gitea pipeline through repository-owned
.ci.yaml. The organization bridge reads the opt-in from develop after merge; it then skips the legacy CI build jobs and requires the shared result.The Maven verification runs once, then the existing flatten goal retains the exact tested JARs and resolved consumer POM for trusted snapshot publication. The legacy release caller stops on develop, preventing a second snapshot build/publisher. Existing RC and stable release paths remain until their migration. No application source or dependency version changes.
Configuration parsing passed against the merged shared schema. The platform implementation and opt-in bridge are merged. Keep this PR unmerged until the existing trusted publisher is ready for this enrollment; no completed end-to-end publication is claimed yet. No separate shared-delivery workflow is added.