Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion docs/updating-go-version.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,24 @@
Each major Go release is supported until there are two newer major releases. When a Go release reaches it end of life,
we should remove support for it in jsii. To do this, you have to:

## 1. Update jsii/superchain

- Update the `GO_VERSION` in the [Dockerfile](https://github.com/aws/jsii-superchain/blob/main/superchain/Dockerfile#L87)

## 2. Update `cdk init` template

- Needs to be updated to the new version, so that new apps declare their minimum requirements correctly.
- See example [PR](https://github.com/aws/aws-cdk-cli/pull/768)s

## 3. Update @jsii/go-runtime and jsii repo

- Update the baseline version of Go in `.github/workflows/main.yml`.
- Update `packages/@jsii/go-runtime/jsii-runtime-go/go.mod`
- Update the value of the `GO_VERSION` constant in `packages/jsii-pacmak/lib/targets/go/package.ts`. Don't forget to
also update the `jsii-pacmak` jest snapshots.
- Update `packages/@jsii/go-runtime-test/project/go.mod`.
- Update `packages/@jsii/go-runtime-test/project/go.mod`.

## 4. Update jsii-pacmak in aws-cdk-lib (Automatic)

Eventually the above updates will be released and the jsii-pacmak version in `aws-cdk-lib` will be updated automatically.
This should now pass the canaries and everything is completed.
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
# package (wheel, sdist), but not declared as build-system dependencies.

setuptools~=75.3.2 # build-system
build~=1.2.2.post1 # build-system
build~=1.3.0 # build-system

twine~=6.1.0

Expand Down

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading