Update release script to not run "just check"
This commit is contained in:
@@ -5,7 +5,7 @@ remotes and then run `./release (major|minor|patch)`. It will handle a
|
|||||||
git-flow-y release, meaning that it will perform a merge from `develop` to
|
git-flow-y release, meaning that it will perform a merge from `develop` to
|
||||||
`master`, create a git tag, sync all remotes and run `cargo publish`.
|
`master`, create a git tag, sync all remotes and run `cargo publish`.
|
||||||
|
|
||||||
The release script will also run `just check` to make sure that nothing it
|
Make sure to run `just check` before releasing to make sure that nothing is
|
||||||
broken.
|
broken.
|
||||||
|
|
||||||
As GRM is still `v0.x`, there is not much consideration for backwards
|
As GRM is still `v0.x`, there is not much consideration for backwards
|
||||||
@@ -17,7 +17,7 @@ dependencies](./dependency_updates.md). As `./release.sh patch` is exposed as a
|
|||||||
Justfile target (`release-patch`), it's possible to do both in one step:
|
Justfile target (`release-patch`), it's possible to do both in one step:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
$ just update-dependencies release-patch
|
$ just update-dependencies check release-patch
|
||||||
```
|
```
|
||||||
|
|
||||||
## Release notes
|
## Release notes
|
||||||
|
|||||||
@@ -94,8 +94,6 @@ if ((changes == 0)); then
|
|||||||
exit 1
|
exit 1
|
||||||
fi
|
fi
|
||||||
|
|
||||||
just check
|
|
||||||
|
|
||||||
sed -i "0,/^version/{s/^version.*$/version = \"${new_version}\"/}" Cargo.toml
|
sed -i "0,/^version/{s/^version.*$/version = \"${new_version}\"/}" Cargo.toml
|
||||||
|
|
||||||
cargo update --package git-repo-manager --precise "${new_version}"
|
cargo update --package git-repo-manager --precise "${new_version}"
|
||||||
|
|||||||
Reference in New Issue
Block a user