chore(release): 1.31.0 #6972
Closed
chore(release): 1.31.0 #6972
Conversation
This file contains 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
Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.640.0 to 2.641.0. - [Release notes](https://github.com/aws/aws-sdk-js/releases) - [Changelog](https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md) - [Commits](aws/aws-sdk-js@v2.640.0...v2.641.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.641.0 to 2.642.0. - [Release notes](https://github.com/aws/aws-sdk-js/releases) - [Changelog](https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md) - [Commits](aws/aws-sdk-js@v2.641.0...v2.642.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
chore: do not announce CDK releases in awscdkio (#6800) So long as the AWS CDK has over 150 modules, tweeting about each new version when new releases come out is extremely spammy. The construct catalog will respect a [stanza](https://github.com/construct-catalog/catalog/pull/22) in package.json that indicates that a module wishes to opt-out from the announcement (it will still be rendered and available under awscdk.io). Fixes construct-catalog/catalog#24
It's `preBuild` not `prebuild`. See https://docs.aws.amazon.com/amplify/latest/userguide/build-settings.html Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Avoid confusion about the default value. Fixes #6694.
Co-authored-by: Rico Huijbers <rix0rrr@gmail.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* chore(cli): convert the bootstrap template from JSON to YAML. This allows us to add comments to the template, which make it clearer why certain things (most noticeably, permissions) are required. While I was in the area, fixed a small issue with the bootstrap integ test (the test app wasn't respecting the env the bootstrap stack was created in). * Reuse YAML parsing routines we already have Co-authored-by: Rico Huijbers <rix0rrr@gmail.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Bumps [fs-extra](https://github.com/jprichardson/node-fs-extra) from 8.1.0 to 9.0.0. - [Release notes](https://github.com/jprichardson/node-fs-extra/releases) - [Changelog](https://github.com/jprichardson/node-fs-extra/blob/master/CHANGELOG.md) - [Commits](jprichardson/node-fs-extra@8.1.0...9.0.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
When building a NodejsFunction via the aws-lambda-nodejs package, a build directory and cache directory are automatically created when your function is built. These files should not be checked into your repository, as they are temporary build artifacts. You can configure the location of these directories by passing `buildDir` or `cacheDir` in your NodejsFunctionProps. https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-lambda-nodejs.NodejsFunctionProps.html#properties Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
This review adds a basic check to not try and validate unresolved tokens when performing validation for the `DnsValidatedCertificate` construct. fixes #6133 Co-authored-by: Reed Hermes <hermesr@amazon.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* clean commit * add usage example * update package.json * remove jest from package.json * add more tests * minor syntax update * add more tests * fix issues * update package.json * add more tests and fix package.json format error * update package.json * update package.json * fix issues from the review * update README * rename EnvironmentEc2 to Ec2Environment * revert yarn.lock * revert * fix subnetSelection syntax * fix json syntax error Co-authored-by: Adam Ruka <adamruka@amazon.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Reuse of the same metric ID was already checked upon construction of the `MathExpression` instance and so we thought this error couldn't occur. However, reuse can also occur (and is also prohibited) between different `MathExpression`s, even on different axes. Make the error message describe the situation in a way that is actionable.
* chore: upgrade jsii to v1.1.0 * fix: cast unknown types in core tests Due to a typescript version upgrade in JSII, types in tests in @aws-cdk/core no don't match. It looks like this is due to the following breaking change. https://github.com/microsoft/TypeScript/wiki/Breaking-Changes#generic-type-parameters-are-implicitly-constrained-to-unknown It isn't immediately apparent if we can workaround this without explicitly casting in this way. * Update test diffs * chore: upgrade constructs to v2.0.0 * update integ test expectations
Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.642.0 to 2.643.0. - [Release notes](https://github.com/aws/aws-sdk-js/releases) - [Changelog](https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md) - [Commits](aws/aws-sdk-js@v2.642.0...v2.643.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* fix(aws-ecs-patterns): only create an A record if LB is public Before this change, we unnecessarily create A record when the load balancer(s) is non public-facing. This commit fixes #6702. * Added tests * Moved these 2 lines back to where they were
Bumps [yaml](https://github.com/eemeli/yaml) from 1.8.2 to 1.8.3. - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v1.8.2...v1.8.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
* fix(dam): immutable role cannot be used as a construct Due to a change in how `ConstructNode`s are associated with `Construct`s in 1.29.0, `ImmutableRole`'s "impersonation to a construct" -- by reflecting the construct's `node` property -- no longer works. This change simply turns `ImmutableRole` into a real construct by extending the `Construct` base class. This fixes the use case in #6885 * memoize immutable role so it can be called any number of times
…etcoreapp (#6941) * fix(cli): init templates for c# and f# use unsupported version of netcoreapp * remove package-lock
…5.0 (#6946) Bumps [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) from 2.24.0 to 2.25.0. - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v2.25.0/packages/eslint-plugin) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.643.0 to 2.644.0. - [Release notes](https://github.com/aws/aws-sdk-js/releases) - [Changelog](https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md) - [Commits](aws/aws-sdk-js@v2.643.0...v2.644.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
BREAKING CHANGE: .NET Core v3.1 is required with JSII v1.1 Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* docs(stepfunctions): Add snippet for Map state Closes #5736 * address PR feedback * address PR feedback * add link to Step Functions documentation * add backticks to map and parallel in readme Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* add initial tests and constructure for batch job target * add comments * roll other pr into this one: * Add experimental and remove yarn.lcok * fix tests and update event target * reset yarn.lock * remove changes to yarn.lock * revert yarn.lock * fix yarn.lock * add another readme update * fix value setters * Update batch.ts * fix test * fix integ test * update tests * Update package.json Co-authored-by: Rico Huijbers <rix0rrr@gmail.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Prior v1.29.0, the context passed to the docker build command was always the current working directory. In v1.29.0, this was changed to be the directory the user passed when instantiating the asset. However, docker doesn't respect the context passed to the build command when the `--file` argument is also passed. This broke assets for users passing the `file` prop when constructing a `DockerImageAsset`. This is fixed by changing the current working directory of the `docker build` command and passing that context as `.`. Then docker uses the current working directory as the context and correctly finds the image definition file from the `file` prop. An existing integration test in the framework covers this case, but does not fail unless the stack is deployed fresh since the asset isn't rebuilt when the hash is not changed. Fix: #6954 #6814
…oy (#6938) A couple of changes - - `emailVerificationMessage` and `emailVerificationSubject` properties are not set when link-style verification is used. This is root cause for the error message reported by the user. - The defaults `emailBody` and `emailSubject` are modified when link-style verification is used. They will now correctly contain the template placeholder `{##Verify Email##}`. - Validations are now added that email and SMS verification messages have the mandatory placeholders. fixes #6811
RomainMuller
suggested changes
Mar 24, 2020
Comment on lines
+8
to
+11
| ### Bug Fixes | ||
|
|
||
| * **cognito:** user pool - link style email verification fails to deploy ([#6938](https://github.com/aws/aws-cdk/issues/6938)) ([b5c60d5](https://github.com/aws/aws-cdk/commit/b5c60d50a6c4fb7e93185c5874a2651ba40d0247)), closes [#6811](https://github.com/aws/aws-cdk/issues/6811) | ||
|
|
There was a problem hiding this comment.
This fails to mention a lot of things.... Including
fix(cdk-assets): context path not honored by Docker asset build (#6957)
This is kinda puzzling.
There was a problem hiding this comment.
Ohhh this could be my bad, in fact... I'm going to try and re-generate this.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
see CHANGELOG