You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today we use chronicle to generate release notes based off of labels on PRs and issues. It would be great to add automation that can auto-label PRs with schema-specific changes. Take for instance this PR https://github.com/anchore/syft/releases/tag/v0.85.0 .
The breaking-change label was manually added to the #1846 but could have been automatically added by automation when a new JSON schema file was added in schema/json and compared the new version to the last version. Adding both the breaking-change and something that indicates the json schema was changed such as a new new-json-schema would be nice. With some changes to chronicle we could add another section that denotes the specific changes that changed the json schema.
The text was updated successfully, but these errors were encountered:
Today we use chronicle to generate release notes based off of labels on PRs and issues. It would be great to add automation that can auto-label PRs with schema-specific changes. Take for instance this PR https://github.com/anchore/syft/releases/tag/v0.85.0 .
The
breaking-change
label was manually added to the #1846 but could have been automatically added by automation when a new JSON schema file was added inschema/json
and compared the new version to the last version. Adding both thebreaking-change
and something that indicates the json schema was changed such as a newnew-json-schema
would be nice. With some changes to chronicle we could add another section that denotes the specific changes that changed the json schema.The text was updated successfully, but these errors were encountered: