chore: npm-check-updates and yarn upgrade

[MrArnoldPalmer]

Upgrade dependency versions when available. Change the yarn-upgrade
workflow to only upgrade minor versions automatically. This will prevent
major version dependency upgrades from happening automatically in the
future.

Exclude aws-sdk from automatic upgrades temporarily due to changes in
TS type definitions that removed ConfigurationOptions from the
aws-sdk/lib/config entrypoint. See
aws/aws-sdk-js#3453 for details.

---

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

[eladb]

This will cause unsolicited major upgrades to dependencies

[iliapolo]

@MrArnoldPalmer Is this PR supposed to resolve the security alert? Because an old version of yargs-parser will still be mentioned in the lock file.

Its coming from an old dependency on yargs coming from the make-runnable dependency in prlint.

[MrArnoldPalmer]

@MrArnoldPalmer Is this PR supposed to resolve the security alert? Because an old version of yargs-parser will still be mentioned in the lock file.

Its coming from an old dependency on yargs coming from the make-runnable dependency in prlint.

Removed make-runnable dependency as discussed.

This will cause unsolicited major upgrades to dependencies

@eladb was this referring to the auto-updates in the yarn-upgrade workflow? Or does this refer to the dependencies that are upgraded to a new major version in this PR?

The majority of dependencies with a new major version are devDependencies, all of the runtime dependencies receiving an upgraded version aren't exposed on public APIs.

The exception here is Jest, which is a peer-dependency in @monocdk-experiment/assert. It is only declared as a peerDep in the monocdk version of assert, its a devDependency in @aws-cdk/assert. So this may cause users to get the "peerDependency jest doesn't satisfy version x.x.x" warning when using monocdk-experiment, but shouldn't break them. Do you think excluding the Jest MV upgrade is prudent in this case?

Revised

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
• Commit ID: 73f18c6
• 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).