feat: release-publish-git — the OCI chain's sibling for git-clone repos - #97
Closed
sebasnallar wants to merge 1 commit into
Closed
feat: release-publish-git — the OCI chain's sibling for git-clone repos#97sebasnallar wants to merge 1 commit into
sebasnallar wants to merge 1 commit into
Conversation
Service/scope repositories whose deliverable IS the repository (specs, workflows, scripts — no image) get the same one-run chain: release-please cuts the version, the same run registers a git_repository artifact pinning the tag (np artifact create --type git_repository --url --reference, visible-to organization=* by default), and the release gets its Repository/Reference/Commit/Artifact-ID table and leaves draft. Same conventions as release-publish-oci: ARTIFACT_NP_API_KEY secret, NP_ARTIFACT_NRN variable, existing_tag recovery path, declared-choice errors instead of silent skips, idempotent release-body append. No id-token needed — there is no registry push. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Sep 1, 2026
Contributor
Author
|
Closing: the three service repos ship worker IMAGES after all (Pao provisioned their ECR Public repos + publisher roles in iac-null-runtime#109), so they adopt the existing release-publish-oci chain instead — no git_repository flavor needed. Branch kept in case a git-clone-only repo ever wants this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
`release-publish-git.yml`: the `release-publish-oci` chain for repositories whose deliverable is the repository — the service repos the agent git-clones (services-s-3, services-endpoint-exposer, services-postgresql-rds are the immediate adopters; caller PRs open alongside this one).
One chained run: release-please → `np artifact create --type git_repository --url --reference ` → release finalized with a Repository / Reference / Commit / Artifact-ID table and pulled out of draft.
Same conventions as the OCI chain, deliberately:
Differences from OCI, because there's nothing to push: no `id-token`/preflight, no docker jobs — just release + finalize.
🤖 Generated with Claude Code