Tags: kaiz-io/aws-cdk
Tags
chore(release): 2.0.0-rc.33 (aws#17734) * chore: fix build break caused by exported deprecated functions (aws#17719) Functions (not member methods) aren't acknowledged by jsii, so they are not stripped out of the compiled source, even when deprecated. These two functions are deprecated and reference deprecated interfaces. When running the init template tests against JS/TS, the tests fail with: ``` node_modules/aws-cdk-lib/aws-elasticloadbalancingv2/lib/alb/application-listener-rule.d.ts(110,62): error TS2304: Cannot find name 'FixedResponse'. node_modules/aws-cdk-lib/aws-elasticloadbalancingv2/lib/alb/application-listener-rule.d.ts(116,68): error TS2304: Cannot find name 'RedirectResponse'. ``` By -- on v2 only -- un-exporting the functions and inlining them in their secondary usages, we can effectively "strip" these functions from the JS/TS. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license* * chore: duplicate enum values not usable (aws#17731) There is an outstanding bug with `jsii` (aws/jsii#2782) where duplicate enum values are not available to the non-JS/TS languages. In these cases, only the first enum value defined is present in the assembly. For these cases, the first value was the deprecated one. This meant that only the deprecated values were present, and once we stripped the deprecated elements, we were left without values. For *v2 only*, we can reorder these enums so the non-deprecated values appear in the assembly. Note that we *cannot* backport this to `master` (v1), because it would introduce breaking changes to our Java/Go/Dotnet/Python customers. * chore(release): 2.0.0-rc.33 Co-authored-by: Nick Lynch <nlynch@amazon.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: AWS CDK Team <aws-cdk@amazon.com>
chore: fix build break caused by exported deprecated functions (backp… …ort aws#17719) (aws#17720) This is an automatic backport of pull request aws#17719 done by [Mergify](https://mergify.com). --- <details> <summary>Mergify commands and options</summary> <br /> More conditions and actions can be found in the [documentation](https://docs.mergify.com/). You can also trigger Mergify actions by commenting on this pull request: - `@Mergifyio refresh` will re-evaluate the rules - `@Mergifyio rebase` will rebase this PR on its base branch - `@Mergifyio update` will merge the base branch into this PR - `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch Additionally, on Mergify [dashboard](https://dashboard.mergify.com/) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.com </details>
chore(release): 2.0.0-rc.31 (aws#17662) See [CHANGELOG](https://github.com/aws/aws-cdk/blob/bump/2.0.0-rc.31/CHANGELOG.md)
chore(release): 2.0.0-rc.30 (aws#17535) See [CHANGELOG](https://github.com/aws/aws-cdk/blob/bump/2.0.0-rc.30/CHANGELOG.md)
chore(release): 2.0.0-rc.29 (aws#17445) See [CHANGELOG](https://github.com/aws/aws-cdk/blob/bump/2.0.0-rc.29/CHANGELOG.md)
chore(release): 2.0.0-rc.28 (aws#17428) See [CHANGELOG](https://github.com/aws/aws-cdk/blob/bump/2.0.0-rc.28/CHANGELOG.md)
PreviousNext