Get notified
We are not going to collect your email address to send you a newsletter we have not written. Releases are cut on GitHub, and GitHub already has three good ways to tell you when one lands — one of which does not involve an account at all. Pick whichever fits how you already work.
Three ways
Current release is v10.0. Everything below points at the same repository:
paracoding-ai/paracoding-oss.
The one most people want. On the repository page, open the Watch menu, choose Custom, and tick Releases only. GitHub notifies you when a release is published and stays quiet about every issue, comment and push in between. Signal without the firehose.
No GitHub account required, no notification settings to maintain, nothing that can be
unsubscribed on your behalf. Point any feed reader at
https://github.com/paracoding-ai/paracoding-oss/releases.atom and you get an entry
per release, with the tag and the notes.
Not a notification channel — a bookmark and a signal. It puts the repo in your own stars list so you can find it again, and it is the only vanity metric this project keeps. If the work is useful to you, it is a cheap way to say so.
# The feed, if you would rather wire it up yourself:
https://github.com/paracoding-ai/paracoding-oss/releases.atom
# Check what the newest published release is, from a shell:
curl -fsSL https://github.com/paracoding-ai/paracoding-oss/releases.atom \
| grep -m1 '<title>'Release discipline
Worth knowing before you subscribe, because it tells you what a notification from this repository actually means.
A minor bump every time a cut leaves our hands. There is no "unreleased build floating around", no dot-release for a typo that quietly also changed behaviour, no two artefacts wearing the same number. If it left here, the version moved. That means a notification from this feed always corresponds to a distinct, addressable set of bytes — never to a re-published tag you have already installed.
The version is an input, not a side effect. The release generator is told what version it is building; it does not infer one from the branch, the date, the commit count or whatever happens to be in a tag at the time. That inversion is what makes the next sentence possible, and it is deliberate: a version derived from mutable context is a version that changes when the context does.
Same commit plus same version always means the same bytes. The generator is deterministic.
Cut twice, run diff -r over the two trees, expect zero. Archives are reproducible
— fixed mtime, gzip level 9, file modes taken from the tree, which is also why
install.sh arrives executable in the tarball and does not in a clone. Every file carries
a SHA-256 entry in a per-release manifest, so you can verify what you downloaded rather than trusting
that it looks right.
diff -r the results: zero differences. If it is not reproducible, it is not a release.0755 where the tree says 0755.Release notes say what changed and, where it matters, what it breaks. We do not ship a roadmap item
described as if it already works, and we do not quietly change a default without naming it —
the shipped defaults are PC_AUTO_APPROVE=1, PC_GUARDRAILS=0 and
PC_REQUIRE_PASSKEY=0, and if any of those ever moves, that will be the first line of the
notes, not a footnote.
While you wait
v10.0 is out. Subscribing is for the next one — the current one you can install this afternoon.
Elsewhere in the network: GPUHA.com, Seaside Mushrooms and Paracoding Press — where Book 1 and Book 2 live, and where Book 3, Agentic Fungi — written in the same substrate this harness runs on — is out now.