SDODS

Release notes

Changes per version, generated from changesets.

Releases are versioned with changesets and published to npm as @sdods/*.

0.2.1

Fixes found by driving the web UI and sweeping every CLI command.

  • Sign out works. It could do nothing at all: logging out without a live session returned 401, and the client discarded the rejection, so the button had no visible effect. Logout is now idempotent and always clears the cookie, while an authenticated logout still requires a CSRF token so no cross-site page can force one. Signing out also clears every cached query, so no data crosses a session boundary on a shared machine.
  • An expired session returns you to the sign-in form instead of rendering "AUTH_REQUIRED: Authentication required" inside a shell that still looked signed in.
  • users deactivate, users set-role and tokens revoke no longer crash with "root.opts is not a function". users deactivate is how access is revoked, so this was not cosmetic.
  • tokens revoke tells the truth: an unknown or already-revoked id now warns instead of reporting success.
  • The platform database is resolved from the workspace root. Running a command from a subdirectory used to open a different, empty database — sdods serve started inside a run's artifacts folder rejected every login because the users lived in the workspace database.
  • The projects list shows its processes rather than processes: , , ,.

0.2.0

First published release: npm i -g @sdods/cli installs SDODS as compiled packages, so there is no longer a source checkout in ~/.sdods/app.

  • The installer defaults to the published packages; --source git clones a checkout for working on SDODS itself, and is never used as a silent fallback.

  • sdods init scaffolds the demo project from assets shipped inside @sdods/cli.

  • sdods serve ships the dashboard inside @sdods/server.

    0.1.0 was never released for this project; the version number was already taken on npm by an earlier, unrelated placeholder, so the first release is 0.2.0.

0.1.0 (unreleased)

  • Monorepo with @sdods/contracts, @sdods/core, @sdods/cli and the demo-shop project.
  • Six-layer configuration precedence with provenance, secret-literal refusal and ${VAR:-default} interpolation.
  • Organization → workspace → project → module hierarchy and named processes.
  • sdods project, env, config, doctor commands.
  • This documentation site.

Using an AI coding agent? Install SDODS:

Install the SDODS plugin in Claude Code: skills, subagents, commands and the MCP server.

  1. /plugin marketplace add YarlisAISolutions/sdods-skills
  2. /plugin install sdods@sdods
Learn more about using SDODS with AI tools

On this page