Skip to content

fix: use main branch for changesets/bot action #363

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kimyouknow merged 3 commits into from
Apr 21, 2026
Merged

fix: use main branch for changesets/bot action #363

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fec7d99
fix: use main branch for changesets/bot action
guesung Apr 2, 2026
bcf5104
ci: pin changesets/bot action to commit SHA for supply-chain security
guesung Apr 10, 2026
bdd89a5
Merge branch 'main' into fix/changeset-bot-action-tag
kimyouknow Apr 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/changeset-bot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,4 +11,4 @@ jobs:
bot:
runs-on: ubuntu-latest
steps:
- uses: changesets/bot@v1
- uses: changesets/bot@main
Copy link

Copilot AI Apr 2, 2026

Choose a reason for hiding this comment

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

Using a floating ref (changesets/bot@main) makes this workflow non-deterministic and increases supply-chain risk, especially with pull_request_target and pull-requests: write permissions (the action code can change without review). Prefer pinning the action to an immutable commit SHA (or a trusted, signed tag/release if one becomes available) and update it intentionally when needed.

Suggested change
- uses: changesets/bot@main
- uses: changesets/bot@3b4cf1f2c9a6c1891d3dbed1d5d295df1b548d64 # pinned from @main

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Collaborator

@kimyouknow kimyouknow Apr 7, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

@guesung Thanks for fixing the bot failure from #350!

All our other actions are SHA-pinned for supply-chain security
(see #325). Could you pin this one too?

Copy link
Copy Markdown
Contributor Author

@guesung guesung Apr 10, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

@kimyouknow Thanks for the review! I've pinned it to a full commit SHA in bcf5104.

I pinned to e755cedfffdc49f54ce5daa69d960a143941b787(current master HEAD).

Copy link
Copy Markdown
Collaborator

@kimyouknow kimyouknow Apr 21, 2026

Choose a reason for hiding this comment

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

Thanks!

Loading