Repository navigation
Conversation
|
👍 @Innei Thank you for raising your pull request and contributing to our Community. 非常感谢您提出拉取请求并为我们的社区做出贡献,请确保您已经遵循了我们的贡献指南,我们会尽快审查它。 |
|
@Innei is attempting to deploy a commit to the LobeHub OSS Team on Vercel. A member of the Team first needs to authorize it. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 47d180ec8f
ℹ️ 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: Release | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/create-github-app-token@v2 |
There was a problem hiding this comment.
Mint the release App token after the build
When Install deps, CI, Test, and Build take at least an hour, the token created here has expired before the Release step uses it. GitHub documents that an installation access token "will expire after 1 hour", whereas the replaced PAT did not have this deadline, so a slow but otherwise successful release now fails during publishing; create or refresh the App token immediately before Release instead.
Useful? React with 👍 / 👎.
Replaces the
GH_TOKENpersonal access token with an installation token minted by the LobeHub bot GitHub App, matchinglobehub/lobehubandlobehub/lobe-ui.Each job that read
secrets.GH_TOKENnow starts with:and uses
${{ steps.app-token.outputs.token }}where it used${{ secrets.GH_TOKEN }}.LOBEHUB_BOT_APP_IDandLOBEHUB_BOT_APP_PRIVATE_KEYare org-level, so no repo setup is needed. TheGH_TOKENPAT is being revoked.Changed:
.github/workflows/issue-auto-comments.yml.github/workflows/issue-check-inactive.yml.github/workflows/issue-close-require.yml.github/workflows/release.yml