Skip to content

Releases: avgeek-oss/rootset

Rootset v0.1.2

Choose a tag to compare

@github-actions github-actions released this 11 Oct 16:15
1209038

What's Changed

Full Changelog: v0.1.1...v0.1.2

Rootset v0.1.1

Choose a tag to compare

@github-actions github-actions released this 11 Oct 13:09
505b49a

What's Changed

Full Changelog: v0.1.0...v0.1.1

Rootset v0.1.0

Choose a tag to compare

@github-actions github-actions released this 10 Oct 07:03
30caebf

Rootset’s first public release provides typed PostgreSQL tables through a spreadsheet UI, REST API and MCP.

Included in 0.1.0

  • Compact, virtualized tables with double-click inline editing, filters, type icons and Command-Z undo for saved cell edits.
  • Eleven field types, required fields, defaults, typed constraints and single- or multiple-field unique rules.
  • The latest 200 saved changes per existing cell, presented as a paginated changelog.
  • Complete CSV and JSONL exports through Export Requests.
  • Admin, Member and Viewer roles, with permission-limited personal and team API keys, password and passkey authentication.
  • Separate public API and UI origins, plus REST and MCP access.
  • Shared application components and documentation with lossless screenshots.

Container installation

All three images are published at version 0.1.0 from the same source commit, with Linux AMD64 and ARM64 support:

ghcr.io/avgeek-oss/rootset-api:0.1.0
ghcr.io/avgeek-oss/rootset-worker:0.1.0
ghcr.io/avgeek-oss/rootset-web:0.1.0

Download compose.images.yaml and rootset.env.example from the assets below. Copy the environment example to .env, configure the API/UI origins, PostgreSQL, SMTP and S3-compatible storage, and keep ROOTSET_VERSION=0.1.0. Compose supports an existing PostgreSQL instance or its optional bundled database profile. Migrations use the API image; background jobs use the worker image.

rootset-images.json records the immutable image digests, source commit and supported architectures. The release workflow verifies anonymous image access and a fresh installation with preserved state after restart on both architectures before publication.

This release uses the initial fresh-install database baseline. It is not an upgrade path for earlier prelaunch schemas.

Installation guide