Skip to content

chore: migrate to pnpm and fix default value resolution for coercion schemas#21

Merged
CatchMe2 merged 3 commits into
mainfrom
migrate-to-pnpm
May 19, 2026
Merged

chore: migrate to pnpm and fix default value resolution for coercion schemas#21
CatchMe2 merged 3 commits into
mainfrom
migrate-to-pnpm

Conversation

@CatchMe2
Copy link
Copy Markdown
Owner

@CatchMe2 CatchMe2 commented May 19, 2026

  • Migrates package manager from npm to pnpm 11.1.0: updates packageManager
    in package.json, replaces package-lock.json with pnpm-lock.yaml, and
    updates all three GitHub Actions workflows (ci.yml, publish.yml,
    bump-version.yml) to use pnpm/action-setup@v4 with pinned SHAs
  • Fixes default not appearing in generated markdown for coercion schemas
    (e.g. z.stringbool().default(false)): Zod v4 places the default on the
    output JSON schema rather than the input schema for these types
  • Extends the fix to all metadata fields by merging input and output schemas
    ({ ...outputSchema, ...inputSchema }), so input takes precedence for
    constraints/enum while output fills in gaps for post-coercion fields
  • Makes generateMarkdown async and awaits validate() to support async
    Standard Schema implementations; fixes optional detection to use
    !issues per the spec rather than 'value' in result

@CatchMe2 CatchMe2 changed the title chore: migrate to pnpm chore: migrate to pnpm and fix default value resolution for coercion schemas May 19, 2026
@CatchMe2 CatchMe2 merged commit 1d1622d into main May 19, 2026
4 checks passed
@CatchMe2 CatchMe2 deleted the migrate-to-pnpm branch May 19, 2026 11:55
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