fix: scrub unregistered evalcraft.dev domain (release 0.2.1)#28
Merged
Conversation
evalcraft.dev was never registered (NXDOMAIN), but the cloud feature defaulted to a non-existent api.evalcraft.dev endpoint and the landing page linked hello@evalcraft.dev. - cloud client: no default endpoint; resolve base_url from arg / EVALCRAFT_BASE_URL / ~/.evalcraft/config.json, and raise a clear 'no public service — self-host' error when unset (new test). save_config only writes base_url when provided. - 'evalcraft cloud --url': no default; init-template example -> localhost self-host. - landing page + demo scripts: dead-domain emails -> real/placeholder addresses. - bump 0.2.0 -> 0.2.1 + CHANGELOG. 804 tests, ruff 0, mypy 0; built + twine-checked locally.
beyhangl
added a commit
that referenced
this pull request
Jun 1, 2026
evalcraft.dev was never registered (NXDOMAIN), but the cloud feature defaulted to a non-existent api.evalcraft.dev endpoint and the landing page linked hello@evalcraft.dev. - cloud client: no default endpoint; resolve base_url from arg / EVALCRAFT_BASE_URL / ~/.evalcraft/config.json, and raise a clear 'no public service — self-host' error when unset (new test). save_config only writes base_url when provided. - 'evalcraft cloud --url': no default; init-template example -> localhost self-host. - landing page + demo scripts: dead-domain emails -> real/placeholder addresses. - bump 0.2.0 -> 0.2.1 + CHANGELOG. 804 tests, ruff 0, mypy 0; built + twine-checked locally.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
evalcraft.devwas never registered (NXDOMAIN), yet shipped code + the landing page still referenced it. This scrubs every reference and ships 0.2.1.Changes
api.evalcraft.devdefault.base_urlresolves from the arg, thenEVALCRAFT_BASE_URL, then~/.evalcraft/config.json; a cloud call with none configured raises a clear self-host error instead of failing against a dead host.save_configwritesbase_urlonly when provided. New test covers it.evalcraft cloud --url: no default; theevalcraft initconfig-template example now points at a localhost self-host.site/CNAMEcomment cleared.Verification
evalcraft.devreferences remain outside the CHANGELOG (documents the fix) and privatelaunch/drafts.twine checkPASS (evalcraft-0.2.1).Merging + pushing the
v0.2.1tag publishes to PyPI.