[DO NOT MERGE] Test PR to try to add automated PR comments by DaveTryon · Pull Request #884 · microsoft/sbom-tool (original) (raw)

DaveTryon changed the title[DO NOT MERGE} Test PR to try to add automated PR comments [DO NOT MERGE] Test PR to try to add automated PR comments

Jan 21, 2025

You touched the API project--how does this impact the API version?

You touched the API project. Did you change any of the API interfaces in any way? If so, this is an API-breaking change. Please be sure you do the following:

1. Bump the major version in the next release
2. Update the documentation to show the new functionality

DaveTryon deleted the DaveTryon/try-action-pr-comments branch

January 22, 2025 01:21

DaveTryon restored the DaveTryon/try-action-pr-comments branch

January 22, 2025 17:22

This PR changes files in the API project. Does it change any of the API interfaces in any way? Please note that this includes the following types of changes:

• Changing the signature of an existing interface method
• Adding a new method to an existing interface
• Adding a required data member to a class that an existing interface method consumes

Because any of these changes can potentially break a downstream consumer with customized interface implementations, these changes need to be treated as breaking changes. Please do one of the following:

Option 1 - Publish this as a breaking change

1. Update the documentation to show the new functionality and/or explain the change
2. Bump the major version in the next release
3. Be sure to highlight the breaking changes in the release notes

Option 2 - Refactor the changes to be non-breaking

1. Review this commit, which adds a new interface in a backward-compatible way
2. Refactor the change to follow this pattern so that existing interfaces are left completely intact
3. Bump the minor version in the next release

This PR changes files in the API project. Does it change any of the API interfaces in any way? Please note that this includes the following types of changes:

• Changing the signature of an existing interface method
• Adding a new method to an existing interface
• Adding a required data member to a class that an existing interface method consumes

Because any of these changes can potentially break a downstream consumer with customized interface implementations, these changes need to be treated as breaking changes. Please do one of the following:

Option 1 - Publish this as a breaking change

1. Update the documentation to show the new functionality and/or explain the change
2. Bump the major version in the next release

Option 2 - Refactor the changes to be non-breaking

1. Review this commit, which adds a new interface in a backward-compatible way
2. Refactor the change to follow this pattern so that existing interfaces are left completely intact
3. Bump the minor version in the next release

DaveTryon deleted the DaveTryon/try-action-pr-comments branch

January 22, 2025 18:27

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})