Skip to content

[DEPENDABOT][SHARED] Weekly npm updates(deps-dev): Bump @tinacms/cli from 2.1.5 to 2.5.1 - #2348

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

[DEPENDABOT][SHARED] Weekly npm updates(deps-dev): Bump @tinacms/cli from 2.1.5 to 2.5.1#2348
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/tinacms/cli-2.5.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 16, 2026

Copy link
Copy Markdown
Contributor

Bumps @tinacms/cli from 2.1.5 to 2.5.1.

Release notes

Sourced from @​tinacms/cli's releases.

@​tinacms/cli@​2.5.1

Patch Changes

@​tinacms/cli@​2.5.0

Minor Changes

  • #7049 29a0e2e Thanks @​0xharkirat! - Add Astro as a first-class framework in tinacms init (now listed first). Selecting Astro:

    • auto-sets the public assets folder to public (no prompt) and wraps the package.json dev/build scripts (tinacms dev -c "astro dev", tinacms build && astro build)
    • installs @tinacms/astro plus an @astrojs/node adapter pinned to the project's Astro major (node 9 for Astro 5, node 10 for Astro 6), and matched react/react-dom (^18.3.1) as dev dependencies — the site stays React-free, but the admin SPA is built with React and a bare Astro project ships none (skipped when the project already declares both)
    • wires astro.config for SSR + visual editing, or — when your config is already customized — prints exactly what to add
    • scaffolds a self-contained, fully editable visual-editing demo at /tinacms-demo: a dark hero whose eyebrow, headline, tagline, and both call-to-action buttons (label + link) are all click-to-edit, with scoped styles and a procedural SVG starfield (no CSS framework or image assets). CMS-editable button links are passed through sanitizeHref.

    The demo is scaffolded automatically with no opt-in (mirroring the Next.js init demo), and is skipped during Forestry migrations.

    init also makes clear it adds Tina to an existing site: it points to npx create-tina-app@latest for new projects and stops early (with that pointer) when run in a folder that has no package.json.

Patch Changes

@​tinacms/cli@​2.4.4

Patch Changes

  • Updated dependencies [7b539b8]:
    • tinacms@3.9.1
    • @​tinacms/app@​2.5.4

@​tinacms/cli@​2.4.3

Patch Changes

@​tinacms/cli@​2.4.2

Patch Changes

... (truncated)

Changelog

Sourced from @​tinacms/cli's changelog.

2.5.1

Patch Changes

2.5.0

Minor Changes

  • #7049 29a0e2e Thanks @​0xharkirat! - Add Astro as a first-class framework in tinacms init (now listed first). Selecting Astro:

    • auto-sets the public assets folder to public (no prompt) and wraps the package.json dev/build scripts (tinacms dev -c "astro dev", tinacms build && astro build)
    • installs @tinacms/astro plus an @astrojs/node adapter pinned to the project's Astro major (node 9 for Astro 5, node 10 for Astro 6), and matched react/react-dom (^18.3.1) as dev dependencies — the site stays React-free, but the admin SPA is built with React and a bare Astro project ships none (skipped when the project already declares both)
    • wires astro.config for SSR + visual editing, or — when your config is already customized — prints exactly what to add
    • scaffolds a self-contained, fully editable visual-editing demo at /tinacms-demo: a dark hero whose eyebrow, headline, tagline, and both call-to-action buttons (label + link) are all click-to-edit, with scoped styles and a procedural SVG starfield (no CSS framework or image assets). CMS-editable button links are passed through sanitizeHref.

    The demo is scaffolded automatically with no opt-in (mirroring the Next.js init demo), and is skipped during Forestry migrations.

    init also makes clear it adds Tina to an existing site: it points to npx create-tina-app@latest for new projects and stops early (with that pointer) when run in a folder that has no package.json.

Patch Changes

2.4.4

Patch Changes

  • Updated dependencies [7b539b8]:
    • tinacms@3.9.1
    • @​tinacms/app@​2.5.4

2.4.3

Patch Changes

... (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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
[DEPENDABOT][SHARED] Weekly npm updates(deps-dev): Bump @tinacms/cli
a48e864 
Bumps [@tinacms/cli](https://github.com/tinacms/tinacms/tree/HEAD/packages/@tinacms/cli) from 2.1.5 to 2.5.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.5.1/packages/@tinacms/cli)

---
updated-dependencies:
- dependency-name: "@tinacms/cli"
  dependency-version: 2.5.1
  dependency-type: direct:development
...

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 Jun 16, 2026
@dependabot dependabot Bot mentioned this pull request Jun 16, 2026
Closed
@vercel

vercel Bot commented Jun 16, 2026 •
edited
Loading

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
filecoin-site Error Error Jun 16, 2026 6:13pm
3 Skipped Deployments
Project Deployment Actions Updated (UTC)
ffdweb-site Skipped Skipped Jun 16, 2026 6:13pm
filecoin-foundation-site Skipped Skipped Jun 16, 2026 6:13pm
filecoin-foundation-uxit Skipped Skipped Jun 16, 2026 6:13pm

Request Review

@vercel
vercel Bot temporarily deployed to Preview – ffdweb-site June 16, 2026 18:10 Inactive
@vercel
vercel Bot temporarily deployed to Preview – filecoin-foundation-site June 16, 2026 18:10 Inactive
@vercel
vercel Bot temporarily deployed to Preview – filecoin-foundation-uxit June 16, 2026 18:10 Inactive
@github-actions

github-actions Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

🔍 PR Change Explainer

This automated summary helps you understand what this PR changes and how it affects the website.

📊 Quick Stats
Files changed 2
Lines added +12431
Lines removed -11859

🌐 Affected Websites

  • filecoin.io (filecoin-site)

📝 What Changed (Plain Language)

This is a configuration change. It modifies build settings, dependencies, or project configuration.

📂 Detailed File Breakdown

Click to expand full file list

filecoin.io (filecoin-site)

Config:

  • apps/filecoin-site/package.json

Root / Config

  • package-lock.json

🚀 Preview & Next Steps

  1. Wait for the Vercel preview — a preview link will appear in this PR as a separate comment from the Vercel bot
  2. Click the preview link to see exactly how your changes look on the live site
  3. Test your changes:
  4. Check the status checks below — all checks should pass (green checkmarks) before merging
  5. When ready, request a review or merge the PR
📖 Glossary (click to expand)
Term What it means
PR (Pull Request) A proposed set of changes waiting to be merged into the main website
Preview deployment A temporary version of the website showing your changes (not public)
Merge Applying your changes to the main website — this triggers a production deploy
Build The process of converting code into a working website
Status checks Automated tests that verify your changes don't break anything
Content file (.md) A Markdown file containing text content (blog posts, events, etc.)
Component (.tsx) A reusable piece of the website's UI (buttons, cards, headers, etc.)
Frontmatter The metadata at the top of content files (title, date, description, etc.)
Shared package Code used by multiple websites — changes here affect all sites

🤖 This comment was generated automatically to help explain PR changes. If something looks wrong, ask a developer for help.

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 size/L

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants