Version Packages (beta)

[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.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@vayo-hq/ast@0.1.1-beta.2

Patch Changes

• 5ad2159: Fixed every package README still linking to the old, never-actually-published
  bare vayo npm package name (npm rejected it as a first-publish
  typosquat — see the CLI rename changeset) instead of the real
  @vayo-hq/cli. Also fixed @vayo-hq/db-mongo's README claiming "most people
  never call this directly," which contradicted the createAdapter/
  runMigrations wiring snippet every other doc (and vayo init's own printed
  next steps) shows being called directly in a real project. Root README's
  "Using Vayo" section no longer describes the pre-publish tarball workflow —
  all 9 packages are live on npm now, so it gives the real, verified
  npm install ...@beta command instead. Every install example across the
  repo now explicit about the @beta tag rather than relying on latest,
  since latest only moves when explicitly re-tagged during this prerelease
  period (discovered live: the very first publish grabbed latest
  automatically and every subsequent --tag beta publish left it pointing at
  an old, broken version).
• Updated dependencies [5ad2159]
  • @vayo-hq/types@0.1.1-beta.2

@vayo-hq/capture-express@0.1.1-beta.2

Patch Changes

• 5ad2159: Fixed every package README still linking to the old, never-actually-published
  bare vayo npm package name (npm rejected it as a first-publish
  typosquat — see the CLI rename changeset) instead of the real
  @vayo-hq/cli. Also fixed @vayo-hq/db-mongo's README claiming "most people
  never call this directly," which contradicted the createAdapter/
  runMigrations wiring snippet every other doc (and vayo init's own printed
  next steps) shows being called directly in a real project. Root README's
  "Using Vayo" section no longer describes the pre-publish tarball workflow —
  all 9 packages are live on npm now, so it gives the real, verified
  npm install ...@beta command instead. Every install example across the
  repo now explicit about the @beta tag rather than relying on latest,
  since latest only moves when explicitly re-tagged during this prerelease
  period (discovered live: the very first publish grabbed latest
  automatically and every subsequent --tag beta publish left it pointing at
  an old, broken version).
• Updated dependencies [5ad2159]
  • @vayo-hq/types@0.1.1-beta.2
  • @vayo-hq/schema-engine@0.1.1-beta.2

@vayo-hq/cli@0.1.1-beta.2

Patch Changes

• 5ad2159: Fixed every package README still linking to the old, never-actually-published
  bare vayo npm package name (npm rejected it as a first-publish
  typosquat — see the CLI rename changeset) instead of the real
  @vayo-hq/cli. Also fixed @vayo-hq/db-mongo's README claiming "most people
  never call this directly," which contradicted the createAdapter/
  runMigrations wiring snippet every other doc (and vayo init's own printed
  next steps) shows being called directly in a real project. Root README's
  "Using Vayo" section no longer describes the pre-publish tarball workflow —
  all 9 packages are live on npm now, so it gives the real, verified
  npm install ...@beta command instead. Every install example across the
  repo now explicit about the @beta tag rather than relying on latest,
  since latest only moves when explicitly re-tagged during this prerelease
  period (discovered live: the very first publish grabbed latest
  automatically and every subsequent --tag beta publish left it pointing at
  an old, broken version).
• Updated dependencies [5ad2159]
  • @vayo-hq/types@0.1.1-beta.2
  • @vayo-hq/ast@0.1.1-beta.2
  • @vayo-hq/schema-engine@0.1.1-beta.2
  • @vayo-hq/openapi-compiler@0.1.1-beta.2
  • @vayo-hq/db-mongo@0.1.1-beta.2
  • @vayo-hq/server@0.1.1-beta.2

@vayo-hq/db-mongo@0.1.1-beta.2

Patch Changes

• 5ad2159: Fixed every package README still linking to the old, never-actually-published
  bare vayo npm package name (npm rejected it as a first-publish
  typosquat — see the CLI rename changeset) instead of the real
  @vayo-hq/cli. Also fixed @vayo-hq/db-mongo's README claiming "most people
  never call this directly," which contradicted the createAdapter/
  runMigrations wiring snippet every other doc (and vayo init's own printed
  next steps) shows being called directly in a real project. Root README's
  "Using Vayo" section no longer describes the pre-publish tarball workflow —
  all 9 packages are live on npm now, so it gives the real, verified
  npm install ...@beta command instead. Every install example across the
  repo now explicit about the @beta tag rather than relying on latest,
  since latest only moves when explicitly re-tagged during this prerelease
  period (discovered live: the very first publish grabbed latest
  automatically and every subsequent --tag beta publish left it pointing at
  an old, broken version).
• Updated dependencies [5ad2159]
  • @vayo-hq/types@0.1.1-beta.2
  • @vayo-hq/schema-engine@0.1.1-beta.2

@vayo-hq/openapi-compiler@0.1.1-beta.2

Patch Changes

• 5ad2159: Fixed every package README still linking to the old, never-actually-published
  bare vayo npm package name (npm rejected it as a first-publish
  typosquat — see the CLI rename changeset) instead of the real
  @vayo-hq/cli. Also fixed @vayo-hq/db-mongo's README claiming "most people
  never call this directly," which contradicted the createAdapter/
  runMigrations wiring snippet every other doc (and vayo init's own printed
  next steps) shows being called directly in a real project. Root README's
  "Using Vayo" section no longer describes the pre-publish tarball workflow —
  all 9 packages are live on npm now, so it gives the real, verified
  npm install ...@beta command instead. Every install example across the
  repo now explicit about the @beta tag rather than relying on latest,
  since latest only moves when explicitly re-tagged during this prerelease
  period (discovered live: the very first publish grabbed latest
  automatically and every subsequent --tag beta publish left it pointing at
  an old, broken version).
• Updated dependencies [5ad2159]
  • @vayo-hq/types@0.1.1-beta.2
  • @vayo-hq/schema-engine@0.1.1-beta.2

@vayo-hq/schema-engine@0.1.1-beta.2

Patch Changes

• 5ad2159: Fixed every package README still linking to the old, never-actually-published
  bare vayo npm package name (npm rejected it as a first-publish
  typosquat — see the CLI rename changeset) instead of the real
  @vayo-hq/cli. Also fixed @vayo-hq/db-mongo's README claiming "most people
  never call this directly," which contradicted the createAdapter/
  runMigrations wiring snippet every other doc (and vayo init's own printed
  next steps) shows being called directly in a real project. Root README's
  "Using Vayo" section no longer describes the pre-publish tarball workflow —
  all 9 packages are live on npm now, so it gives the real, verified
  npm install ...@beta command instead. Every install example across the
  repo now explicit about the @beta tag rather than relying on latest,
  since latest only moves when explicitly re-tagged during this prerelease
  period (discovered live: the very first publish grabbed latest
  automatically and every subsequent --tag beta publish left it pointing at
  an old, broken version).
• Updated dependencies [5ad2159]
  • @vayo-hq/types@0.1.1-beta.2

@vayo-hq/server@0.1.1-beta.2

Patch Changes

• 5ad2159: Fixed every package README still linking to the old, never-actually-published
  bare vayo npm package name (npm rejected it as a first-publish
  typosquat — see the CLI rename changeset) instead of the real
  @vayo-hq/cli. Also fixed @vayo-hq/db-mongo's README claiming "most people
  never call this directly," which contradicted the createAdapter/
  runMigrations wiring snippet every other doc (and vayo init's own printed
  next steps) shows being called directly in a real project. Root README's
  "Using Vayo" section no longer describes the pre-publish tarball workflow —
  all 9 packages are live on npm now, so it gives the real, verified
  npm install ...@beta command instead. Every install example across the
  repo now explicit about the @beta tag rather than relying on latest,
  since latest only moves when explicitly re-tagged during this prerelease
  period (discovered live: the very first publish grabbed latest
  automatically and every subsequent --tag beta publish left it pointing at
  an old, broken version).
• Updated dependencies [5ad2159]
  • @vayo-hq/types@0.1.1-beta.2
  • @vayo-hq/schema-engine@0.1.1-beta.2
  • @vayo-hq/openapi-compiler@0.1.1-beta.2
  • @vayo-hq/db-mongo@0.1.1-beta.2
  • @vayo-hq/ui@0.1.1-beta.2

@vayo-hq/types@0.1.1-beta.2

Patch Changes

• 5ad2159: Fixed every package README still linking to the old, never-actually-published
  bare vayo npm package name (npm rejected it as a first-publish
  typosquat — see the CLI rename changeset) instead of the real
  @vayo-hq/cli. Also fixed @vayo-hq/db-mongo's README claiming "most people
  never call this directly," which contradicted the createAdapter/
  runMigrations wiring snippet every other doc (and vayo init's own printed
  next steps) shows being called directly in a real project. Root README's
  "Using Vayo" section no longer describes the pre-publish tarball workflow —
  all 9 packages are live on npm now, so it gives the real, verified
  npm install ...@beta command instead. Every install example across the
  repo now explicit about the @beta tag rather than relying on latest,
  since latest only moves when explicitly re-tagged during this prerelease
  period (discovered live: the very first publish grabbed latest
  automatically and every subsequent --tag beta publish left it pointing at
  an old, broken version).

@vayo-hq/ui@0.1.1-beta.2

Patch Changes

• Updated dependencies [5ad2159]
  • @vayo-hq/types@0.1.1-beta.2
  • @vayo-hq/openapi-compiler@0.1.1-beta.2