-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(merge-back): 1.199.0 #24893
chore(merge-back): 1.199.0 #24893
Conversation
…) (#24829) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
See CHANGELOG https://github.com/aws/aws-cdk/blob/patch/v1.198.1/CHANGELOG.md ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork). |
Reverts #24893 The merge back mistakenly bumped to version `1.199.0` even though the release associated with it was for `1.198.1`. It happened because th `1.199.0` release got triggered before `1.198.1` finished, and the merge back build reads the current version from the latest `v1-release` branch, instead of the commit that triggered it. Long story short, the [latest v1 version](https://www.npmjs.com/package/aws-cdk?activeTab=versions) is `1.198.1`, so thats what we should have in the code.
See CHANGELOG