Skip to content

ci: update actions in gh workflows and use GITHUB_TOKEN - #52

Merged
shadowusr merged 1 commit into
masterfrom
users/shadowusr/TRIVIAL.fix-gh-actions-wf
Jul 22, 2026
Merged

ci: update actions in gh workflows and use GITHUB_TOKEN#52
shadowusr merged 1 commit into
masterfrom
users/shadowusr/TRIVIAL.fix-gh-actions-wf

Conversation

@shadowusr

Copy link
Copy Markdown
Member

No description provided.

@shadowusr
shadowusr merged commit 999fc4d into master Jul 22, 2026
2 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fc47b0d906

ℹ️ 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".

mcp_release_created: ${{ steps.release.outputs['packages/mcp--release_created'] }}
steps:
- uses: googleapis/release-please-action@v4
- uses: googleapis/release-please-action@v5

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore the PAT for release-please CI

This invocation now omits token, so release-please-action falls back to github.token; its v5 docs warn to use a PAT “if you want GitHub Actions CI checks to run on Release Please PRs.” Since this repo’s CI is a pull_request workflow on master, generated release PRs will stop getting the automatic checks that the old secrets.GH_ACCESS_TOKEN triggered, so protected merges can sit blocked until a maintainer manually approves/reruns them.

Useful? React with 👍 / 👎.

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.

1 participant