Bump @tinacms/cli from 2.1.11 to 2.3.0

[dependabot]

Bumps @tinacms/cli from 2.1.11 to 2.3.0.

Release notes

Sourced from @​tinacms/cli's releases.

@​tinacms/cli@​2.3.0

Minor Changes

• #6738 4d0c37a Thanks @​joshbermanssw! - Stop writing generated files (_schema.json, _graphql.json, _lookup.json, tina-lock.json) to the content repo when localContentPath is set. Generated files now live only in the generator repo's tina/__generated__/. The content repo is no longer required to contain a tina/ folder. FilesystemBridge.get / put / delete now route tina/__generated__/ and .tina/__generated__/ paths to rootPath (the generator) instead of outputPath (the content root). Closes tinacms/tinacloud#3295.

  ⚠️ Rollout gate

  This release must not be promoted to the @latest dist-tag until TinaCloud prod has deployed tinacms/tinacloud#3403. Pre-#3403 TinaCloud reads tina-lock.json from the content repo on generator pushes; shipping this change before the server-side fix breaks every existing multi-repo user's indexing.

  Migration notes for existing multi-repo projects

  After upgrading (and once TinaCloud prod is on #3403):

  • Stale tina/ folder in your content repo. Pre-upgrade builds committed tina/__generated__/* and tina/tina-lock.json to the content repo. Nothing updates or reads those files any more. They are safe — and recommended — to delete from the content repo in a single cleanup commit.
  • ConfigManager.generatedFolderPathContentRepo is removed. If any custom CLI code, plugins, or scripts referenced this field, they will fail at type-check or runtime. Use generatedFolderPath — it has always been the generator-relative path.
  • ConfigManager.getTinaFolderPath no longer accepts an isContentRoot option. The content root never needs a tina/ folder now, so the option was removed. If any custom code called getTinaFolderPath(path, { isContentRoot: true }), drop the second argument.
  • FilesystemBridge behavior change for tina/__generated__/ paths. In multi-repo setups, bridge reads/writes of paths under tina/__generated__/ or .tina/__generated__/ now resolve against the generator (rootPath) rather than the content repo (outputPath). If you have custom bridge subclasses or code that relied on these paths resolving to the content repo, update it.
  • Generated client.ts / database-client.ts now import ./types extensionless (was ./types.ts) for TypeScript projects. Avoids requiring allowImportingTsExtensions: true in consumer tsconfigs, which broke the build under Next.js 15.5+ defaults. JS projects still import ./types.js (Node ESM requires the extension).

Patch Changes

• Updated dependencies [723632b, 95758a0, eafb1ff, 4d0c37a, 9e7eba9]:
  • tinacms@3.8.0
  • @​tinacms/graphql@​2.4.0
  • @​tinacms/metrics@​2.1.0
  • @​tinacms/app@​2.4.7
  • @​tinacms/search@​1.2.14

@​tinacms/cli@​2.2.6

Patch Changes

• #6770 3da4588 Thanks @​zaidkhatri-dev! - - Improved error handling for file and folder operations: errors are now shown as clear notifications in the UI rather than just logging to the console.

  • Fixed an issue where renaming a document to an already existing filename would silently fail; this now correctly triggers an error alert in the UI.

• #6739 7f66caa Thanks @​galsakuri! - Fix missing .js extension on ./types import in generated client.ts and databaseClient.ts

• #6758 63234a1 Thanks @​joshbermanssw! - ⚕️ adds tinacms doctor in CLI to check a project's direct TinaCMS package dependencies against the npm latest dist-tag

• #6776 c9e08ef Thanks @​kulesy! - Warn when a project still uses the legacy .tina/ config folder. tina-lock.json is only generated for the new tina/ layout, and TinaCloud requires it to index the schema, so projects on the legacy layout were silently failing the Project Setup Checklist. The warning fires once per CLI run from dev, build, and any other command that loads the config.

• Updated dependencies [3e4dcc7, 38cbec7, 3da4588, b37187d, 75f69a6, 556a162, 84ec7ad, 28b869a]:

  • tinacms@3.7.6
  • @​tinacms/graphql@​2.3.1
  • @​tinacms/schema-tools@​2.7.4
  • @​tinacms/search@​1.2.13
  • @​tinacms/app@​2.4.6
  • @​tinacms/metrics@​2.0.1

@​tinacms/cli@​2.2.5

... (truncated)

Changelog

Sourced from @​tinacms/cli's changelog.

2.3.0

Minor Changes

• #6738 4d0c37a Thanks @​joshbermanssw! - Stop writing generated files (_schema.json, _graphql.json, _lookup.json, tina-lock.json) to the content repo when localContentPath is set. Generated files now live only in the generator repo's tina/__generated__/. The content repo is no longer required to contain a tina/ folder. FilesystemBridge.get / put / delete now route tina/__generated__/ and .tina/__generated__/ paths to rootPath (the generator) instead of outputPath (the content root). Closes tinacms/tinacloud#3295.

  ⚠️ Rollout gate

  This release must not be promoted to the @latest dist-tag until TinaCloud prod has deployed tinacms/tinacloud#3403. Pre-#3403 TinaCloud reads tina-lock.json from the content repo on generator pushes; shipping this change before the server-side fix breaks every existing multi-repo user's indexing.

  Migration notes for existing multi-repo projects

  After upgrading (and once TinaCloud prod is on #3403):

  • Stale tina/ folder in your content repo. Pre-upgrade builds committed tina/__generated__/* and tina/tina-lock.json to the content repo. Nothing updates or reads those files any more. They are safe — and recommended — to delete from the content repo in a single cleanup commit.
  • ConfigManager.generatedFolderPathContentRepo is removed. If any custom CLI code, plugins, or scripts referenced this field, they will fail at type-check or runtime. Use generatedFolderPath — it has always been the generator-relative path.
  • ConfigManager.getTinaFolderPath no longer accepts an isContentRoot option. The content root never needs a tina/ folder now, so the option was removed. If any custom code called getTinaFolderPath(path, { isContentRoot: true }), drop the second argument.
  • FilesystemBridge behavior change for tina/__generated__/ paths. In multi-repo setups, bridge reads/writes of paths under tina/__generated__/ or .tina/__generated__/ now resolve against the generator (rootPath) rather than the content repo (outputPath). If you have custom bridge subclasses or code that relied on these paths resolving to the content repo, update it.
  • Generated client.ts / database-client.ts now import ./types extensionless (was ./types.ts) for TypeScript projects. Avoids requiring allowImportingTsExtensions: true in consumer tsconfigs, which broke the build under Next.js 15.5+ defaults. JS projects still import ./types.js (Node ESM requires the extension).

Patch Changes

• Updated dependencies [723632b, 95758a0, eafb1ff, 4d0c37a, 9e7eba9]:
  • tinacms@3.8.0
  • @​tinacms/graphql@​2.4.0
  • @​tinacms/metrics@​2.1.0
  • @​tinacms/app@​2.4.7
  • @​tinacms/search@​1.2.14

2.2.6

Patch Changes

• #6770 3da4588 Thanks @​zaidkhatri-dev! - - Improved error handling for file and folder operations: errors are now shown as clear notifications in the UI rather than just logging to the console.

  • Fixed an issue where renaming a document to an already existing filename would silently fail; this now correctly triggers an error alert in the UI.

• #6739 7f66caa Thanks @​galsakuri! - Fix missing .js extension on ./types import in generated client.ts and databaseClient.ts

• #6758 63234a1 Thanks @​joshbermanssw! - ⚕️ adds tinacms doctor in CLI to check a project's direct TinaCMS package dependencies against the npm latest dist-tag

• #6776 c9e08ef Thanks @​kulesy! - Warn when a project still uses the legacy .tina/ config folder. tina-lock.json is only generated for the new tina/ layout, and TinaCloud requires it to index the schema, so projects on the legacy layout were silently failing the Project Setup Checklist. The warning fires once per CLI run from dev, build, and any other command that loads the config.

• Updated dependencies [3e4dcc7, 38cbec7, 3da4588, b37187d, 75f69a6, 556a162, 84ec7ad, 28b869a]:

  • tinacms@3.7.6
  • @​tinacms/graphql@​2.3.1
  • @​tinacms/schema-tools@​2.7.4
  • @​tinacms/search@​1.2.13
  • @​tinacms/app@​2.4.6
  • @​tinacms/metrics@​2.0.1

... (truncated)

Commits

• 8cbed24 Version Packages (#6791)
• 4d0c37a feat(cli): tinacms dev & build support for localContentPath (no duplicate con...
• e537950 Version Packages (#6748)
• 3da4588 fix: show user-facing alerts for folder and file actions (#6770)
• c9e08ef feat(@​tinacms/cli): warn when project uses legacy .tina/ folder (#6776)
• 63234a1 tinacms doctor package command (#6758)
• 7f66caa fix(@​tinacms/cli): add .js extension to ./types import in generated client (f...
• 1dca21b Version Packages (#6741)
• a85b1c0 feat(schema-tools, cli): validate localContentPath + extract content-root res...
• e3fffc7 Version Packages (#6713)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)