feat: update workflows for release 3 support and version bumping #417
Conversation
![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.
ℹ️ 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".
| - name: Build Artifacts | ||
| uses: ./.github/actions/build-artifacts |
There was a problem hiding this comment.
The new publish workflow calls the composite action ./.github/actions/build-artifacts without providing its required PERSONAL_ACCESS_TOKEN input. That action’s definition marks the token as required, so this job will fail immediately with “Input required and not supplied: PERSONAL_ACCESS_TOKEN” before any build or publish steps run, blocking the release/3 publish pipeline.
Useful? React with 👍 / 👎.
| on: | ||
| push: | ||
| branches: | ||
| - main | ||
| - release/v3 |
There was a problem hiding this comment.
The update workflow now listens for pushes on release/v3, but the rest of the release automation (auto-dependency matrix and the new publish workflow trigger) consistently use the release/3 branch naming. With this typo the update job will never run on the actual release branch, so pushing release/3 changes will no longer deploy the docs unless triggered manually.
Useful? React with 👍 / 👎.
No description provided.