Skip to content

Remove the Cloud Free Tier server interface - #154

Merged
kesmit13 merged 1 commit into
mainfrom
remove-free-tier-shell
Oct 30, 2026
Merged

kesmit13 merged 1 commit into
mainfrom
remove-free-tier-shell

Conversation

@kesmit13

@kesmit13 kesmit13 commented Oct 30, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

singlestoredb.server.free_tier provisioned a server through shell.singlestore.com. That service has been shut down, so free_tier.start() can no longer succeed. This PR removes:

  • singlestoredb/server/free_tier.py
  • the "Cloud Free Tier" section of the API reference (docs/src/api.rst), with the "Server Tools" intro reworded to describe Docker only
  • the Free Tier section of ARCHITECTURE.md

singlestoredb.server.docker is unaffected. Its open_shell() runs a local mysql client against the container and doesn't depend on the hosted shell service.

User-facing change for the release notes: import singlestoredb.server.free_tier now raises ModuleNotFoundError. Users should switch to singlestoredb.server.docker. whatsnew.rst is left for the release bump; the historical v1.12 entry stays as it is.

Verification

  • import singlestoredb, singlestoredb.server.docker succeeds
  • A fresh Sphinx build (-E) of docs/src gives no free_tier warnings
  • No remaining references outside whatsnew.rst history and generated docs/ output, which gets regenerated at release
  • pre-commit passes

🤖 Generated with Claude Code


Note

Medium Risk
Removes a public module and breaks existing imports, though the underlying hosted service no longer works.

Overview
Removes singlestoredb.server.free_tier and the whole singlestoredb/server/free_tier.py module, which provisioned servers via the shut-down shell.singlestore.com API. singlestoredb.server.docker is unchanged.

ARCHITECTURE.md and docs/src/api.rst now describe Server Tools as Docker-only: the Cloud Free Tier section, examples, and autosummary entries are gone.

Breaking change: import singlestoredb.server.free_tier raises ModuleNotFoundError. Callers should use singlestoredb.server.docker instead.

Reviewed by Cursor Bugbot for commit 5e33312. Bugbot is set up for automated code reviews on this repo. Configure here.

singlestoredb.server.free_tier provisioned a server through
shell.singlestore.com, which has been shut down, so free_tier.start()
can no longer succeed. Remove the module along with its API reference
section and its ARCHITECTURE.md entry. The Docker server interface is
unaffected.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues remain for the removal of the retired Free Tier interface and related documentation.

No open issues 🎉

What changed in this PR

Removes the Cloud Free Tier server interface because its backing service has shut down. Docker remains the supported server-management option and is unchanged.

Changes:

  • Deletes singlestoredb.server.free_tier; existing imports now raise ModuleNotFoundError, and users should migrate to singlestoredb.server.docker.
  • Removes Free Tier documentation and updates Server Tools descriptions to cover Docker only.
File Description
singlestoredb/​server/​free_tier.py Deletes the retired Cloud Free Tier implementation.
docs/​src/​api.rst Removes Free Tier examples and API entries; describes Docker-only support.
ARCHITECTURE.md Removes Free Tier guidance and narrows Server Tools to Docker.

Review effort: Balanced

@kesmit13
kesmit13 merged commit f0c467f into main Oct 30, 2026
15 checks passed
@kesmit13
kesmit13 deleted the remove-free-tier-shell branch October 30, 2026 16:17

This branch was successfully deployed

1 active deployment
Base — 5e333124 Deployed Oct 30, 2026 by kesmit13 via test-coverage #596
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants