Skip to content

chore(deps-dev): bump @tinacms/cli from 2.1.11 to 2.3.1#177

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/tinacms/cli-2.3.1
Open

chore(deps-dev): bump @tinacms/cli from 2.1.11 to 2.3.1#177
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/tinacms/cli-2.3.1

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 14, 2026

Bumps @tinacms/cli from 2.1.11 to 2.3.1.

Release notes

Sourced from @​tinacms/cli's releases.

@​tinacms/cli@​2.3.1

Patch Changes

  • #6850 629af08 Thanks @​18-th! - Fix the generated client.ts / databaseClient.ts ./types import so it satisfies both TypeScript strict mode and Node native ESM. The generated import is now import { queries } from "./types.js" unconditionally, and the CLI emits a co-resident types.js alongside types.ts for TypeScript projects. Modern TS module resolution (bundler / node16 / nodenext) rewrites the .js import back to types.ts at compile time, so type checking still sees the .ts source and allowImportingTsExtensions is not required, while Node ESM consumers resolve the on-disk .js file at runtime.

  • Updated dependencies [890108d]:

    • @​tinacms/graphql@​2.4.1
    • @​tinacms/search@​1.2.15
    • tinacms@3.8.1
    • @​tinacms/app@​2.4.8

@​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

@​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

... (truncated)

Changelog

Sourced from @​tinacms/cli's changelog.

2.3.1

Patch Changes

  • #6850 629af08 Thanks @​18-th! - Fix the generated client.ts / databaseClient.ts ./types import so it satisfies both TypeScript strict mode and Node native ESM. The generated import is now import { queries } from "./types.js" unconditionally, and the CLI emits a co-resident types.js alongside types.ts for TypeScript projects. Modern TS module resolution (bundler / node16 / nodenext) rewrites the .js import back to types.ts at compile time, so type checking still sees the .ts source and allowImportingTsExtensions is not required, while Node ESM consumers resolve the on-disk .js file at runtime.

  • Updated dependencies [890108d]:

    • @​tinacms/graphql@​2.4.1
    • @​tinacms/search@​1.2.15
    • tinacms@3.8.1
    • @​tinacms/app@​2.4.8

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

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

... (truncated)

Commits

Dependabot compatibility score

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)

@dependabot
chore(deps-dev): bump @tinacms/cli from 2.1.11 to 2.3.1
202b77c 
Bumps [@tinacms/cli](https://github.com/tinacms/tinacms/tree/HEAD/packages/@tinacms/cli) from 2.1.11 to 2.3.1.
- [Release notes](https://github.com/tinacms/tinacms/releases)
- [Changelog](https://github.com/tinacms/tinacms/blob/main/packages/@tinacms/cli/CHANGELOG.md)
- [Commits](https://github.com/tinacms/tinacms/commits/@tinacms/cli@2.3.1/packages/@tinacms/cli)

---
updated-dependencies:
- dependency-name: "@tinacms/cli"
  dependency-version: 2.3.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 14, 2026
@dependabot dependabot Bot mentioned this pull request May 14, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants