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

@baseplate-dev/core-generators@0.2.5

Patch Changes

• #613 2aae451 Thanks @kingston! - Add $templateName syntax for intra-generator template references

  Templates can now reference other templates within the same generator using the $templateName syntax. This enables templates to access file paths of other templates in the same generator during generation.

  Key features:

  • Use $templateName in template files to reference other generator templates
  • Kebab-case template names are automatically converted to camelCase (e.g., session-constants → sessionConstants)
  • Configure referenced templates using the referencedGeneratorTemplates field in extractor.json
  • Works seamlessly with existing variable replacement and import maps
  • Provides clear error messages for missing template references

  Example usage:

  // In template file
  import { Constants } from '$sessionConstants';
  import { Utils } from '$authUtils';
  
  // In extractor.json
  {
    "user-service": {
      "sourceFile": "services/user.service.ts",
      "referencedGeneratorTemplates": ["session-constants", "auth-utils"]
    }
  }

  This feature is designed for intra-generator template references only. For cross-generator references, continue using import map providers.

• Updated dependencies [e0d690c]:

  • @baseplate-dev/sync@0.2.5
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/create-project@0.2.5

Patch Changes

• Updated dependencies []:
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/fastify-generators@0.2.5

Patch Changes

• #608 01c47c7 Thanks @kingston! - Fix pothos writer to write typed args correctly (t.arg.string instead of t.string)

• Updated dependencies [e0d690c, 2aae451]:

  • @baseplate-dev/sync@0.2.5
  • @baseplate-dev/core-generators@0.2.5
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/project-builder-cli@0.2.5

Patch Changes

• #614 e0d690c Thanks @kingston! - Add .baseplateignore support and sync command with force-overwrite

  Enhance the baseplate diff command to support ignore patterns via a .baseplateignore file, similar to .gitignore. This reduces noise in diff output by filtering out expected differences like environment files, logs, and build artifacts.

  Additionally, introduces a new baseplate sync command (replacing build) with a --force-overwrite flag that respects ignore patterns when overwriting files.

  Features:

  • Uses .baseplateignore file in project root with gitignore-style syntax
  • Includes sensible default patterns (.env, *.log, node_modules/, dist/, build/, .DS_Store, Thumbs.db)
  • Can be disabled with --no-ignore-file flag
  • Backward compatible (enabled by default)
  • Graceful fallback when .baseplateignore doesn't exist

• #614 e0d690c Thanks @kingston! - Add force overwrite mode for sync command

  Adds a --force-overwrite flag to the baseplate sync command that bypasses merge conflict detection and overwrites existing files with generated content without attempting to merge changes. When force overwrite is enabled, files matching patterns in .baseplateignore are automatically excluded from being overwritten to preserve user customizations.

  Also updates the diff command to load .baseplateignore patterns from each app directory instead of the base directory, providing more granular control over which files are ignored during diff operations.

• Updated dependencies [e0d690c, e0d690c, 01c47c7]:

  • @baseplate-dev/project-builder-server@0.2.5
  • @baseplate-dev/project-builder-lib@0.2.5
  • @baseplate-dev/project-builder-web@0.2.5
  • @baseplate-dev/project-builder-common@0.2.5
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/project-builder-common@0.2.5

Patch Changes

• Updated dependencies [e0d690c, e0d690c, 01c47c7, 01c47c7, 01c47c7]:
  • @baseplate-dev/project-builder-server@0.2.5
  • @baseplate-dev/sync@0.2.5
  • @baseplate-dev/project-builder-lib@0.2.5
  • @baseplate-dev/plugin-auth@1.0.5
  • @baseplate-dev/plugin-storage@1.0.5

@baseplate-dev/project-builder-lib@0.2.5

Patch Changes

• #608 01c47c7 Thanks @kingston! - Refactor plugin migration system to separate config and project definition changes

  Previously, plugin migrations had mixed responsibilities - both transforming plugin config and mutating the project definition in the same unclear contract. This made the system hard to test and reason about.

  New Migration Interface:

  • PluginMigrationResult with explicit updatedConfig and updateProjectDefinition properties
  • Clear separation between config transformations and project definition updates
  • Better type safety and testability

  Schema Version Bug Fix:

  • Fixed bug where enabling plugins via UI didn't set configSchemaVersion
  • Plugin card now uses PluginUtils.setPluginConfig to automatically set correct schema version
  • Prevents unnecessary migrations when enabling new plugins

  Migration Updates:

  • All existing migrations updated to use new interface
  • Auth plugin migration: simple config-only transformation
  • Storage plugin migrations: migration Refactor generator v2 #1 (config-only), migration Add GitHub workflows #2 (config + project updates)

