Skip to content

ci(release): add reusable release-please workflow and dogfood it#16

Open
OgeonX-Ai wants to merge 2 commits into
mainfrom
ci/release-please-automation
Open

ci(release): add reusable release-please workflow and dogfood it#16
OgeonX-Ai wants to merge 2 commits into
mainfrom
ci/release-please-automation

Conversation

@OgeonX-Ai

Copy link
Copy Markdown
Contributor

Summary

  • Adds .github/workflows/release-please-reusable.yml: a workflow_call workflow wrapping googleapis/release-please-action@45996ed1f6d02564a971a2fa1b5860e934307cf7 (v5.0.0, SHA-pinned), with job-level contents/pull-requests/issues: write permissions and an optional release-type input (default simple).
  • Dogfoods the pattern: org-dotgithub's own release-please-config.json (release-type simple, changelog-path: CHANGELOG.md) + .release-please-manifest.json (bootstrap "0.0.0", zero existing GitHub tags) + .github/workflows/release-please.yml caller wired to uses: Coding-Autopilot-System/.github/.github/workflows/release-please-reusable.yml@f288e5e3b67b29a2c08880b76da7b852f4a132d0 (the exact SHA of this branch's first commit).
  • Adds a "Release Automation (v1.5)" section to docs/RELEASE_POLICY.md documenting tool choice, uniform release-type: simple, per-repo independent SemVer, bootstrap baseline rules, and the SHA-pin policy.

This is Phase 39 wave 1 (39-01) of the CAS v1.5 milestone. Wave 2/3 plans (39-02, 39-03) will wire the other 12 portfolio repos against the pin SHA f288e5e3b67b29a2c08880b76da7b852f4a132d0 produced here.

Test plan

  • yaml.safe_load on both new workflow YAML files parses clean
  • json.load on release-please-config.json and .release-please-manifest.json parses clean
  • Reusable workflow has no target-branch input (lets each caller's own default branch auto-detect)
  • Caller workflow's uses: line references the 40-char commit SHA of the first commit on this branch, not a branch/tag ref

PR-only per org convention — not merging.

Co-Authored-By: Claude Fable 5 noreply@anthropic.com

- workflow_call entry point wrapping googleapis/release-please-action@45996ed (v5.0.0)
- SHA-pinned, job-level permissions (contents/pull-requests/issues: write)
- optional release-type input (default simple), no target-branch input so callers' own default branch auto-detects
- release-please-config.json: release-type simple, package ".", changelog-path CHANGELOG.md
- .release-please-manifest.json: bootstrap ".": "0.0.0" (org-dotgithub has zero GitHub tags today)
- .github/workflows/release-please.yml: push-to-main trigger, calls release-please-reusable.yml pinned to this branch's first commit SHA
- docs/RELEASE_POLICY.md: document tool choice, uniform release-type, per-repo independent SemVer, bootstrap baseline rationale, and SHA-pin policy
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants