@botonic/create-workspace 2.29.0 → 2.30.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,3 +1,13 @@
1
+ ## 2.30.0 (2026-06-11)
2
+
3
+ ### šŸš€ Features
4
+
5
+ - support botonic v2 preview in flow builder ([#916](https://github.com/metis-ai/hubtype-product/pull/916))
6
+
7
+ ### ā¤ļø Thank You
8
+
9
+ - Marc Rabat @vanbasten17
10
+
1
11
  ## 2.29.0 (2026-05-12)
2
12
 
3
13
  This was a version bump only for @botonic/create-workspace to align it with other projects, there were no code changes.
@@ -95,7 +95,11 @@ try {
95
95
  console.log(`\nšŸ“ Created .npmrc with custom registry: ${registry}`)
96
96
  }
97
97
 
98
- const installPluginCommand = `pnpm add -D @botonic/nx-plugin`
98
+ // --no-strict-peer-dependencies: @nx/react@21 depends on @nx/vite@21 which declares
99
+ // vitest@^1||^2||^3 as a peer. In a Verdaccio-backed workspace only workspace packages
100
+ // are published, so pnpm can't resolve vitest@3.x and fails. The bot-app itself uses
101
+ // vitest@4; we install the correct version later when the generated package.json lands.
102
+ const installPluginCommand = `pnpm add -D @botonic/nx-plugin --no-strict-peer-dependencies`
99
103
 
100
104
  console.log(
101
105
  `\nšŸ“¦ Installing Botonic plugin from ${registry || 'public npm'}: ${installPluginCommand}`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@botonic/create-workspace",
3
- "version": "2.29.0",
3
+ "version": "2.30.0",
4
4
  "description": "Create a new workspace for Botonic bot development",
5
5
  "main": "index.js",
6
6
  "bin": {