Skip to content

chore(release): version packages#2

Open
github-actions[bot] wants to merge 1 commit intomainfrom
changeset-release/main
Open

chore(release): version packages#2
github-actions[bot] wants to merge 1 commit intomainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions bot commented Apr 9, 2026

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

@zvndev/yable-core@0.2.1

Patch Changes

  • 7d0ffa2: Gold-standard hardening sprint.
    • Security: tighten CSS value sanitization in createTheme() to strip all four structural CSS characters ({, }, ;, :) — previously only {}; were stripped, leaving an a: b injection vector.
    • Error handling: prefix 11 production error sites with [yable E###] codes. Canonical reference at docs/errors.md.
    • Build: declare sideEffects: false on all public packages for better tree-shaking.
    • Types: enable noUncheckedIndexedAccess repo-wide and fix surfaced index-access paths.
    • Testing: +5 property-based fuzz tests for the formula parser, +19 vanilla renderer XSS tests, +33 theme sanitizer tests, shared makeTableState fixture factory.
    • CI: parallel workflow with lint / typecheck / build / test (Node 20 and 22 matrix) / size-limit / audit jobs.
    • Release engineering: changesets with fixed-group versioning across all four packages, canary channel on merge-to-main, stable on tag.
    • Docs: SECURITY, CODE_OF_CONDUCT, CHANGELOG, FLAGS, docs/errors.md, and full truth-audit of README / AGENTS / FEATURES / CONTRIBUTING / landing page (removed stale "coming soon" markers on features that already ship).

@zvndev/yable-react@0.2.1

Patch Changes

  • 7d0ffa2: Gold-standard hardening sprint.

    • Security: tighten CSS value sanitization in createTheme() to strip all four structural CSS characters ({, }, ;, :) — previously only {}; were stripped, leaving an a: b injection vector.
    • Error handling: prefix 11 production error sites with [yable E###] codes. Canonical reference at docs/errors.md.
    • Build: declare sideEffects: false on all public packages for better tree-shaking.
    • Types: enable noUncheckedIndexedAccess repo-wide and fix surfaced index-access paths.
    • Testing: +5 property-based fuzz tests for the formula parser, +19 vanilla renderer XSS tests, +33 theme sanitizer tests, shared makeTableState fixture factory.
    • CI: parallel workflow with lint / typecheck / build / test (Node 20 and 22 matrix) / size-limit / audit jobs.
    • Release engineering: changesets with fixed-group versioning across all four packages, canary channel on merge-to-main, stable on tag.
    • Docs: SECURITY, CODE_OF_CONDUCT, CHANGELOG, FLAGS, docs/errors.md, and full truth-audit of README / AGENTS / FEATURES / CONTRIBUTING / landing page (removed stale "coming soon" markers on features that already ship).
  • Updated dependencies [7d0ffa2]

    • @zvndev/yable-core@0.2.1
    • @zvndev/yable-themes@0.2.1

@zvndev/yable-themes@0.2.1

Patch Changes

  • 7d0ffa2: Gold-standard hardening sprint.
    • Security: tighten CSS value sanitization in createTheme() to strip all four structural CSS characters ({, }, ;, :) — previously only {}; were stripped, leaving an a: b injection vector.
    • Error handling: prefix 11 production error sites with [yable E###] codes. Canonical reference at docs/errors.md.
    • Build: declare sideEffects: false on all public packages for better tree-shaking.
    • Types: enable noUncheckedIndexedAccess repo-wide and fix surfaced index-access paths.
    • Testing: +5 property-based fuzz tests for the formula parser, +19 vanilla renderer XSS tests, +33 theme sanitizer tests, shared makeTableState fixture factory.
    • CI: parallel workflow with lint / typecheck / build / test (Node 20 and 22 matrix) / size-limit / audit jobs.
    • Release engineering: changesets with fixed-group versioning across all four packages, canary channel on merge-to-main, stable on tag.
    • Docs: SECURITY, CODE_OF_CONDUCT, CHANGELOG, FLAGS, docs/errors.md, and full truth-audit of README / AGENTS / FEATURES / CONTRIBUTING / landing page (removed stale "coming soon" markers on features that already ship).

@zvndev/yable-vanilla@0.2.1

Patch Changes

  • 7d0ffa2: Gold-standard hardening sprint.

    • Security: tighten CSS value sanitization in createTheme() to strip all four structural CSS characters ({, }, ;, :) — previously only {}; were stripped, leaving an a: b injection vector.
    • Error handling: prefix 11 production error sites with [yable E###] codes. Canonical reference at docs/errors.md.
    • Build: declare sideEffects: false on all public packages for better tree-shaking.
    • Types: enable noUncheckedIndexedAccess repo-wide and fix surfaced index-access paths.
    • Testing: +5 property-based fuzz tests for the formula parser, +19 vanilla renderer XSS tests, +33 theme sanitizer tests, shared makeTableState fixture factory.
    • CI: parallel workflow with lint / typecheck / build / test (Node 20 and 22 matrix) / size-limit / audit jobs.
    • Release engineering: changesets with fixed-group versioning across all four packages, canary channel on merge-to-main, stable on tag.
    • Docs: SECURITY, CODE_OF_CONDUCT, CHANGELOG, FLAGS, docs/errors.md, and full truth-audit of README / AGENTS / FEATURES / CONTRIBUTING / landing page (removed stale "coming soon" markers on features that already ship).
  • Updated dependencies [7d0ffa2]

    • @zvndev/yable-core@0.2.1
    • @zvndev/yable-themes@0.2.1

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 9, 2026

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

Project Deployment Actions Updated (UTC)
yable-demo Error Error Apr 9, 2026 9:06pm

Request Review

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.

0 participants