Skip to content

feat(core): gate experimental integrations behind an env var - #88

Merged
ldelvoye merged 1 commit into
mainfrom
feat/experimental-integrations
Sep 16, 2026
Merged

ldelvoye merged 1 commit into
mainfrom
feat/experimental-integrations

Conversation

@ldelvoye

Copy link
Copy Markdown
Owner

Adds an experimental flag to Manifest. The registry only registers an experimental integration when SMORG_EXPERIMENTAL names it, comma-separated, so SMORG_EXPERIMENTAL=gcal smorg brings the calendar back and a plain run does not see it at all.

gcal is three milestones in and already on main, so cutting any release from main today would offer a half-built Google Calendar tab to everyone on the tap. With the flag, main carries the code and offers nothing. Milestone 6 drops it.

tests/test_seams.py now walks INTEGRATIONS instead of manifests(): hiding an integration from a run must not hide its action keys from the check that they are bound.

A manifest can mark itself experimental, and the registry registers it
only when SMORG_EXPERIMENTAL names it. gcal is the first: its code is on
main three milestones in, and without this a release would offer the
half-built tab to everyone.
@ldelvoye
ldelvoye merged commit 8870d63 into main Sep 16, 2026
1 check passed
@ldelvoye
ldelvoye deleted the feat/experimental-integrations branch September 16, 2026 22:39
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