-
Notifications
You must be signed in to change notification settings - Fork 222
chore: add 1.6.0 changelog notes #5425
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
|
Branch previewReview the following VRT differencesWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
If the changes are expected, update the |
Tachometer resultsCurrently, no packages are changed by this PR... |
|
||
- **icons-workflow**: added missing S2 icons | ||
|
||
### Bug Fixes |
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.
If we choose to move forward with the changesets approach, I believe it makes sense to keep the default grouping as Major, Minor, and Patch
, as it aligns well with semantic versioning and keeps things simple for now.
That said, if we later decide to adopt a more customized grouping—like Bug Fixes, Features, etc.—we’ll likely need to introduce additional customizations to support that structure effectively.
In the meantime, please go ahead and use the script in this PR to start automatically generating the global CHANGELOG. It should help us get closer to a more streamlined and consistent release process.
Let me know if anything feels unclear or if you'd like to explore other options together!
Description
Add in the changelog notes to global changelog for 1.6.0
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main
.