v0.2.0 is out. Grab a binary for Linux or macOS, or the Docker image. Read the release notes

Releases

Releases

Every release, with its notes as they were published on GitHub. Want the next one in your inbox? Leave your address, or watch the repo on GitHub and choose Custom, then Releases.

v0.2.0

Pre-releaseDownloads on GitHub

v0.2.0 is the one where pages get a body. Until now a TachyonCMS document could hold text, numbers, links and lists, but nothing you'd call an article. Now a page can be built from blocks you define, and a post can carry real rich text that you write as JSON or Markdown and read back as JSON, HTML, Markdown or plain text. It's still pre-alpha: drafts, media and the admin screen are next, so keep it off public networks for now.

Get it

  • Binaries for Linux (x86_64, arm64, static) and macOS (Intel, Apple silicon) are attached below.
  • Docker: docker pull ghcr.io/tachyon-cms/tachyoncms:v0.2.0. Set TACHYON_DATABASE_URL and TACHYON_PUBLIC_URL, and it serves on port 3000.

Upgrading from v0.1.0? Replace the binary or the image and start it. The one migration runs by itself.

What's in it

  • Pages built from blocks. A blocks field holds rows of the block types you define: a hero, a quote, a call to action. Each row keeps its own id and blockType, and you can filter into them with where[layout.blockType][equals]=quote. Field rules apply inside every row, so a field only Editors may see stays hidden in each block that has it.
  • Blocks you write once. A shared block ("kind": "block") can be used by any number of collections. Change it in one place and every schema that uses it is checked and migrated in the same transaction. If that change would break a page somewhere, it's refused before anything is saved.
  • Rich text that can't run a script. Paragraphs, headings, lists, task lists, quotes, code, tables, links and embedded blocks, with the features turned on per field. HTML output is built and escaped by TachyonCMS itself, never passed through, and every link is checked against http, https, mailto, tel and relative paths, on the way in and again on the way out.
  • Write it in Markdown. Send {"format": "markdown", "value": "…"} and it's converted on the way in, with extensions for blocks (:::callout{type="warning"}), links to other documents ([guide](doc:pages/install)) and embedded references. Anything that can't be converted faithfully is a 422 with the line number, not a quietly mangled post.
  • Read it however your site wants it. ?format=html, markdown or text on any read, populated and joined documents included. A link to something the reader can't see comes out as its text alone.
  • Config mistakes stop at startup. A --config file that doesn't exist, a misspelt key in tachyon.toml, an allowed_origins entry that could never match (a path, a wildcard, no scheme), lockout_attempts = 0 and a session that ends before its idle limit are now errors that name the setting, instead of surprises later. And tachyon schema diff nope.json with the database down now says the file is missing straight away, while a connection that fails names the host, port and database it tried, never the password.

The docs at docs.tachyoncms.com have a page each for blocks, rich text and Markdown input, with every rule the converter applies.

Supply chain

Every binary records its dependency tree, and each archive has an SPDX SBOM. The checksums are signed with cosign, the archives and the image carry build provenance, and the image is signed. Scorecard runs weekly, and every commit is signed off under the DCO.

Thanks

To @foothillsdigital, the first person to send code to TachyonCMS: every startup and CLI fix in this release is theirs (#47, #48, #52), and so are the docs for the first two. There are more good first issues waiting, and this section has room for more names.

Verify a download

cosign verify-blob \
  --certificate-identity 'https://github.com/tachyon-cms/tachyoncms/.github/workflows/release.yml@refs/heads/main' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --bundle checksums.txt.sigstore.json checksums.txt
sha256sum --check --ignore-missing checksums.txt

Full changes: https://github.com/tachyon-cms/tachyoncms/compare/v0.1.0...v0.2.0

Downloads on GitHub

v0.1.0

Pre-releaseDownloads on GitHub

v0.1.0 is the first release of TachyonCMS: a headless CMS in one Rust binary, backed by one Postgres database, with an API generated from the content types you define. It's pre-alpha. The content API, sign-in and access rules work; the admin screen, rich text, drafts and media don't exist yet, so keep it off public networks for now.

Get it

  • Binaries for Linux (x86_64, arm64, static) and macOS (Intel, Apple silicon) are attached below.
  • Docker: docker pull ghcr.io/tachyon-cms/tachyoncms:v0.1.0. Set TACHYON_DATABASE_URL and TACHYON_PUBLIC_URL, and it serves on port 3000.

What's in it

  • Content types over the API, or in a file. Collections and globals with text, number, date, email, URL, select, radio, slug, code, JSON and map-point fields, plus relationships, groups, arrays, rows, collapsible sections and tabs. tachyon schema export, diff and apply keep them in version control, and renames keep your data.
  • Queries that reach where your content does. Filter through relationships (where[author.name][equals]=Ann) and into list rows, sort, page with cursors, and find map points by distance. Populate linked documents to any depth you allow.
  • Ask for only what you need. select and populate trim responses, virtual fields show a linked value without storing it, and join fields list the documents that link to this one.
  • Sign-in, roles and API keys. Sessions or bearer tokens, Argon2id passwords checked against known breaches, lockout after repeated failures, and scoped keys you can rotate. Admin, Editor, Author and Viewer roles, plus your own.
  • Access rules down to a field. Published posts for everyone, drafts for their authors, a salary field for HR. Rules compile to SQL per caller, so a hidden document can't be found by filtering for it, and GET /api/access tells each caller what they can do.
  • Errors that point at the problem. Every error is RFC 9457 problem+json, names the exact field (seo.title, links.0.url) and carries a request ID you can find in the logs.

Supply chain

Every binary records its dependency tree, and each archive has an SPDX SBOM. The checksums are signed with cosign, the archives and the image carry build provenance, and the image is signed. Scorecard runs weekly, and every commit is signed off under the DCO.

Thanks

To everyone who starred, watched and opened the repo before there was anything to download. Ten issues are ready for a first contribution, and the next release notes have room for your name.

Verify a download

cosign verify-blob \
  --certificate-identity 'https://github.com/tachyon-cms/tachyoncms/.github/workflows/release.yml@refs/heads/main' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --bundle checksums.txt.sigstore.json checksums.txt
sha256sum --check --ignore-missing checksums.txt

Full changes: https://github.com/tachyon-cms/tachyoncms/commits/v0.1.0

Downloads on GitHub