-
Notifications
You must be signed in to change notification settings - Fork 329
Release checklist
Dave Herman edited this page Apr 17, 2019
·
24 revisions
This is Dave's manual process for now. This should all be automated.
Update ./RELEASES.md with a new entry. Add a bullet item for every user-facing PR that has been merged since the last release.
Update ./Cargo.toml to have the new version in the version field.
Commit this change with a commit message "v$version" where $version is the new version.
Push and make sure CI passes.
On linux host:
git pull
cargo build --release
./dev/unix/build.sh release
gzip -9 dev/unix/install.sh
cd dev/unix
scp install.sh.gz dherman-mn1.linkedin.biz:install.sh.gz
On laptop:
mv ~/install.sh.gz ./
gunzip install.sh.gz
mv install.sh notion-$VERSION-linux-openssl-$OPENSSLVERSION.sh
git pull
cargo build --release
./dev/unix/build.sh release
mv dev/unix/install.sh ./notion-$VERSION-macos.sh
- Draft a new release
- name: "v$VERSION", tag_name: "v$VERSION"
- check prerelease
- upload the two shell scripts
- click publish
- update the
latest-versionin https://github.com/notion-cli/www to $VERSION (without the leading 'v')
curl -sSLf https://get.notionjs.com | bash- open new terminal
-
notion versionshould report the new$VERSION