Note: If you need to publish a new version of devtools_server, you will need to do that prior to performing these steps, and update the devtools pubspec.yaml to reference the new published version of devtools_server. To publish devtools_server, run pub publish
from packages/devtools_server
. Be sure to test the server locally before publishing. For instructions on how to do that, see CONTRIBUTING.md.
Create a branch for your release. Below we're creating release 0.0.15, with all the PRs.
cd ~/devtools-git/devtools checkout master git pull upstream master git checkout -b release_0_0_15
./tool/update_version.sh 0.0.15
Verify that this script updated the pubspecs under packages/ and updated all references to those packages. These packages always have their version numbers updated in lock step so we don't have to worry about versioning. Also make sure that the version constant in packages/devtools_app/lib/devtools.dart was updated.
Add the release number and date followed by the features or changes e.g.,
## 0.0.15 - 2019-04-01 * Added a great feature ...
git commit -a -m “Prepare for v0.0.15 release.” git push origin release_0_0_15
From the git UI tool create the PR, squash and commit.
Ensure that the tip of master is the above commit, just made with the exact set of PRs wanted. Otherwise, checkout using the SHA1 of the above commit e.g.,
git checkout -b release_15 <SHA1>
then proceed to the step ‘Prep to publish’.
cd ~/devtools-git/devtools git checkout master git pull upstream master
./tool/publish.sh
cd packages/devtools dart bin/devtools.dart
./tool/pub_publish.sh
git checkout .gitignore git checkout packages/*/pubspec.yaml
This script will automatically determine the version from the packages/devtools/pubspec.yaml
so there is no need to manually enter the version.
tool/tag_version.sh