Skip to content
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

feat(node)!: default to node16 and remove jsii/superchain from workflows #2510

Merged
merged 1 commit into from Mar 21, 2023

Conversation

mrgrain
Copy link
Contributor

@mrgrain mrgrain commented Mar 15, 2023

BREAKING CHANGE: default to node16
To use any other Node version, explicitly provide the desired version number

BREAKING CHANGE: remove jsii/superchain image from AwsCdkConstructLibrary workflows
Using the jsii/superchain image provides no tangible benefit over installing dependencies with GitHub Actions. However AWS CDK Constructs often require to run docker commands, and thus using the image forces GitHub Action to exectute commands as Docker in Docker. This is does not work in many situations and generic fixes are not reliable (see #2094 & aws/aws-cdk#8799). Additionally the existing build and package workflows had an inconsistent usage of the image, causing more problems.

To restore the old behavior, set options.workflowContainerImage to the desired image.

Fixes #2094
Closes #1065


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

@mrgrain mrgrain changed the title feat(node)!: default to node16 and do not use jsii/superchain image… feat(node)!: default to node16 and remove jsii/superchain from workflows Mar 15, 2023
@mrgrain mrgrain force-pushed the mrgrain/feat/node-16-no-superchain branch from 699778c to f8f32c6 Compare March 15, 2023 13:40
… in workflows

BREAKING CHANGE: default to node16
To use any other Node version, explicitly provide the desired version number

BREAKING CHANGE: remove `jsii/superchain` image from AwsCdkConstructLibrary workflows
Using `jsii/superchain` provides no tangible benefit over installing dependencies with GitHub Actions.
However because AWS CDK Constructs often require to run docker commands, with image GitHub Action workflows end up attempting to run Docker in Docker.
This is not trivial to achieve (see #2094 & aws/aws-cdk#8799).
Additionally the existing build and package workflows had an inconsistent usage of the image, causing further problems.

To restore the old behavior, set `options.workflowContainerImage` to the desired image.

Fixes #2094
Closes #1065
@mrgrain mrgrain marked this pull request as ready for review March 21, 2023 17:51
@mrgrain mrgrain force-pushed the mrgrain/feat/node-16-no-superchain branch from f8f32c6 to d303e2d Compare March 21, 2023 17:51
Copy link
Contributor

@kaizencc kaizencc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yay!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants