Release Notes for denoland/celld: Where to Find and How to Use Them

The release notes for denoland/celld are published exclusively on GitHub Releases, with each version including a structured changelog, breaking changes, bug fixes, and signed binary artifacts.

The celld distributed systems experiment from the Deno team follows semantic versioning and publishes every release through GitHub's release infrastructure. Understanding where these notes live and how they're generated helps operators track changes and deploy safely.

---

Where Release Notes Are Published

All release notes for denoland/celld appear at the canonical location:

https://github.com/denoland/celld/releases

Each release entry contains four core components:

• Version tag — the exact semantic version (e.g., v0.5.2)
• Release date — timestamp from the GitHub release creation
• Markdown-formatted notes — grouped by feature, breaking change, bug fix, and documentation
• Signed artifacts — compressed binaries with SHA-256 checksums and attestation signatures

The release notes use a consistent template across versions. You can parse this structure programmatically or read it directly in the GitHub UI.

---

Release Notes Format and Structure

Based on the codebase structure and release workflow, celld release notes follow this organization:

Section	Description
Highlights	New capabilities like LTX block objects for replication, memory-pressure thresholds (CELLD_MAX_RSS_MB), or operator API enhancements
Breaking Changes	Migration requirements, such as bucket format deprecations or default durability mode switches
Bug Fixes	Race condition resolutions, authentication corrections, timeout handling improvements
Documentation	Updates to docs/guarantees.md, docs/telemetry.md, or docs/limitations.md
Assets	Downloadable celld-linux-x86_64.tar.gz, celld-linux-aarch64.tar.gz, plus checksums and attestation files

The notes reference specific source files when relevant. For example, durability guarantee changes cite docs/guarantees.md, while telemetry additions point to docs/telemetry.md.

---

How Releases Are Generated

The denoland/celld release process is fully automated through .github/workflows/release.yml. Understanding this pipeline explains why the release notes appear as they do.

The workflow performs these steps:

1. Build — compiles a statically-linked celld binary in release profile
2. Verify — checks that celld --version outputs the expected tag
3. Compress — creates tar.gz archives for supported architectures
4. Draft — creates a draft GitHub release with auto-generated notes
5. Sign — generates attestation signatures for provenance verification
6. Publish — promotes the draft to a public release

The release notes body comes from the tag's associated commits and can be edited before publication to add context about breaking changes or migration steps.

---

Accessing Release Notes Programmatically

For automation, CI pipelines, or tooling integration, use the GitHub Releases API:

# Fetch the latest release notes

curl -s https://api.github.com/repos/denoland/celld/releases/latest | jq '.body'

The JSON response includes these key fields relevant to celld release notes:

• tag_name — version identifier matching celld --version output
• published_at — ISO 8601 timestamp
• body — the complete Markdown release notes
• assets — array of binaries, checksums, and attestation files with download URLs

To retrieve a specific version's notes:

curl -s https://api.github.com/repos/denoland/celld/releases/tags/v0.5.2 | jq '.body'

List all releases for historical comparison:

curl -s https://api.github.com/repos/denoland/celld/releases | jq '.[] | {tag: .tag_name, date: .published_at}'

---

Downloading and Verifying a Specific Release

After reading the celld release notes, deploy a specific version with verification:

# Set target version

VERSION="v0.5.2"
ARCH="x86_64"  # or aarch64

# Download binary

curl -L -o celld.tar.gz \
  "https://github.com/denoland/celld/releases/download/${VERSION}/celld-linux-${ARCH}.tar.gz"

# Download and verify checksum (recommended)

curl -L -o celld.tar.gz.sha256 \
  "https://github.com/denoland/celld/releases/download/${VERSION}/celld-linux-${ARCH}.tar.gz.sha256"
sha256sum -c celld.tar.gz.sha256

# Or verify with GitHub Attestations (if available for your version)

gh attestation verify celld.tar.gz --repo denoland/celld

# Extract and install

tar -xzf celld.tar.gz -C ~/.local/bin
chmod +x ~/.local/bin/celld

# Confirm version matches release notes

celld --version  # Expected: celld v0.5.2

The celld binary reports its version at build time from the Git tag, ensuring what you run matches the release notes you read.

---

Key Source Files Related to Releases

File	Purpose
.github/workflows/release.yml	Defines the complete CI/CD pipeline for building, signing, and publishing releases
Cargo.toml	Workspace configuration; the binary version is injected from Git tags during the release workflow
README.md	Installation instructions referencing specific release versions and verification procedures
docs/guarantees.md	Durability semantics that evolve across releases—often cited in breaking change sections
docs/telemetry.md	Observability flags added or modified in recent releases
docs/limitations.md	Operational constraints that may change version-to-version

When reading celld release notes, cross-reference any documentation changes against these files in the repository.

---

Version Tracking and Upgrade Planning

The denoland/celld release notes indicate stability through version prefixes:

• v0.x.x — pre-1.0 releases with potential breaking changes in minor versions
• Semantic versioning applies: patch increments for fixes, minor for features, major for breaking changes (though pre-1.0, minor bumps may break)

Monitor the Breaking Changes section carefully. Historical patterns show:

• Durability defaults shifted from bucket to fleet mode
• Authentication methods for object storage backends evolved
• Memory management parameters (CELLD_MAX_RSS_MB, CELLD_LOG_HEDGE_MS) were introduced

---

Summary

• denoland/celld release notes live exclusively at github.com/denoland/celld/releases
• Each release includes structured Markdown notes with highlights, breaking changes, bug fixes, and documentation updates
• The Release workflow in .github/workflows/release.yml automates build, sign, and publish steps
• Use the GitHub API to fetch notes programmatically for CI/CD integration
• Always verify downloaded binaries using SHA-256 checksums or GitHub Attestations before deployment
• Cross-reference documentation changes in docs/guarantees.md, docs/telemetry.md, and docs/limitations.md

---

Frequently Asked Questions

How do I find the release notes for a specific celld version?

Navigate to the GitHub releases page at https://github.com/denoland/celld/releases and select your target tag, or use the API endpoint /repos/denoland/celld/releases/tags/vX.Y.Z. The body field contains the complete Markdown release notes for that version.

Why don't I see a CHANGELOG.md file in the celld repository?

The denoland/celld project maintains release history exclusively through GitHub Releases rather than a static file. This approach allows dynamic updates, rich formatting, and direct association with signed artifacts. The release workflow in .github/workflows/release.yml publishes notes alongside each build.

How can I verify that a downloaded celld binary matches the release notes?

Each release includes SHA-256 checksums and attestation signatures. Download the .sha256 file for your architecture and run sha256sum -c, or use gh attestation verify with the GitHub CLI. The celld --version output must match the release tag cited in the notes.

Are celld release notes available in a machine-readable format?

Yes. The GitHub Releases API returns JSON where the body field contains the Markdown notes. Parse this with jq or any JSON processor. The tag_name, published_at, and assets arrays provide structured metadata for automation.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}