Document crate and changelog updates
@@ -8,19 +8,24 @@ The Bash script in the root of the project, named `publish.sh` can be used to pu
Make sure that you are are starting from a clean working directory for both `dev` and `master`, completely up to date with remote and all local changes either committed and pushed or stashed.
+Note that the script will update the crates and lockfile, so in case you did not do so before, you really should to make sure none of the dependencies introduce some SemVer breaking change. Then commit so you again have a clean working directory.
+
+Also don't forget to update `CHANGELOG.md` with the version number, release date, and at the bottom the comparison links.
+
You will want to perform a dry run first: `./publish --dry-run 0.1.0`. Please make note of any errors or warnings. In particular, you may need to explicitly inform Git which remote you want to track for the `master` branch like so: `git --track origin/master` (or whatever you have called the `librespot-org` remote `master` branch).
Depending on your system the script may fail to publish the main `librespot` crate after having published all the `librespot-xyz` sub-crates. If so then make sure the working directory is committed and pushed (watch `Cargo.toml`) and then run `cargo publish` manually after `publish.sh` finished.
-To publish the crates your GitHub account needs to be authorized on `crates.io` by `librespot-org`.
+To publish the crates your GitHub account needs to be authorized on `crates.io` by `librespot-org`. First time you should run `cargo login` and follow the on-screen instructions.
## What the script does
This is briefly how the script works:
- Change to branch master, pull latest version, merge development branch.
- - CD to working dir.
+ - Change to working directory.
- Change version number in all files.
+ - Update crates and lockfile.
- Commit and tag changes.
- Publish crates in given order.
- Push version commit and tags to master.
