Skip to content

v26.9.2

Choose a tag to compare

View all tags
@cblaettl cblaettl released this 29 Sep 12:55
v26.9.2
6795506
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
lucity-social-preview(8)

This release does not add shiny new feature but instead focuses on polishing the existing experience. The standout change is a completely and carefully overhauled docs section. Besides that the MCP gained some important privacy improvements and we did some tweaking to make the platform more stable.

Docs

  • Entirely new docs, now part of the landing page. A quickstart with screenshots takes you from a fresh account to a live app on its own domain, with a PostgreSQL database and an object storage bucket attached. (#98)
  • Framework deploy guides, plus dedicated pages for services, deployments, builds, variables, domains, PostgreSQL, Redis, object storage, volumes, projects, and workspaces. (#98)
  • A CLI reference generated straight from the CLI's own help texts, so the two can't drift apart. (#98)
  • Use cases and comparisons now live in their own sections. (#98)

Eject

  • An ejected project now ships with a README and a build.sh that rebuilds your source-built services with Railpack (pinned to the version Lucity uses) and pushes them to a registry of your choice. Leaving got a lot less work. (#98)

MCP and CLI

  • The Lucity MCP server never puts secret values into the model's context. Agents can no longer read variable values or database and bucket credentials, and secrets in log output are masked. (#99)
  • lucity token prints a valid bearer token, handy for scripting against the API. (#98)
  • Every CLI command has its own --help with usage and examples, for example lucity login --help. (#98)

Object Storage

  • Creating the first bucket in a brand-new workspace no longer fails. The platform now gives fresh bucket credentials time to propagate before using them. (#96)

Self-hosting

  • Platform routes accept extra response headers through routes.responseHeaders, for example an X-Robots-Tag that keeps a staging instance out of search indexes. (#98)
  • Two fewer settings: GITHUB_OAUTH_CALLBACK_URL and OIDC_CLIENT_SECRET are no longer used. GitHub sign-in goes through the identity provider, and the dashboard signs in with PKCE. (#98)
  • The docs and landing pages link to the dashboard on the same host, so a self-hosted instance no longer sends visitors to lucity.cloud. (#98)
  • The infra chart now ships the Vertical Pod Autoscaler from the Kubernetes autoscaler project. (#100)

Reliability & operations

  • The platform now learns how much CPU and memory each service actually uses. It's the groundwork for sizing reservations from real usage instead of a fixed share of your limit, so deploys stop waiting on capacity that sits idle. Nothing changes for your services yet. (#100)
Assets 7
Loading