v0.23.6

This release consolidates the changes made since v0.23.1, focusing on package documentation and a more reliable release and publishing process.

Documentation

• Added dedicated README files across all Verikit packages.
• Updated the main project README.
• Simplified source-code comments for clearer package documentation.

Release automation

• Added automated npm publishing through GitHub Actions.
• Added npm Trusted Publishing using OIDC, removing the need for long-lived npm authentication tokens.
• Added release validation to prevent publishing packages with mismatched versions.
• Added pnpm vsync --check for verifying that all workspace package versions match the root version.
• Improved vsync to make version releases atomic.
• Added support for:
  • pnpm vsync patch
  • pnpm vsync minor
  • pnpm vsync major
• Version bumps now update the root and all workspace packages together.
• Release commits and Git tags are now created from the same synchronized state, preventing tags from pointing to commits with stale package versions.
• Release tags remain explicitly pushed, keeping publishing an intentional operation.

CI

• Added release-time build and package smoke-test validation.
• Configured the publishing workflow for Node.js 24 and pnpm 11.
• Added package-version consistency checks before npm publishing.
• Improved pnpm 11 CI configuration for upgrade-compatible setup.

Publishing

All Verikit workspace packages are now published through the same validated release pipeline:

• @verikit/core
• @verikit/runtime
• @verikit/server
• @verikit/client
• @verikit/react
• @verikit/vue
• @verikit/ui-core
• @verikit/theme
• @verikit/prisma
• @verikit/drizzle

Publishing now uses npm Trusted Publishing through GitHub Actions with OIDC. Published packages include npm provenance, providing verifiable information linking package artifacts back to the Verikit GitHub repository and release workflow.

Upgrade

pnpm update '@verikit/*'

Full Changelog: v0.23.1...v0.23.6