Uh oh!
There was an error while loading. Please reload this page.
fix(ci): remove release commit to avoid unsigned commits - #379
Conversation
…-release Per semantic-release FAQ, making commits during release adds significant complexity including branch protection bypass. Use GitHub Releases for changelog instead of committing CHANGELOG.md.
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe semantic-release workflow and configuration are modernized to use GitHub App token authentication instead of manually configured git credentials, and the release plugin chain is simplified by removing the changelog and git plugins while disabling success/failure comments in the GitHub plugin. ChangesSemantic-release configuration modernization
🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Uh oh!
There was an error while loading. Please reload this page.
✅ Deploy Preview for devsydev canceled.
|
…-release (#379) Per semantic-release FAQ, making commits during release adds significant complexity including branch protection bypass. Use GitHub Releases for changelog instead of committing CHANGELOG.md.
Summary
@semantic-release/gitand@semantic-release/changelogplugins that were causing unsigned commits on protected branchesCHANGELOG.md— release notes now live exclusively in GitHub ReleasesPer the semantic-release FAQ, making commits during release adds significant complexity including branch protection bypass requirements.
Summary by CodeRabbit