Repository navigation
chore: migrate release workflow from baseline to releaser - #51
Conversation
Split single-step release.yml into prepare-release.yml (workflow_dispatch) and publish-release.yml (triggered on release branch PR merge), using actions from rubykatzen/releaser@v0.4.1 instead of removed baseline actions. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2c5a4efd3d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| steps: | ||
| - uses: actions/checkout@v7 | ||
| with: | ||
| ref: main |
There was a problem hiding this comment.
🤖 [rubykatzen/docker-apps]: In the inspected .github/workflows/publish-release.yml, checking out ref: main means the tag and docker-apps.zip are built from whatever main points to when this job starts. If another PR lands after the release PR is merged but before this workflow reaches checkout, the release tag will include unrelated post-release changes while the release notes still come from the release branch/version; use the pull request merge SHA or the event SHA instead of the moving branch ref.
Useful? React with 👍 / 👎.
| with: | ||
| version: ${{ inputs.version }} | ||
| notes: ${{ steps.notes.outputs.notes }} | ||
| - uses: rubykatzen/releaser/.github/actions/push-release-branch@v0.4.1 |
There was a problem hiding this comment.
🤖 [rubykatzen/docker-apps]: This is the final step of the prepare workflow, and it only pushes release/v${version}; the new publish workflow runs only when a PR into main is closed. A workflow_dispatch run therefore leaves the release process stalled unless someone manually creates the PR, contrary to the intended prepare → merge PR → publish flow; add a PR creation step/permission here or document and automate the manual handoff elsewhere.
Useful? React with 👍 / 👎.
Summary
release.yml, который ссылался на удалённые actions изrubykatzen/baselineprepare-release.yml(workflow_dispatch) — создаёт release-веткуpublish-release.yml(триггер на merge release-ветки) — создаёт GitHub release и загружает бандлНовый процесс
Prepare releaseвручную сversionиbase_sharelease/v{version}→mainPublish releaseавтоматически создаст тег, релиз и загрузитdocker-apps.zipTest plan
prepare-releaseдляv0.2.2release/v0.2.2🤖 Generated with Claude Code