Slotlock changelog

package_identifier

ghcr.io/pilotaai/slotlock:0.9.1 → ghcr.io/pilotaai/slotlock:0.11.0

version

0.9.1 → 0.11.0

package_identifier

ghcr.io/pilotaai/slotlock:0.9.0 → ghcr.io/pilotaai/slotlock:0.9.1

version

0.9.0 → 0.9.1

package_identifier

ghcr.io/pilotaai/slotlock:0.8.0 → ghcr.io/pilotaai/slotlock:0.9.0

version

0.8.0 → 0.9.0

package_identifier

ghcr.io/pilotaai/slotlock:0.6.3 → ghcr.io/pilotaai/slotlock:0.8.0

version

0.6.3 → 0.8.0

package_identifier

ghcr.io/pilotaai/slotlock:0.6.2 → ghcr.io/pilotaai/slotlock:0.6.3

version

0.6.2 → 0.6.3

package_identifier

ghcr.io/pilotaai/slotlock:0.6.0 → ghcr.io/pilotaai/slotlock:0.6.2

version

0.6.0 → 0.6.2

https://slotlock.pylota.io/llms.txt

− Slotlock is an early (0.x) TypeScript library and MCP/A2A server, on npm as `slotlock`. It has no hosted service; you run it against your own PostgreSQL 16.− - Writes need an `idempotency_key`; retry with the same key and arguments. Updates and deletes need the `expected_revision` you last read.− - [API keys and dashboard](https://slotlock.pylota.io/docs/keys.md): Give each agent a key of its own, scoped and revocable, from the command line or from a dashboard where people sign in with GitHub.− - [Quickstart](https://slotlock.pylota.io/docs/quickstart.md): Run Slotlock and PostgreSQL 16 with Docker, connect Claude Code, and have an agent find and book a free slot.− - [Use Slotlock from TypeScript](https://slotlock.pylota.io/docs/library.md): Call Slotlock's engine and PostgreSQL store from your own code, with holds, events and tenant isolation, and no server in between.− - [Concepts](https://slotlock.pylota.io/docs/concepts.md): The ideas Slotlock is built on, from resources and availability rules to holds, free/busy certainty and tenancy.− - [Security model](https://slotlock.pylota.io/docs/security.md): How Slotlock keeps agent writes safe. A person can confirm each one, PostgreSQL decides every overlap, and forced row-level security keeps tenants apart.+ Slotlock is an early (0.x) TypeScript library and MCP/A2A server, on npm as `slotlock`. You run it against your own PostgreSQL 16 or newer: hosted Slotlock (https://slotlock-api.pylota.io) is not open, and self-hosting is the only supported path today (https://slotlock.pylota.io/docs/hosted.md).+ - Event writes (`slotlock_create_event`, `slotlock_update_event`, `slotlock_delete_event`) need an `idempotency_key`; retry with the same key and arguments. Updates and deletes also need the `expected_revision` you last read. Holds belong to the application API, not the tools.+ - On hosted Slotlock a write takes effect at once; no person is asked to confirm it. A `429 rate_limited` answer carries `Retry-After`: wait that long.+ - [Quickstart](https://slotlock.pylota.io/docs/quickstart.md): Run Slotlock and PostgreSQL 18 with Docker, connect Claude Code, and have an agent find and book a free slot.+ - [Set up with a coding agent](https://slotlock.pylota.io/docs/agent-setup.md): Paste one prompt into Claude Code, Cursor or Codex and let it set Slotlock up for your project, then prove it works.+ - [Hosted Slotlock](https://slotlock.pylota.io/docs/hosted.md): The hosted service is not open; self-hosting is the only supported path today. What hosted Slotlock will be, its limits, terms, privacy, status and support.+ - [Self-hosting](https://slotlock.pylota.io/docs/self-host.md): Run the Slotlock server from the published image or from npm, configure it with environment variables, and check it end to end.+ - [API keys](https://slotlock.pylota.io/docs/keys.md): Give each agent a key of its own, limited to what it needs and revocable without a restart.+ - [Dashboard](https://slotlock.pylota.io/docs/dashboard.md): Let people sign in with GitHub and manage their own resources, bookable hours and API keys.+ - [TypeScript library](https://slotlock.pylota.io/docs/library.md): Call Slotlock's engine and PostgreSQL store from your own Node.js code, with no server in between.+ - [Language clients](https://slotlock.pylota.io/docs/clients.md): Slotlock's REST API from Python, Go, Rust, Java and .NET, one method per operation, each tested against a real server in CI.+ - [Operations](https://slotlock.pylota.io/docs/operations.md): Run Slotlock in production. Maintenance, quotas, retention, erasure and the production checklist.+ - [Scaling](https://slotlock.pylota.io/docs/scaling.md): How far one PostgreSQL takes Slotlock, how to measure it, and how to grow past it, by resource, by region, with replicas and alongside a solver.+ - [Benchmarks](https://slotlock.pylota.io/docs/benchmarks.md): How Slotlock's range constraint compares with one row per slot under pgbench, measured on every release, with the method and its caveats.+ - [Concepts](https://slotlock.pylota.io/docs/concepts.md): The ideas Slotlock is built on, from resources and availability rules to holds, free/busy certainty and tenancy.+ - [Security model](https://slotlock.pylota.io/docs/security.md): How Slotlock keeps agent writes safe. An MCP client can ask its person to confirm each one, PostgreSQL decides every overlap, and forced row-level security keeps tenants apart.+ - [Versions and stability](https://slotlock.pylota.io/docs/versioning.md): What a Slotlock version number promises, what stays stable under /v1 and in the tools, and how features are deprecated and removed.+ - [Known issues](https://slotlock.pylota.io/docs/known-issues.md): Where Slotlock 0.2.0 can accept a double booking and the zod advisory it pins. Both are fixed in 0.3.0 and later; upgrade.+ - [Hosted status](https://slotlock.pylota.io/docs/status.md): Where to see whether hosted Slotlock is up, and how its status is checked from outside the server.+ - [Privacy notice](https://slotlock.pylota.io/docs/privacy.md): What hosted Slotlock stores about you and the people in your calendars, why, for how long, who processes it, and how to have it erased. A draft for review.+ - [Terms of Service](https://slotlock.pylota.io/docs/terms.md): The agreement for using hosted Slotlock, including the data processing terms for the personal data in your calendars. A draft for review.+ - [Acceptable Use Policy](https://slotlock.pylota.io/docs/acceptable-use.md): What you may not do with hosted Slotlock, what happens if you do, and how to report abuse. A draft for review.+ - [REST API](https://slotlock.pylota.io/docs/api.md): every route, with a page per route at /docs/api/<route>.md, and the OpenAPI document at https://slotlock.pylota.io/openapi.json

package_identifier

ghcr.io/pilotaai/slotlock:0.5.3 → ghcr.io/pilotaai/slotlock:0.6.0

version

0.5.3 → 0.6.0

package_identifier

ghcr.io/pilotaai/slotlock:0.5.2 → ghcr.io/pilotaai/slotlock:0.5.3

version

0.5.2 → 0.5.3

env_vars

DATABASE_URL, SLOTLOCK_AUTH_TOKEN, SLOTLOCK_CONFIRMATION_SECRET, PORT, SLOTLOCK_MIGRATE_DATABASE_URL, SLOTLOCK_CONFIRM_WRITES, SLOTLOCK_AVAILABILITY, SLOTLOCK_REST_API, SLOTLOCK_SHARED_LIMITS, SLOTLOCK_WEBHOOKS, SLOTLOCK_TENANT → DATABASE_URL, SLOTLOCK_AUTH_TOKEN, SLOTLOCK_CONFIRMATION_SECRET, SLOTLOCK_METRICS_TOKEN, PORT, SLOTLOCK_MIGRATE_DATABASE_URL, SLOTLOCK_CONFIRM_WRITES, SLOTLOCK_AVAILABILITY, SLOTLOCK_REST_API, SLOTLOCK_RETENTION_DAYS, SLOTLOCK_SHARED_LIMITS, SLOTLOCK_WEBHOOKS, SLOTLOCK_TENANT

package_identifier

ghcr.io/pilotaai/slotlock:0.4.1 → ghcr.io/pilotaai/slotlock:0.5.2

version

0.4.1 → 0.5.2

env_vars

DATABASE_URL, SLOTLOCK_AUTH_TOKEN, SLOTLOCK_CONFIRMATION_SECRET, PORT, SLOTLOCK_MIGRATE_DATABASE_URL, SLOTLOCK_CONFIRM_WRITES, SLOTLOCK_AVAILABILITY, SLOTLOCK_REST_API, SLOTLOCK_TENANT → DATABASE_URL, SLOTLOCK_AUTH_TOKEN, SLOTLOCK_CONFIRMATION_SECRET, PORT, SLOTLOCK_MIGRATE_DATABASE_URL, SLOTLOCK_CONFIRM_WRITES, SLOTLOCK_AVAILABILITY, SLOTLOCK_REST_API, SLOTLOCK_SHARED_LIMITS, SLOTLOCK_WEBHOOKS, SLOTLOCK_TENANT

package_identifier

ghcr.io/pilotaai/slotlock:0.3.0 → ghcr.io/pilotaai/slotlock:0.4.1

version

0.3.0 → 0.4.1

package_identifier

ghcr.io/pilotaai/slotlock:0.2.0 → ghcr.io/pilotaai/slotlock:0.3.0

version

0.2.0 → 0.3.0

package_identifier

ghcr.io/pilotaai/slotlock:0.1.1 → ghcr.io/pilotaai/slotlock:0.2.0

version

0.1.1 → 0.2.0