Pushing a new Release

Preparing a Release

Before releasing there are a few boxes to tick off.

  • [ ] Is there a milestone plan for the release? If so, has it been updated?
  • [ ] Is the changelog up to date? (Look at commit history to verify.)
    • [ ] Chronological order is fine.
  • [ ] Does the AUTHORS file need updating?
  • [ ] Spot check new lint rules for naming consistency. Rename as needed.

Doing the Push

First, make sure the build is GREEN.

Build Status

All clear? Then:

  1. Update pubspec.yaml with a version bump and CHANGELOG.md accordingly.
  2. Tag a release branch.
  3. Publish to pub.dev (dart pub lish); heed all warnings that are not test data related!
  4. Update SDK DEPS.

You're done!

Updating documentation

Documentation on https://dart-lang.github.io/linter/ is located on the gh-pages branch and automatically updated as changes are made to the main branch.

To update the dart.dev linter rules documentation, you need to manually update the file its generated from:

  1. Download the automatically generated rules.json file.
  2. Rename the downloaded file to linter_rules.json.
  3. Clone and/or open the site-www repository, creating a new branch for your changes.
  4. Replace the old linter_rules.json with the newly downloaded version and commit your changes.
  5. Submit your changes in a pull request with an overview of what has changed, such as what version of the linter these changes are tied to.