chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

stack-effect@0.18.0

Minor Changes

• f820f29: Target names now support nested directories while keeping npm package names flat.

  For example, package/sdk/client creates packages/sdk/client with the name @repo/sdk-client, and server/sdk/api creates apps/sdk/server-api with the name server-sdk-api. Additions use the same target name to find the existing package. Conflicting package names and overlapping package roots are rejected before files are written.

  Generated workspaces register package owners explicitly so nested template manifests do not interfere with dependency installation.

• 1665149: Catalog templates can select content based on the modules attached to a target with module and noModule conditions.

  Publishable libraries now use one package.json for workspace use and npm publication. Build before importing the library in the workspace, use npm run dev to watch changes, and run npm run pack or npm publish from the library directory.

Patch Changes

• 674dea4: Skip unsupported target kinds when generating catalog authoring workspaces for Deno.

@stack-effect/author@0.3.0

Minor Changes

• f820f29: Target names now support nested directories while keeping npm package names flat.

  For example, package/sdk/client creates packages/sdk/client with the name @repo/sdk-client, and server/sdk/api creates apps/sdk/server-api with the name server-sdk-api. Additions use the same target name to find the existing package. Conflicting package names and overlapping package roots are rejected before files are written.

  Generated workspaces register package owners explicitly so nested template manifests do not interfere with dependency installation.

• 1665149: Catalog templates can select content based on the modules attached to a target with module and noModule conditions.

  Publishable libraries now use one package.json for workspace use and npm publication. Build before importing the library in the workspace, use npm run dev to watch changes, and run npm run pack or npm publish from the library directory.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
stack-effect-docs	Ready	Preview	Oct 12, 2026 11:21am UTC