Updating to new SDK releases

This page covers the procedures you might not remember to do when a new Dart SDK comes out.

What (not) to do

Obviously, you might to need to update text and examples to reflect the new release. Here's what else you need to do:

• Once the stable build is uploaded, update the checksum values in the Dockerfile following the Dart SDK and Node PPA Checksum values instructions.
• Update the What's new and Language evolution pages
• Update the SDK version in src/_data/pkg-vers.json. The SDK version is visible in https://dart.dev/tools/sdk and used in links to API docs (via {{site.data.pkg-vers.SDK.channel}}. For an example, see PR #2462.

You might also want to do the following:

• Add a banner to point to the release announcement. For an example of adding the banner, see PR #1234.
• If necessary, update the min SDK in examples' pubspec.yaml files.
• Update the Wikipedia page to display the new release number.

Consider NOT updating the following:

• The SDK version used by repo tools. This is controlled by the topmost pubspec.yaml. Unless you're updating the tools, there's no need to update this.

Testing a proposed SDK release

1. Verify you have updated the checksums as outlined in the Dart SDK and Node PPA Checksum values instructions.

2. From the root directory, run the build with tests:

   $ make test