chore(prlint): add exempt label to breaking change on stable modules#18102
Merged
mergify[bot] merged 2 commits intoaws:masterfrom Dec 21, 2021
kaizencc:conroy/linter
Merged
chore(prlint): add exempt label to breaking change on stable modules#18102mergify[bot] merged 2 commits intoaws:masterfrom kaizencc:conroy/linter
mergify[bot] merged 2 commits intoaws:masterfrom
kaizencc:conroy/linter
Conversation
|
|
Contributor
Author
|
If this PR is accepted then I will create the necessary label. |
Collaborator
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Contributor
|
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
TikiTDO
pushed a commit
to TikiTDO/aws-cdk
that referenced
this pull request
Feb 21, 2022
…ws#18102) This PR introduces a proposed new label, `pr-linter/exempt-breaking-change` that, when added, circumvents the check that asserts stable modules do not have breaking changes. Motivation: A situation like aws#18027 where we have are willing to accept a functional breaking change to a stable module. The regular `allowed-breaking-changes.txt` file does not work here, since there is no breaking change to the API. We want to be able to document the breaking change, but by documenting we alert `prlint` that we are breaking a stable module. Counterargument: Functional breaking changes were explicitly banned in aws#14861. From the PR description: "The CDK must be more strict on preventing such changes and the impact due to their perception." I also added some "manual linting" to the file myself since it was bothering me, and now it muddies the diff. Sorry! ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a proposed new label,
pr-linter/exempt-breaking-changethat, when added, circumvents the check that asserts stable modules do not have breaking changes.Motivation: A situation like #18027 where we have are willing to accept a functional breaking change to a stable module. The regular
allowed-breaking-changes.txtfile does not work here, since there is no breaking change to the API. We want to be able to document the breaking change, but by documenting we alertprlintthat we are breaking a stable module.Counterargument: Functional breaking changes were explicitly banned in #14861. From the PR description: "The CDK must be more strict on preventing such changes and the impact due to their perception."
I also added some "manual linting" to the file myself since it was bothering me, and now it muddies the diff. Sorry!
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license