2 files changed, 4 insertions(+), 5 deletions(-)

M CONTRIBUTING.md
M Project.toml

@@ 86,6 86,9 @@ so stable releases might skip a few tags.
 Online documentation is only built for stable versions,
 so releasing stable versions requires administrator access to the online GitHub repository.
 
+The provided pre-commit hook script can be used to verify the last git tag
+against `Project.toml`.
+
 ### Releasing a new version on `next` (unstable)
 
 1. Update `Project.toml` with the new version number.


@@ 99,10 102,6 @@ so releasing stable versions requires administrator access to the online GitHub 
 9. Create an annotated git tag with `git tag -am "Version <version>" v<version>`.
 10. Push `next` to all remotes (with `--follow-tags`).
 
-Some of the above steps are automated in `tools/make-next.jl`.
-The script requires [ArgParse.jl](https://github.com/carlobaldassi/ArgParse.jl) and
-[JuliaFormatter](https://github.com/domluna/JuliaFormatter.jl).
-
 ### Releasing a new version on `main` (stable)
 
 Once a release is considered stable enough, it can be merged onto `main` from `next`.

@@ 1,7 1,7 @@
 name = "PlateMotionRequests"
 uuid = "d13234e1-ff52-466f-9770-1615bbbda812"
 authors = ["adigitoleo <adigitoleo@dissimulo.com>"]
-version = "2.0.2"
+version = "3.0.0"
 
 [deps]
 DataStructures = "864edb3b-99cc-5e75-8d2d-829cb0a9cfe8"