ci: actually automate updating rule version metadata, for real this time#7430
ci: actually automate updating rule version metadata, for real this time#7430
Conversation
|
WalkthroughRemoved .changeset/fluffy-jeans-cheat.md (placeholder-only file). Added a "Stash changes" step to .github/workflows/release.yml that runs git stash push -u -m __automated-changes after scripts/update-next-version.sh and before the Create Release Pull Request step. Updated package.json Suggested labels
Suggested reviewers
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
✨ Finishing Touches🧪 Generate unit tests
Comment |
71fabd0 to
6a286c0
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
.changeset/fluffy-jeans-cheat.md(0 hunks).github/workflows/release.yml(1 hunks)package.json(1 hunks)
💤 Files with no reviewable changes (1)
- .changeset/fluffy-jeans-cheat.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Check JS Files
- GitHub Check: Test Node.js API
6a286c0 to
adc1b95
Compare
Summary
Follow up to #7429. The job will now stash the changes to get around the git reset and reapply them later. We can't do a commit because the changeset cli resets to the branch to a specific commit, not to the current HEAD. https://github.com/changesets/action/blob/04d574e831923498156e0b2b93152878063203a3/src/git.ts#L100
Test Plan
We'll see if it works when it lands. I don't know if its actually required to have a new changeset to actually trigger the workflow to run.
Docs