Bump tinacms from 2.8.3 to 3.11.0

[dependabot]

Bumps tinacms from 2.8.3 to 3.11.0.

Release notes

Sourced from tinacms's releases.

tinacms@3.11.0

Minor Changes

• #7235 908fe7d Thanks @​joshbermanssw! - Editorial-workflow saves (Save draft / Save to a new branch, and the media create-branch flow) now run a single branch-list lookup instead of two sequential ones, roughly halving the delay before the progress modal appears.

Patch Changes

• #7194 711ba30 Thanks @​kulesy! - Button now renders the shared loading-dots indicator automatically when busy, so every busy button gets a consistent spinner instead of each call site wiring its own (and some, like the account password form, were missing it entirely). The dots inherit the button text color so they stay visible across variants.

• #7161 566af78 Thanks @​ahfoysal! - Keep folder collection views open when they only contain one document.

• #7251 b8df6ee Thanks @​kulesy! - Fix the rich-text link popover not appearing when adding or editing a link.

  Since the popover was moved into a portal on document.body, plate-floating's inline z-index: 50 overrode its z-[999999] class, so it rendered behind the form field wrappers (which use z-index up to 1000) and was invisible. It now sits above them, so clicking the link button shows the URL input as expected.

• #7204 59efccc Thanks @​joshbermanssw! - Show a clear error when repo-based media is used with a self-hosted site, instead of a misleading "Bad Route" message.

• #7213 056ffc2 Thanks @​wicksipedia! - Publish internal package references as ranges instead of exact versions.

  Internal dependencies were declared as workspace:*, which pnpm expands to an exact version when publishing ("tinacms": "3.10.0"), not a range. An exact pin cannot deduplicate against the version a consumer has already installed, so npm nests a second — and third — complete copy of tinacms and its dependency tree. In a stock Astro + TinaCMS blog this produced three copies of tinacms, three of mermaid (186 MB), five of date-fns (151 MB), and four of typescript (88 MB): about 320 MB of duplication.

  The same expansion applied to peerDependencies, so packages such as next-tinacms-cloudinary and tinacms-authjs published "tinacms": "3.10.0" as a peer — requiring consumers to have that exact version or hit an ERESOLVE conflict, and forcing a republish of every dependent on each tinacms release.

  Switching these to workspace:^ publishes them as caret ranges (^3.10.0), which deduplicate normally and let onlyUpdatePeerDependentsWhenOutOfRange do its job.

• Updated dependencies [cdbf469, 056ffc2]:

  • @​tinacms/bridge@​0.3.1
  • @​tinacms/mdx@​2.1.11
  • @​tinacms/search@​1.2.23

tinacms@3.10.1

Patch Changes

• Updated dependencies [4b4e139]:
  • @​tinacms/mdx@​2.1.10
  • @​tinacms/search@​1.2.22

tinacms@3.10.0

Minor Changes

• #7136 c809733 Thanks @​joshbermanssw! - editorial workflow - add toggle to switch PRs created between draft and ready to review mode

Patch Changes

• #7141 3a1b39a Thanks @​joshbermanssw! - Update @radix-ui/* dependencies to their latest patch/minor releases and remove the unused @radix-ui/react-checkbox dependency

• #7140 de4a807 Thanks @​joshbermanssw! - Add a PostHog editorial-workflow-save event that records which save option was used in the "Save changes to new branch" modal (draft, ready for review, or publish), whether the save succeeded, and the failure reason when it didn't.

• #7138 8497110 Thanks @​joshbermanssw! - Editorial workflow: replace the draft / ready-for-review toggle in the "Save changes to new branch" modal with a save-options dropdown (Save draft, Save (ready for review), Save and publish). The split button's main action reflects the editor's last choice (default Save draft, remembered via localStorage), and Save and publish is disabled with a tooltip on protected branches.

... (truncated)

Changelog

Sourced from tinacms's changelog.

3.11.0

Minor Changes

