chore(cli): prepare Effect v4 migration#3851
Open
Alberto Schiabel (jkomyno) wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
The Please review and fix the vulnerabilities. You can try running: pnpm audit --fix --prodAudit output |
Collaborator
Author
Not addressing in this PR: it does not change package manifests or the lockfile, and the reported advisory is in pre-existing Mastra runtime E2E dependency paths. This PR remains scoped to Effect v4 migration guidance and the read-only source oracle. |
This was referenced Jul 16, 2026
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
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.
Summary
Agents can now start the CLI's Effect v4 migration from a verified, repository-local baseline instead of translating APIs from memory. The production CLI remains on Effect v3; this PR establishes the migration guidance, exact beta matrix, source oracle, and behavior checks needed for later implementation slices.
The foundation deliberately keeps two versions separate:
ts/vendor/effecttracks upstream source for API investigation, while executable examples compile against the published4.0.0-beta.98packages. This prevents an unreleased upstream API from being mistaken for an installable CLI dependency.What reviewers should assess
effect-v4skill captures the Composio-specific CLI seams that are not mechanical renames: built-ins, suggestions, argument preprocessing, help/error rendering, andCommand.runWithbehavior.typescript-testingnow describes the current Effect v3 suite and the future v4@effect/vitestboundary without encouraging a premature mixed-version test graph.4f2107548fa64c21a8643b7b0efcd556cd16d4b9to upstreammainat80b539f8aba68f478c75c35c2b4140c4ffc4fada.No changeset is included because published package dependencies and runtime behavior are unchanged.
Validation
node .agents/skills/effect-v4/scripts/check-examples.mjs— all three Effect v4 examples compile against the exact beta matrix.pnpm validate:agent-skills— 16 canonical skills validated.pnpm validate:skill-routing— 16 routing probes pass.effect-v4andtypescript-testing.pnpm --filter @composio/cli typecheckandpnpm --filter @composio/cli buildpass.Effect-TS/effectmain.Post-Deploy Monitoring & Validation
No additional production monitoring is required because this PR changes agent guidance and a read-only source oracle, not the shipped CLI runtime. During the next migration slice, the SDK owner should treat the agent-skill validators, exact-beta example compiler, CLI typecheck/build, and CLI behavior suites as the healthy signals; any red check, beta misalignment, or help/output regression is the rollback trigger. Reverting this commit restores the previous guidance and gitlink.