• Updated dependencies [e0d690c]:

  • @baseplate-dev/sync@0.2.5
  • @baseplate-dev/ui-components@0.2.5
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/project-builder-server@0.2.5

Patch Changes

• #614 e0d690c Thanks @kingston! - Add .baseplateignore support and sync command with force-overwrite

  Enhance the baseplate diff command to support ignore patterns via a .baseplateignore file, similar to .gitignore. This reduces noise in diff output by filtering out expected differences like environment files, logs, and build artifacts.

  Additionally, introduces a new baseplate sync command (replacing build) with a --force-overwrite flag that respects ignore patterns when overwriting files.

  Features:

  • Uses .baseplateignore file in project root with gitignore-style syntax
  • Includes sensible default patterns (.env, *.log, node_modules/, dist/, build/, .DS_Store, Thumbs.db)
  • Can be disabled with --no-ignore-file flag
  • Backward compatible (enabled by default)
  • Graceful fallback when .baseplateignore doesn't exist

• #614 e0d690c Thanks @kingston! - Add force overwrite mode for sync command

  Adds a --force-overwrite flag to the baseplate sync command that bypasses merge conflict detection and overwrites existing files with generated content without attempting to merge changes. When force overwrite is enabled, files matching patterns in .baseplateignore are automatically excluded from being overwritten to preserve user customizations.

  Also updates the diff command to load .baseplateignore patterns from each app directory instead of the base directory, providing more granular control over which files are ignored during diff operations.

• Updated dependencies [2aae451, 01c47c7, e0d690c, 01c47c7, 01c47c7, 2aae451]:

  • @baseplate-dev/react-generators@0.2.5
  • @baseplate-dev/fastify-generators@0.2.5
  • @baseplate-dev/sync@0.2.5
  • @baseplate-dev/project-builder-lib@0.2.5
  • @baseplate-dev/core-generators@0.2.5
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/project-builder-web@0.2.5

Patch Changes

• #608 01c47c7 Thanks @kingston! - Refactor plugin migration system to separate config and project definition changes

  Previously, plugin migrations had mixed responsibilities - both transforming plugin config and mutating the project definition in the same unclear contract. This made the system hard to test and reason about.

  New Migration Interface:

  • PluginMigrationResult with explicit updatedConfig and updateProjectDefinition properties
  • Clear separation between config transformations and project definition updates
  • Better type safety and testability

  Schema Version Bug Fix:

  • Fixed bug where enabling plugins via UI didn't set configSchemaVersion
  • Plugin card now uses PluginUtils.setPluginConfig to automatically set correct schema version
  • Prevents unnecessary migrations when enabling new plugins

  Migration Updates:

  • All existing migrations updated to use new interface
  • Auth plugin migration: simple config-only transformation
  • Storage plugin migrations: migration Refactor generator v2 #1 (config-only), migration Add GitHub workflows #2 (config + project updates)

• Updated dependencies [01c47c7]:

  • @baseplate-dev/project-builder-lib@0.2.5
  • @baseplate-dev/ui-components@0.2.5
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/react-generators@0.2.5

Patch Changes

• #613 2aae451 Thanks @kingston! - Reorganize components folder structure in generated codebases

  The components folder structure has been reorganized to improve organization and reduce bundle size:

  Breaking Changes:

  • Removed bundle export at components/index.ts to prevent importing all components at once
  • Moved all UI components from components/ to components/ui/ folder

  New Structure:

  components/
  ├── ui/           # UI components
  │   ├── button.tsx
  │   ├── input.tsx
  │   └── ...
  └── [other-components]  # Custom application components
  

  Migration:

  • Replace import { Button } from '@src/components' with import { Button } from '@src/components/ui/button'
  • Update imports to use specific component paths instead of barrel exports
  • UI components are now co-located in the ui/ subfolder for better organization

  This change improves tree-shaking, reduces bundle size, and provides clearer separation between UI library components and custom application components.

• #608 01c47c7 Thanks @kingston! - Remove changeOrigin: true from vite proxy to allow custom auth plugin to work

• Updated dependencies [e0d690c, 2aae451]:

  • @baseplate-dev/sync@0.2.5
  • @baseplate-dev/core-generators@0.2.5
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/sync@0.2.5

Patch Changes

