Adds the existing shared SDK release-candidate channel for release/* using rc-from-branch and Maven release validation. Preserves the qualified develop snapshot channel, verification commands, artifact paths, Central completion and source version write-back. Excludes release branches from the retired legacy producer to prevent duplicate publication. Production source and tests are unchanged. The publisher destination must separately authorize this RC channel before the first cut. Signed RC tag/prerelease-record parity is not implemented by this SDK path and is not claimed by this artifact publication change.
Adds the existing shared SDK release-candidate channel for release/* using rc-from-branch and Maven release validation. Preserves the qualified develop snapshot channel, verification commands, artifact paths, Central completion and source version write-back. Excludes release branches from the retired legacy producer to prevent duplicate publication. Production source and tests are unchanged. The publisher destination must separately authorize this RC channel before the first cut. Signed RC tag/prerelease-record parity is not implemented by this SDK path and is not claimed by this artifact publication change.
Declare a release-candidate channel (push to release/*, versioning maven-release, effective version rule rc-from-branch, central completion and
the same source write-back policy as the snapshot channel) and publish it to the existing qrun-maven destination alongside the snapshot channel.
The snapshot channel, verification pushes, component, build commands (including flattening) and artifact paths are unchanged. The operator
enrollment of the destination must also grant the release-candidate channel before anything publishes.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The legacy caller already skips develop because the shared pipeline publishes it. A push to release/X.Y would otherwise start the retired
producer next to the shared release-candidate channel and publish the same RC twice. Skip release/* the same way. Needs CI-owner review: the
file is the standard thin caller (its sha256 is an enrolled workflow identity of the legacy route, which is retired for this repository).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
Adds the existing shared SDK release-candidate channel for release/* using rc-from-branch and Maven release validation. Preserves the qualified develop snapshot channel, verification commands, artifact paths, Central completion and source version write-back. Excludes release branches from the retired legacy producer to prevent duplicate publication. Production source and tests are unchanged. The publisher destination must separately authorize this RC channel before the first cut. Signed RC tag/prerelease-record parity is not implemented by this SDK path and is not claimed by this artifact publication change.