• #7235 908fe7d Thanks @​joshbermanssw! - Editorial-workflow saves (Save draft / Save to a new branch, and the media create-branch flow) now run a single branch-list lookup instead of two sequential ones, roughly halving the delay before the progress modal appears.

Patch Changes

• #7194 711ba30 Thanks @​kulesy! - Button now renders the shared loading-dots indicator automatically when busy, so every busy button gets a consistent spinner instead of each call site wiring its own (and some, like the account password form, were missing it entirely). The dots inherit the button text color so they stay visible across variants.

• #7161 566af78 Thanks @​ahfoysal! - Keep folder collection views open when they only contain one document.

• #7251 b8df6ee Thanks @​kulesy! - Fix the rich-text link popover not appearing when adding or editing a link.

  Since the popover was moved into a portal on document.body, plate-floating's inline z-index: 50 overrode its z-[999999] class, so it rendered behind the form field wrappers (which use z-index up to 1000) and was invisible. It now sits above them, so clicking the link button shows the URL input as expected.

• #7204 59efccc Thanks @​joshbermanssw! - Show a clear error when repo-based media is used with a self-hosted site, instead of a misleading "Bad Route" message.

• #7213 056ffc2 Thanks @​wicksipedia! - Publish internal package references as ranges instead of exact versions.

  Internal dependencies were declared as workspace:*, which pnpm expands to an exact version when publishing ("tinacms": "3.10.0"), not a range. An exact pin cannot deduplicate against the version a consumer has already installed, so npm nests a second — and third — complete copy of tinacms and its dependency tree. In a stock Astro + TinaCMS blog this produced three copies of tinacms, three of mermaid (186 MB), five of date-fns (151 MB), and four of typescript (88 MB): about 320 MB of duplication.

  The same expansion applied to peerDependencies, so packages such as next-tinacms-cloudinary and tinacms-authjs published "tinacms": "3.10.0" as a peer — requiring consumers to have that exact version or hit an ERESOLVE conflict, and forcing a republish of every dependent on each tinacms release.

  Switching these to workspace:^ publishes them as caret ranges (^3.10.0), which deduplicate normally and let onlyUpdatePeerDependentsWhenOutOfRange do its job.

• Updated dependencies [cdbf469, 056ffc2]:

  • @​tinacms/bridge@​0.3.1
  • @​tinacms/mdx@​2.1.11
  • @​tinacms/search@​1.2.23

3.10.1

Patch Changes

• Updated dependencies [4b4e139]:
  • @​tinacms/mdx@​2.1.10
  • @​tinacms/search@​1.2.22

3.10.0

Minor Changes

• #7136 c809733 Thanks @​joshbermanssw! - editorial workflow - add toggle to switch PRs created between draft and ready to review mode

Patch Changes

• #7141 3a1b39a Thanks @​joshbermanssw! - Update @radix-ui/* dependencies to their latest patch/minor releases and remove the unused @radix-ui/react-checkbox dependency

• #7140 de4a807 Thanks @​joshbermanssw! - Add a PostHog editorial-workflow-save event that records which save option was used in the "Save changes to new branch" modal (draft, ready for review, or publish), whether the save succeeded, and the failure reason when it didn't.

... (truncated)

Commits

• b636a22 Version Packages (#7205)
• 566af78 Fix folder collection auto-open (#7161)
• 908fe7d ⚡ Collapse editorial-workflow branch guard to a single branch-list fetch (#7235)
• b8df6ee fix(tinacms): show the rich-text link popover above form fields (#7251)
• 056ffc2 🐛 Publish internal package refs as ranges, not exact pins (~320 MB of duplica...
• 59efccc 🐛 Show a clear error for repo-based media on self-hosted sites (#7204)
• 711ba30 refactor(tinacms): render loading dots automatically on busy buttons (#7194)
• adeafbc Version Packages (#7174)
• a1ebeda Version Packages (#7130)
• ff10e65 fix(tinacms): reject invalid folder names inline via shared relativePath allo...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for tinacms since your current version.

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)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
allocin.it	Error		Jul 16, 2026 6:40pm