diff options
| author | bryan newbold <bnewbold@robocracy.org> | 2023-11-30 17:24:25 -0800 |
|---|---|---|
| committer | bryan newbold <bnewbold@robocracy.org> | 2023-11-30 17:24:25 -0800 |
| commit | ec223a407b52a3d34dbeda3902b04a89c8d1d105 (patch) | |
| tree | fdcac526e8d2f86e22f70f007b6180c19defe98d | |
| parent | 257f56ff0c0688eaf201f56bdaad8b329d62cc10 (diff) | |
| download | adenosine-main.tar.gz adenosine-main.zip | |
more specific release notesmain
| -rw-r--r-- | extra/HOWTO_release.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/extra/HOWTO_release.md b/extra/HOWTO_release.md index 1631484..395c078 100644 --- a/extra/HOWTO_release.md +++ b/extra/HOWTO_release.md @@ -11,7 +11,10 @@ final prep: - ensure working directory is clean (no edits, even if unrelated to code changes) push/tag/etc: -- when project is ready to share on crates.io, do: push to crates.io: `cargo publish -p adenosine-cli`, `cargo publish -p adenosine-pds`, `cargo publish -p adenosine` +- when project is ready to share on crates.io, push: + => `cargo publish -p adenosine` + => `cargo publish -p adenosine-cli` + => `cargo publish -p adenosine-pds` => add `--allow-dirty` if you have local "untracked" git files (and are confident!), and even `--no-verify` (if very confident!) => usually want to do this before git tag in case validation details come up - create a git tag: `git tag vX.Y.Z -a -s -u bnewbold@robocracy.org -m "release X.Y.Z"` |