Commit `c8b514e1a0`

c8b514e1a0324d0af4db0fe528d76e829f9fe106

parent: f072e4aaa7

Verified · cmc

cmc <hello@cleberg.net> · 2026-08-30 07:14 UTC

Describe the release process the repository actually has

`RELEASING.org` described a GitHub-native repository. `origin` is gitbay, and the
release only works because gitbay push-mirrors to `github.com/krazywarez/orgo`,
tags included — a fact the document did not mention and the whole process
depends on. It now says where the repository lives, that `gh` talks to the
mirror, and that neither forge runs the tests, since `ci.yml` was removed and
there is no `.gitbay/ci.yml`.

Two steps were missing: the tag-vs-Cargo.toml check the build performs, and
releasing on gitbay, which has no automation and needs the notes and binaries by
hand.

`Cargo.toml`'s `repository` pointed at the mirror rather than at the repository,
as did the `git clone` line in the README and the install guide.

Two comments claimed CI checks the MSRV on every change. Nothing checks it now.

Layout: unified · split

Cargo.toml +4 −5

 # crates.io caps a keyword at 20 characters, which "static-site-generator" is not.
 keywords = ["org-mode", "static-site", "ssg", "emacs", "blog"]
 categories = ["command-line-utilities", "text-processing"]
-repository = "https://github.com/krazywarez/orgo"
+repository = "https://gitbay.org/krz/orgo"
 homepage = "https://krazywarez.github.io/orgo/"
-# The compiler floor, checked in CI rather than assumed. orgo's own code needs 1.82
+# The compiler floor. orgo's own code needs 1.82 (`Option::is_none_or`); the floor is
-# (`Option::is_none_or`); the floor is 1.88 because dependencies in Cargo.lock declare it
+# 1.88 because dependencies in Cargo.lock declare it — `plist` and `time`, both by way of
-# — `plist` and `time`, both by way of syntect. Raising this is a minor-version change,
+# syntect. Raising this is a minor-version change, never a patch.
-# never a patch.
 rust-version = "1.88"
 # Published crates carry the source, the fixtures the tests need, and nothing else. The

README.md +1 −1

	@@ -29,7 +29,7 @@ cargo install orgo
29	Or from a checkout, if you want to build the version you can read:	29	Or from a checkout, if you want to build the version you can read:
30		30
31	```sh	31	```sh
32	git clone https://github.com/krazywarez/orgo	32	git clone https://gitbay.org/krz/orgo
33	cd orgo	33	cd orgo
34	cargo install --path .	34	cargo install --path .
35	```	35	```

RELEASING.org +38 −10

 Read the content below for the release process.
+** Where the repository lives
+=origin= is gitbay (=ssh://git@gitbay.org/krz/orgo.git=), which is where the issues and
+merge requests are. It push-mirrors to =https://github.com/krazywarez/orgo=, tags
+included.
+That mirror is what makes a release work. The automation is GitHub Actions and nothing
+triggers it directly: a tag pushed to gitbay reaches GitHub within a minute, and
+=.github/workflows/release.yml= runs there. =docs.yml= deploys the documentation site to
+Pages the same way, on a push to =main= that touches =docs/=, =src/=, =Cargo.toml= or
+=Cargo.lock=.
+Neither forge runs the tests. =ci.yml= is gone and there is no =.gitbay/ci.yml=, so the
+checks in step 2 are the only gate a release passes.
 ** Before the first publish
 Nothing to install and no token to store. The release workflow mints a short-lived
-crates.io token with OIDC, configured on crates.io against this repository, the
+crates.io token with OIDC, configured on crates.io against the GitHub repository, the
 =release.yml= workflow file and the =crates-io= environment that job runs in.
-=repository= and =homepage= in =Cargo.toml= point at GitHub and at the documentation site
+=repository= in =Cargo.toml= points at gitbay; =homepage= points at the documentation
-on Pages.
+site on Pages.
 ** Every release
 1. Bump the version in =Cargo.toml=, and build once so =Cargo.lock= follows.
    git push && git push --tags
    #+end_src
-5. The tag push is the release. It builds binaries for macOS (arm64 and x86_64) and
+5. The tag push is the release, by way of the mirror. It builds binaries for macOS
-   Linux (gnu and musl), opens a /draft/ GitHub release with them attached, and runs
+   (arm64 and x86_64) and Linux (gnu and musl), opens a /draft/ GitHub release with them
-   =cargo publish --locked= — there is nothing to publish by hand, and running
+   attached, and runs =cargo publish --locked= — there is nothing to publish by hand, and
-   =cargo publish= locally now only fails on a version crates.io already has.
+   running =cargo publish= locally now only fails on a version crates.io already has. The
+   build checks the tag against =Cargo.toml= rather than trusting the two to match.
+   =gh= talks to the mirror, so it is how you watch the run:
+   #+begin_src sh
+   gh run list -R krazywarez/orgo --limit 3
+   #+end_src
    Publishing is the one step that cannot be undone: a version can be yanked but never
    replaced. The publish job runs in the =crates-io= environment so it can be held —
-   add a required reviewer to that environment in the repository settings and a tag
+   add a required reviewer to that environment in the GitHub repository settings and a
-   push waits for a human before it reaches crates.io.
+   tag push waits for a human before it reaches crates.io.
    A release that fails halfway is re-run from the Actions tab: the workflow takes the
    tag to build as an input, so it does not need a second tag.
-6. Write the release notes and publish the draft.
+6. Write the release notes and publish the draft GitHub release.
+7. Release on gitbay, which has no automation of its own. Same notes, same binaries.
+   #+begin_src sh
+   gitbay release create v0.18.0 --title 0.18.0 --file - < notes.md
+   gh release download v0.18.0 -R krazywarez/orgo -D dist
+   for f in dist/*; do gitbay release asset add v0.18.0 "$(basename "$f")" < "$f"; done
+   #+end_src
 ** If a release goes wrong
 Yank rather than delete, and ship a fix as a new version:

docs/guide/11-versioning.org +4 −4

	@@ -56,10 +56,10 @@ exists to serve the binary, and its types move as the tool does.
56		56
57	* The compiler floor	57	* The compiler floor
58		58
59	The MSRV is 1.88, checked in CI on every change rather than assumed — which is how it	59	The MSRV is 1.88, measured rather than assumed — which is how it came to be 1.88
60	came to be 1.88 rather than the 1.82 orgo's own code needs. The floor is set by	60	rather than the 1.82 orgo's own code needs. The floor is set by dependencies, and a
61	dependencies, and a dependency raising its own is invisible until someone on an older	61	dependency raising its own is invisible until someone on an older compiler tries to
62	compiler tries to build.	62	build.
63		63
64	Raising it is a minor version, never a patch.	64	Raising it is a minor version, never a patch.
65		65

docs/install.org +1 −1

	@@ -21,7 +21,7 @@ That is the whole thing: cargo builds it and puts =orgo= in =~/.cargo/bin=.
21	* From source	21	* From source
22		22
23	#+BEGIN_SRC sh	23	#+BEGIN_SRC sh
24	git clone https://github.com/krazywarez/orgo	24	git clone https://gitbay.org/krz/orgo
25	cd orgo	25	cd orgo
26	cargo build --release	26	cargo build --release
27	#+END_SRC	27	#+END_SRC

Commit c8b514e1a0

Commit `c8b514e1a0`