chore(batch): include breaking change in previous PR

[iliapolo]

This is a "dummy" PR so that our next release will include the breaking change notice from this, previous PR: #6549

The reason it wasn't picked up in the original PR is because mergify takes the content between ## Commit Message and the next markdown header, and i didn't notice the breaking change notice falls outside of the proper section.

Since this PR is a chore, it won't end up in the release notes except from the breaking change notice, which, according to conventional commits, is respected with any commit type

Commit Message

chore(batch): include breaking change in previous PR (#6621)

BREAKING CHANGE: the allocationStrategy property was moved from ComputeEnvironmentProps to the ComputeResources interface, which is where it semantically belongs.

End Commit Message

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
• Commit ID: e8596d3
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[eladb]

Would that work? Wouldn’t the change log generator ignore this since it’s a “chore”?

[iliapolo]

@eladb From the conventional commits spec:

BREAKING CHANGE: a commit that has the text BREAKING CHANGE: at the beginning of its optional body or footer section introduces a breaking API change (correlating with MAJOR in semantic versioning). A BREAKING CHANGE can be part of commits of any type.

Should work...

[mergify]

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).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
• Commit ID: d17926d
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

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).