Skip to content

feat(web): enable personal kits and collections APIs in production - #112

Merged
mrgoonie merged 2 commits into
mainfrom
chore/enable-personal-kits-collections
Oct 20, 2026
Merged

mrgoonie merged 2 commits into
mainfrom
chore/enable-personal-kits-collections

Conversation

@mrgoonie

Copy link
Copy Markdown
Contributor

Summary

Production preconditions (done)

  • Took a D1 Time Travel bookmark before migrating; it is stored in the owner's secret vault.
  • Applied migrations 0018 (registry_publishing) and 0019 (collection_revision_lineage) remotely.
  • Deployed main at fbd0333 (version 27d34bce) with both flags still "0". Smoke: /, search and registry keys return 200; /api/v1/collections returns 404 while the flag is off.

Rollback

For either API, set its flag back to "0" and redeploy. Its routes then return 404, and no data is touched.

Test plan

  • Config-only change: no code paths change. The flag-on behaviour is covered by the existing route tests, which set the env per test.
  • After merge: deploy, then run the personal kits smoke (CAS, private access, rollback) and the collections smoke.

Docs impact: docs/deployment-guide.md updated (flag state).

🤖 Generated with Claude Code

mrgoonie and others added 2 commits October 20, 2026 09:35
Both APIs shipped behind flags that defaulted to off. Migrations 0018 and
0019 are applied to production D1, so the flags can be enabled. Rollback for
either API: set its flag back to "0" and redeploy.

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

Copy link
Copy Markdown
Contributor Author

Production D1 migration evidence (2026-10-20 09:40 +07): wrangler d1 migrations list skillx-db --remote → No migrations to apply!; d1_migrations contains 0015_personal_kits, 0016_personal_kit_proposals, 0018_registry_publishing, 0019_collection_revision_lineage. Head 71b5a22 adds the migration prerequisites and rollback to the flag comments and the deployment guide.

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.

1 participant