-
Notifications
You must be signed in to change notification settings - Fork 207
chore: Updates CHANGELOG.md header, example link and SSDLC compliance report for v1.41.1 release #3735
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
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
Updates the CHANGELOG.md and documentation to reflect the v1.41.1 release by adding the appropriate changelog entries and updating the example link reference to point to the correct version tag.
- Adds CHANGELOG.md entries for version 1.41.1 with bug fixes and version 2.0.1 with enhancements and bug fixes
- Updates example configurations link from v1.41.0 to v1.41.1 in documentation
- Adds new SSDLC compliance report file for v1.41.1 release
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
File | Description |
---|---|
CHANGELOG.md | Adds changelog entries for v1.41.1 and v2.0.1 releases with detailed feature, enhancement, and bug fix information |
docs/index.md | Updates example configurations link to reference v1.41.1 instead of v1.41.0 |
compliance/v1.41.1/ssdlc-compliance-1.41.1.md | Adds new SSDLC compliance report for the v1.41.1 release |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
APIx bot: a message has been sent to Docs Slack channel |
Cherry-picked b9c34fc to avoid example validation from failing because of |
|
||
## 1.41.1 (October 01, 2025) | ||
|
||
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.
we shouldn't have 2.0.0 releases in the changelog for v1 releases
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.
or maybe having CHANGELOG.md for the latest major version (2.x now), and having CHANGELOG-v1.md so they can evolve separately? and we don't need to decide how to merge 1.x and 2.x version changelogs together
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.
no strong opinion here. My idea was to keep both branches CHANGELOG updated with all versions. Open to alternatives
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.
let's discuss offline
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.
LGTM
Description
This should have happened automatically when releasing 1.41.1 but was done in the wrong branch, master. Fixed in #3734 and this brings the changes into master-v1.
Link to any related issue(s):
Type of change:
Required Checklist:
Further comments