v1.0.3

Changed

• Validate stable release metadata and annotated main-branch tags before publishing images, reuse
  verified exact images on retries, and reserve minor aliases for newer remote release tags even
  when those aliases are missing or stale.
• Gate official MCP Registry publishing on offline image startup, complete tool discovery, source
  identity, and the existing per-platform provenance and SBOM checks.

Fixed

• Make container health checks transport-aware and respect configured HTTP bind addresses and ports.
• Stop Registry read-back retries on permanent authentication or malformed-response failures.

v1.0.2

Changed

• Refresh production dependencies, including the MCP SDK, Hono, its Node.js server adapter, and Zod.
• Refresh development, website, and pinned GitHub Actions dependencies.
• Clarify README workflows and setup instructions, and schedule grouped Dependabot updates twice
  monthly.

v1.0.1

Changed

• Publish future GHCR images with explicit max-mode BuildKit SLSA provenance and native SPDX SBOM
  attestations, while deferring separate image signing.
• Refresh production, development, website, and pinned GitHub Actions dependencies.

Fixed

• Update the transitive fast-uri and qs runtime dependencies to versions that address
  published host-confusion, SSRF, and denial-of-service advisories.
• Correct the official MCP Registry OCI package metadata so the version is carried only by the
  immutable image identifier accepted by the Registry publisher.
• Finalize the staged Docker MCP Registry metadata with its validated catalog title, formatting,
  and exact v1.0.0 source pin.

v1.0.0

Added

• Display the public GitHub repository's star count in the website's desktop and mobile navigation,
  using one bounded build-time request with an accessible count-free fallback when GitHub is
  unavailable.

Fixed

• Harden GitHub Actions pinning tests against malformed slash-separated action references and
  replace the CodeQL-flagged generic HTML tag matcher in website contracts with a direct rendered
  disclaimer assertion.

v0.9.0

Added

• Add an Astro Starlight project website with transport setup guides, prominent security guidance,
  accessible install controls, and tool coverage generated from the canonical catalog.
• Strengthen release-candidate validation with package, Compose, local-image, MCP Registry,
  compiled-startup, and redacted full-history secret checks.

Changed

• Make Docker Compose pass only documented runtime settings into published and local-build
  containers while preserving proxy and private-CA configuration.
• Split website contract and browser validation into focused suites covering content, generated
  output, publication safeguards, accessibility, navigation, and responsive behavior.
• Pin third-party GitHub Actions to immutable commit SHAs and enforce the policy with an automated
  workflow check.
• Freeze the reviewed 27-tool MCP protocol contract in release validation, including tool order,
  descriptions, schemas, annotations, and literal confirmation for permanent deletions.
• Make live-smoke recovery safer by reserving a private recovery record before mutation, retaining
  unverified create ids only for manual inspection, and requiring ownership evidence before
  automatic cleanup.
• Refresh the MCP SDK and Hono runtime stack, supported development dependencies, and GitHub Actions
  tooling.

v0.8.1

Changed

• Refresh production and development dependencies, including Hono, the MCP SDK, ESLint, Prettier,
  TypeScript, Vitest, and their supporting packages.
• Refresh the Docker and GitHub Actions toolchain, including the pnpm setup, build, metadata, and
  Buildx actions.

v0.8.0

Added

• Add a Dependabot auto-merge workflow for same-repository npm/pnpm, GitHub Actions, and Docker
  patch/minor updates, while keeping major updates and Docker runtime baseline jumps manual.
• Add weekly, grouped Dependabot version checks for npm/pnpm dependencies, GitHub Actions, and
  Docker image references, and gate PRs with a non-publishing Docker/release dry run.
• Add MCP Registry readiness documentation, Docker MCP Registry staging metadata, and drift checks
  for the existing GHCR distribution path.

Changed

• Split Docker Compose workflows so docker-compose.yml runs the published GHCR image by default,
  docker-compose.local.yml builds from the checkout as simplelogin-mcp:local, and the Docker
  docs distinguish operator deployments from local image validation.
• Refresh the runtime baseline to Node.js 24 and node:24-bookworm-slim, align CI, engines, types,
  and docs with that floor, and switch Docker healthchecks to Node's built-in fetch.

v0.7.0

Added

• Add public-ready repository documentation: expanded install, configuration, client setup,
  self-hosted SimpleLogin, and troubleshooting guidance in the README, plus contributing, support,
  and release-process docs.
• Add public API coverage and non-goals documentation for supported, deferred, and intentionally
  excluded SimpleLogin API areas.

v0.6.0

Added

• Add an opt-in live SimpleLogin smoke-test workflow through pnpm smoke:live, with stdio and HTTP
  runbook coverage in docs/live-smoke-test.md and offline smoke-runner tests for cleanup,
  failure summaries, HTTP auth, and startup behavior.

Changed

• Standardize the public MCP tool surface for the 0.6 milestone: tool names are documented as
  stable 1.0 candidates, every registered tool now carries complete MCP behavior annotations, and
  the generated tool catalog documents each tool's bounds and output shape. Mail-routing updates
  that can stop future delivery, including alias mailbox reassignments and custom-domain routing
  changes, are marked destructive.
• Bound custom_domain_trash_list responses with local page_id/limit pagination (default page
  0, default limit 100, max 500) and return { aliases, page_id, limit, returned, total, more } so
  the unpaginated SimpleLogin endpoint cannot produce unbounded MCP responses while still allowing
  older trash entries to be reached.
• Improve runtime failure diagnostics: SimpleLogin API JSON, text, empty, malformed, timeout,
  abort, network, and rate-limit failures now map deterministically to typed MCP errors with status
  and endpoint context. Logs stay on stderr with redacted structured metadata and never include API
  keys, MCP auth tokens, authorization headers, or request bodies.
• Keep 429 handling explicit and non-retrying in 0.6: rate-limit responses surface the status,
  endpoint, server message, and Retry-After hint when present, leaving retry policy to the caller
  so mutating tools are not repeated implicitly.

v0.5.0

Added

• Add custom-domain tools: custom_domain_list, custom_domain_update, and custom_domain_trash_list.
• Add local pre-flight checks for custom_domain_update.
• Add account utility tools: account_get_stats, notification_list, notification_mark_read, settings_get, and settings_update.
• Keep auth, payment, account-deletion, and sudo-style endpoints out of scope.