rei-mirrors/Fornjot
1
0
Fork 0
mirror of https://github.com/hannobraun/Fornjot synced 2025-06-16 00:08:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update doc references to release-operator folder

Browse Source
This commit is contained in:
Hanno Braun 2022-04-13 15:54:36 +02:00
parent 55e383132e
commit 5e8e264686
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
RELEASES.md
View File

@ -47,7 +47,7 @@ In the release branch, update the version numbers in the `Cargo.toml` files of a
Push the release branch and create a pull request and label it as `release`. Once the CI build completed successfully, merge the pull-request and mention the new version in the commit, e.g. `Release v0.1.2`.
The [release-operator](./release-operator) will run in the scope of GitHub Actions' [CD](./.github/workflows/cd.yml) workflow. It will yield a set of compiled binaries, their checksums and a new GitHub Release with all artifacts attached.
The [release-operator](./tools/release-operator) will run in the scope of GitHub Actions' [CD](./.github/workflows/cd.yml) workflow. It will yield a set of compiled binaries, their checksums and a new GitHub Release with all artifacts attached.
Next, publish the release by running `cargo publish` for each crate.

4
tools/release-operator/README.md
View File

@ -55,7 +55,7 @@ As seen above, the release operator requires the maintainer to:
### Detect a Release
```shell
# release-operator/
# tools/release-operator/
cargo run -- detect --sha <commit-sha> --label <release-label>
```
@ -113,7 +113,7 @@ The release operator defines "outputs" which can be read by subsequent steps wit
### Publish a List of Crates
```shell
# release-operator/
# tools/release-operator/
cargo run -- publish \
--token <crates.io-token> \
--crate ../fj \