• #614 e0d690c Thanks @kingston! - Add force overwrite mode for sync command

  Adds a --force-overwrite flag to the baseplate sync command that bypasses merge conflict detection and overwrites existing files with generated content without attempting to merge changes. When force overwrite is enabled, files matching patterns in .baseplateignore are automatically excluded from being overwritten to preserve user customizations.

  Also updates the diff command to load .baseplateignore patterns from each app directory instead of the base directory, providing more granular control over which files are ignored during diff operations.

• Updated dependencies []:

  • @baseplate-dev/utils@0.2.5

@baseplate-dev/ui-components@0.2.5

Patch Changes

• Updated dependencies []:
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/plugin-auth@1.0.5

Patch Changes

• #608 01c47c7 Thanks @kingston! - Refactor plugin migration system to separate config and project definition changes

  Previously, plugin migrations had mixed responsibilities - both transforming plugin config and mutating the project definition in the same unclear contract. This made the system hard to test and reason about.

  New Migration Interface:

  • PluginMigrationResult with explicit updatedConfig and updateProjectDefinition properties
  • Clear separation between config transformations and project definition updates
  • Better type safety and testability

  Schema Version Bug Fix:

  • Fixed bug where enabling plugins via UI didn't set configSchemaVersion
  • Plugin card now uses PluginUtils.setPluginConfig to automatically set correct schema version
  • Prevents unnecessary migrations when enabling new plugins

  Migration Updates:

  • All existing migrations updated to use new interface
  • Auth plugin migration: simple config-only transformation
  • Storage plugin migrations: migration Refactor generator v2 #1 (config-only), migration Add GitHub workflows #2 (config + project updates)

• #608 01c47c7 Thanks @kingston! - Add React app configuration wrapper for user session provider and add useLogOut.gql file

• Updated dependencies [2aae451, 01c47c7, e0d690c, 01c47c7, 01c47c7, 2aae451]:

  • @baseplate-dev/react-generators@0.2.5
  • @baseplate-dev/fastify-generators@0.2.5
  • @baseplate-dev/sync@0.2.5
  • @baseplate-dev/project-builder-lib@0.2.5
  • @baseplate-dev/core-generators@0.2.5
  • @baseplate-dev/ui-components@0.2.5

@baseplate-dev/plugin-storage@1.0.5

Patch Changes

• #608 01c47c7 Thanks @kingston! - Refactor plugin migration system to separate config and project definition changes

  Previously, plugin migrations had mixed responsibilities - both transforming plugin config and mutating the project definition in the same unclear contract. This made the system hard to test and reason about.

  New Migration Interface:

  • PluginMigrationResult with explicit updatedConfig and updateProjectDefinition properties
  • Clear separation between config transformations and project definition updates
  • Better type safety and testability

  Schema Version Bug Fix:

  • Fixed bug where enabling plugins via UI didn't set configSchemaVersion
  • Plugin card now uses PluginUtils.setPluginConfig to automatically set correct schema version
  • Prevents unnecessary migrations when enabling new plugins

  Migration Updates:

  • All existing migrations updated to use new interface
  • Auth plugin migration: simple config-only transformation
  • Storage plugin migrations: migration Refactor generator v2 #1 (config-only), migration Add GitHub workflows #2 (config + project updates)

• #608 01c47c7 Thanks @kingston! - Make uploaderId optional in data model

• Updated dependencies [2aae451, 01c47c7, e0d690c, 01c47c7, 01c47c7, 2aae451]:

  • @baseplate-dev/react-generators@0.2.5
  • @baseplate-dev/fastify-generators@0.2.5
  • @baseplate-dev/sync@0.2.5
  • @baseplate-dev/project-builder-lib@0.2.5
  • @baseplate-dev/core-generators@0.2.5
  • @baseplate-dev/ui-components@0.2.5
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/tools@0.2.5

@baseplate-dev/utils@0.2.5

@baseplate-dev/project-builder-test@0.2.5

Patch Changes

• Updated dependencies [e0d690c, e0d690c, 01c47c7]:
  • @baseplate-dev/project-builder-server@0.2.5
  • @baseplate-dev/sync@0.2.5
  • @baseplate-dev/project-builder-lib@0.2.5
  • @baseplate-dev/project-builder-web@0.2.5
  • @baseplate-dev/project-builder-common@0.2.5
  • @baseplate-dev/utils@0.2.5

@baseplate-dev/code-morph@0.2.5

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
baseplate-project-builder-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 16, 2025 8:17pm

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.