-
Notifications
You must be signed in to change notification settings - Fork 14
chore: Fix release please config and changelog file #338
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.
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR fixes release-please configuration and updates the changelog to improve release automation. The main changes include adding the include-component-in-tag: false setting to generate cleaner version tags without component prefixes, updating changelog entries to use the corrected tag format, and adding upgrade documentation and scripts.
Changes:
- Configure release-please to exclude component names from version tags
- Update CHANGELOG.md to use corrected version comparison URLs (v6.1.0 instead of poco-v6.1.0)
- Add v6.1.0 upgrade script and update upgrade documentation
Reviewed changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| release-please-config.json | Adds configuration to exclude component prefix from version tags |
| CHANGELOG.md | Updates version comparison URLs and reorganizes changelog entries for v6.2.0 and v6.1.0 |
| scripts/upgrades/v6.2.0-easy-deposit-and-tdx-dataset.md | Adds deployment logs for Arbitrum Mainnet upgrade |
| scripts/upgrades/v6.1.0.ts | Adds new upgrade script for bulk processing upgrade |
| scripts/upgrades/README.md | Updates upgrade process documentation with additional steps |
Comments suppressed due to low confidence (1)
scripts/upgrades/v6.2.0-easy-deposit-and-tdx-dataset.md:3
- The date "21/01/2026" is in the future. The current date is January 21, 2026, but typically upgrade documentation dates should reflect when the upgrade was actually performed or planned, not set to today's date unless it was genuinely executed today.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #338 +/- ##
=======================================
Coverage 96.39% 96.39%
=======================================
Files 33 33
Lines 1137 1137
Branches 214 228 +14
=======================================
Hits 1096 1096
Misses 41 41 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
No description provided.