| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This pull request abridges the release notes to improve their display on the releases page and in Dependabot version updates. The changes remove redundant information and add helpful links to bundle releases.
Changes:
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/script/prepare_changelog.py | Simplified changelog extraction logic to exclude version headings and footer text, making release notes more concise |
| .github/workflows/script/bundle_changelog.py | Added bundle release URL linking to provide users with direct access to CLI and language pack changes |
Sorry, something went wrong.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Sounds reasonable. For completeness, could you paste your local example? I don't think you need to loop Product in.
Sorry, something went wrong.
There was a problem hiding this comment.
One minor comment, otherwise ok.
Sorry, something went wrong.
|
Example bundle release note: Example Action release note (the same): |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Abridge release notes so they display better on the releases page and in Dependabot version updates.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Affects the release process only.
How did/will you validate this change?
Tested locally.
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Check the release notes during the next bundle and Action release.
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist