[dependabot]

Bumps the contentrain group with 3 updates: @contentrain/mcp, @contentrain/query and @contentrain/types.

Updates @contentrain/mcp from 3.9.32 to 3.11.2

Release notes

Sourced from @​contentrain/mcp's releases.

@​contentrain/mcp@​3.11.2

Patch Changes

• Updated dependencies [ad803f7]
  • @​contentrain/types@​1.64.0

@​contentrain/mcp@​3.11.1

Patch Changes

• Updated dependencies [04ce5eb]
  • @​contentrain/types@​1.63.1

@​contentrain/mcp@​3.11.0

Minor Changes

• d089839: Commit hooks are opt-in, and every local write names its base branch.

  • "git": { "verify": true } in .contentrain/config.json, or CONTENTRAIN_VERIFY=1 for one run, runs the repository's commit hooks (pre-commit, prepare-commit-msg, commit-msg) on Contentrain's machine commits: the content commit, the context.json commit, a reconcile merge commit and the seed commit of an empty repo. A hook that rejects the content commit fails the write with the hook's output; nothing is retried without hooks. A hook that rejects only the follow-up context.json commit is reported in the result's warning. CONTENTRAIN_VERIFY=0 skips hooks over the config. The default is unchanged: commit hooks are skipped, so existing projects keep working (#510).
  • Every local write's git block, and contentrain_merge, report base_branch: the resolved branch an auto-merge advances and, unless pushing is off, pushes. When it is not the checked-out branch the result's warning already says the working tree was not touched (#509).
  • ContentrainConfig.git.verify?: boolean and Commit.base_branch?: string in @contentrain/types.

• 7ec8e1f: Validator and init gaps (#512).

  • validate checks document file names against the slug rule. A file such as Bad_Name.md could be read but never saved, because every write rejects that slug. validate now reports it as an error, once per slug, and suggests the slug to rename it to ("bad-name").
  • contentrain init --locales / --domains. Both take a comma-separated list (--locales tr, --locales en,tr, --domains docs), where the first locale is the default. They work with --yes and skip the matching prompt in interactive mode. An invalid locale or domain stops init before anything is written.
  • A YAML inline comment is no longer read as part of the value. status: draft # todo reads as draft, title: "A" # x as A (quotes resolved) and tags: [a, b] # x as the list. C#, "a # b" and a value that starts with # keep their #. The rule is one exported function, stripFrontmatterComment, used by the content engine and by @contentrain/query's generator and Astro loader alike. A list ends at its own closing bracket, so [a, b] # see [c] is ['a', 'b']. The comment is not written back on save, so validate warns about each such line, dash-list items included (frontmatterCommentKeys).

Patch Changes

• 700712c: server.json (the MCP Registry manifest) is on the package's version again. It said 1.8.1. pnpm version-packages now writes it, and pnpm docs:check fails when it drifts. The README tool table lists contentrain_vocabulary_save / contentrain_vocabulary_delete, and the remote-safe subset names them (#516).
• Updated dependencies [18f8792]
• Updated dependencies [3bfe833]
• Updated dependencies [d089839]
• Updated dependencies [7ec8e1f]
  • @​contentrain/types@​1.63.0

@​contentrain/mcp@​3.10.1

Patch Changes

• Updated dependencies [1553879]
  • @​contentrain/types@​1.62.0

@​contentrain/mcp@​3.10.0

Minor Changes

• 7032c5f: Adds local mode, an explicit way to keep every MCP write off the remote. Set "git": { "push": false } in .contentrain/config.json, or CONTENTRAIN_NO_PUSH=1 for one run. The env wins over the config in both directions: =1/true turns pushing off even where config allows it, and =0/false turns it back on over git.push: false. Without either, nothing changes: pushing stays on.

  • No write path pushes: not the branch publish in ensureContentBranch, the review push, the push after an auto-merge, approve (mergeBranch) or reconcile, and not contentrain_submit. Remote branch deletes and prunes are skipped too. Fetching is not a push and still happens.
  • It is never a silent success. RemotePush gains 'disabled', and each write's git block reports remote_push: "disabled" with remote_note: "not pushed (local mode)" and a LOCAL MODE next step. contentrain_submit returns an error naming the switch. Remote delete and prune results report skipped: 'local-mode'. contentrain_merge and contentrain_branch_delete still delete the local branch fully and leave any remote copy untouched.
  • @contentrain/types: ContentrainConfig.git.push and RemotePush 'disabled'.

... (truncated)

Changelog

Sourced from @​contentrain/mcp's changelog.

3.11.2

Patch Changes

• Updated dependencies [ad803f7]
  • @​contentrain/types@​1.64.0

3.11.1

Patch Changes

• Updated dependencies [04ce5eb]
  • @​contentrain/types@​1.63.1

3.11.0

Minor Changes

• d089839: Commit hooks are opt-in, and every local write names its base branch.

  • "git": { "verify": true } in .contentrain/config.json, or CONTENTRAIN_VERIFY=1 for one run, runs the repository's commit hooks (pre-commit, prepare-commit-msg, commit-msg) on Contentrain's machine commits: the content commit, the context.json commit, a reconcile merge commit and the seed commit of an empty repo. A hook that rejects the content commit fails the write with the hook's output; nothing is retried without hooks. A hook that rejects only the follow-up context.json commit is reported in the result's warning. CONTENTRAIN_VERIFY=0 skips hooks over the config. The default is unchanged: commit hooks are skipped, so existing projects keep working (#510).
  • Every local write's git block, and contentrain_merge, report base_branch: the resolved branch an auto-merge advances and, unless pushing is off, pushes. When it is not the checked-out branch the result's warning already says the working tree was not touched (#509).
  • ContentrainConfig.git.verify?: boolean and Commit.base_branch?: string in @contentrain/types.

• 7ec8e1f: Validator and init gaps (#512).

  • validate checks document file names against the slug rule. A file such as Bad_Name.md could be read but never saved, because every write rejects that slug. validate now reports it as an error, once per slug, and suggests the slug to rename it to ("bad-name").
  • contentrain init --locales / --domains. Both take a comma-separated list (--locales tr, --locales en,tr, --domains docs), where the first locale is the default. They work with --yes and skip the matching prompt in interactive mode. An invalid locale or domain stops init before anything is written.
  • A YAML inline comment is no longer read as part of the value. status: draft # todo reads as draft, title: "A" # x as A (quotes resolved) and tags: [a, b] # x as the list. C#, "a # b" and a value that starts with # keep their #. The rule is one exported function, stripFrontmatterComment, used by the content engine and by @contentrain/query's generator and Astro loader alike. A list ends at its own closing bracket, so [a, b] # see [c] is ['a', 'b']. The comment is not written back on save, so validate warns about each such line, dash-list items included (frontmatterCommentKeys).

Patch Changes

• 700712c: server.json (the MCP Registry manifest) is on the package's version again. It said 1.8.1. pnpm version-packages now writes it, and pnpm docs:check fails when it drifts. The README tool table lists contentrain_vocabulary_save / contentrain_vocabulary_delete, and the remote-safe subset names them (#516).
• Updated dependencies [18f8792]
• Updated dependencies [3bfe833]
• Updated dependencies [d089839]
• Updated dependencies [7ec8e1f]
  • @​contentrain/types@​1.63.0

3.10.1

Patch Changes

• Updated dependencies [1553879]
  • @​contentrain/types@​1.62.0

3.10.0

Minor Changes

... (truncated)

Commits

• 4e3b984 chore(release): version packages (#558)
• 7ffefda chore(release): version packages (#540)
• 069c222 chore(release): version packages (#533)
• 700712c docs: tool/skill/package counts, server.json version, dead skills link, astro...
• d089839 feat(mcp,types): commit hooks are opt-in with git.verify, every local write n...
• 7ec8e1f fix(types,mcp,cli,sdk): validate document slugs, init --locales/--domains, YA...
• 3bfe833 fix(types): a document saved without a field change is byte-identical, blank ...
• f715f65 chore(release): version packages (#525)
• 9df5c2e chore(release): version packages (#518)
• 19057f7 docs(mcp): run the standalone server through the scoped package (#523)
• Additional commits viewable in compare view

Updates @contentrain/query from 7.6.38 to 7.6.45

Release notes

Sourced from @​contentrain/query's releases.

@​contentrain/query@​7.6.45

Patch Changes

• Updated dependencies [ad803f7]
  • @​contentrain/types@​1.64.0

@​contentrain/query@​7.6.44

Patch Changes

• Updated dependencies [04ce5eb]
  • @​contentrain/types@​1.63.1

@​contentrain/query@​7.6.43

Patch Changes

• 7ec8e1f: Validator and init gaps (#512).

  • validate checks document file names against the slug rule. A file such as Bad_Name.md could be read but never saved, because every write rejects that slug. validate now reports it as an error, once per slug, and suggests the slug to rename it to ("bad-name").
  • contentrain init --locales / --domains. Both take a comma-separated list (--locales tr, --locales en,tr, --domains docs), where the first locale is the default. They work with --yes and skip the matching prompt in interactive mode. An invalid locale or domain stops init before anything is written.
  • A YAML inline comment is no longer read as part of the value. status: draft # todo reads as draft, title: "A" # x as A (quotes resolved) and tags: [a, b] # x as the list. C#, "a # b" and a value that starts with # keep their #. The rule is one exported function, stripFrontmatterComment, used by the content engine and by @contentrain/query's generator and Astro loader alike. A list ends at its own closing bracket, so [a, b] # see [c] is ['a', 'b']. The comment is not written back on save, so validate warns about each such line, dash-list items included (frontmatterCommentKeys).

• Updated dependencies [18f8792]

• Updated dependencies [3bfe833]

• Updated dependencies [d089839]

• Updated dependencies [7ec8e1f]

  • @​contentrain/types@​1.63.0

@​contentrain/query@​7.6.42

Patch Changes

• Updated dependencies [1553879]
  • @​contentrain/types@​1.62.0

@​contentrain/query@​7.6.41

Patch Changes

• Updated dependencies [3fa05b7]
• Updated dependencies [e360392]
• Updated dependencies [7032c5f]
  • @​contentrain/types@​1.61.0

@​contentrain/query@​7.6.40

Patch Changes

• 193d543: Fixes a correctness bug in the Astro loader: on large sites, content could go missing without any error when the system ran short of open file handles (file-descriptor pressure). Astro starts every collection's loader at once, and each loader used to read all of the project's models and content files in parallel. A site with about 300 models asked for some 190,000 files at the same moment, beyond what macOS allows a process to have open. Any read that failed was treated as a missing file, so a model or collection silently built short, or the build died in Astro's data-store write (EMFILE).

  • The loaders of one Astro sync now read the project once and share it. The dev server still reads it fresh on each load.
  • At most 64 files are read at a time, through one queue shared by every read in the process.
  • Only a missing path (ENOENT/ENOTDIR) counts as absent. Any other read failure, EMFILE included, now fails the build. A file that is not valid JSON still reads as null, as before.
  • When a content file that exists loads no entries, the loader logs a warning with the model name and the number of files found and read.

... (truncated)

Changelog

Sourced from @​contentrain/query's changelog.

7.6.45

Patch Changes

• Updated dependencies [ad803f7]
  • @​contentrain/types@​1.64.0

7.6.44

Patch Changes

• Updated dependencies [04ce5eb]
  • @​contentrain/types@​1.63.1

7.6.43

Patch Changes

• 7ec8e1f: Validator and init gaps (#512).

  • validate checks document file names against the slug rule. A file such as Bad_Name.md could be read but never saved, because every write rejects that slug. validate now reports it as an error, once per slug, and suggests the slug to rename it to ("bad-name").
  • contentrain init --locales / --domains. Both take a comma-separated list (--locales tr, --locales en,tr, --domains docs), where the first locale is the default. They work with --yes and skip the matching prompt in interactive mode. An invalid locale or domain stops init before anything is written.
  • A YAML inline comment is no longer read as part of the value. status: draft # todo reads as draft, title: "A" # x as A (quotes resolved) and tags: [a, b] # x as the list. C#, "a # b" and a value that starts with # keep their #. The rule is one exported function, stripFrontmatterComment, used by the content engine and by @contentrain/query's generator and Astro loader alike. A list ends at its own closing bracket, so [a, b] # see [c] is ['a', 'b']. The comment is not written back on save, so validate warns about each such line, dash-list items included (frontmatterCommentKeys).

• Updated dependencies [18f8792]

• Updated dependencies [3bfe833]

• Updated dependencies [d089839]

• Updated dependencies [7ec8e1f]

  • @​contentrain/types@​1.63.0

7.6.42

Patch Changes

• Updated dependencies [1553879]
  • @​contentrain/types@​1.62.0

7.6.41

Patch Changes

• Updated dependencies [3fa05b7]
• Updated dependencies [e360392]
• Updated dependencies [7032c5f]
  • @​contentrain/types@​1.61.0

7.6.40

Patch Changes

... (truncated)

Commits

• 4e3b984 chore(release): version packages (#558)
• 7ffefda chore(release): version packages (#540)
• 069c222 chore(release): version packages (#533)
• 7ec8e1f fix(types,mcp,cli,sdk): validate document slugs, init --locales/--domains, YA...
• f715f65 chore(release): version packages (#525)
• 9df5c2e chore(release): version packages (#518)
• 0d90276 chore(release): version packages (#504)
• 193d543 fix(sdk): the Astro loader reads the project once and caps open files — no si...
• 51f62fe chore(release): version packages (#493)
• See full diff in compare view

Updates @contentrain/types from 1.59.0 to 1.64.0

Release notes

Sourced from @​contentrain/types's releases.

@​contentrain/types@​1.64.0

Minor Changes

• ad803f7: The header site name takes the source theme's colour where it is not the header's text colour. Header gains brandColor: link paints the name in the site's link colour (a title that is a link styled like every other, as Hello Elementor's is), or a colour (#hex, rgb(), hsl()) is used as it is; anything else is ignored. site.chrome.brandColor carries it in the plan, validated (link or a colour; never a ; or url()), and the starter's BaseLayout passes it through the same guard. Without it the header is exactly as before.

@​contentrain/types@​1.63.1

Patch Changes

• 04ce5eb: A WordPress installed in a directory (https://example.com/blog) moves to a site served from that directory.

  • @contentrain/types: validateProjectPlan accepts a sub-directory install as source.origin (https://example.com/blog): its paths keep the prefix. An origin with a trailing slash, a query or a fragment is still refused.
  • @contentrain/astro-kit: KitImage serves a root image address (/media/a.svg) that it does not optimize from the site's directory under Astro's base, where public/ is served. Without base nothing changes.

  The astro starter serves every address under astro.config base (base: '/blog/', which a migration writes for such an install): the route table, links in menus and bodies, redirect pages and _redirects (old and new addresses), WordPress's query addresses, the sitemap, the feed (its channel link too), llms.txt, canonical and Open Graph URLs, JSON-LD, the favicon, search (Pagefind), body images and the file and link fields of a custom type's page. Plan and store paths stay the install's (/about/). scripts/check-dist.mjs fails a site served from a directory when a page or a host rule points outside it. Its wp-query-map.json check accepts an absolute target (an attachment whose file stays at the old site's address). Without base the built site is unchanged, except that an absolute link to the site's own feed (https://example.com/rss.xml) is written as /rss.xml, like every other link to the site.

@​contentrain/types@​1.63.0

Minor Changes

• 18f8792: A :category permalink token, so WordPress /%category%/%postname%/ sites keep their post URLs.

  • @contentrain/types: PlanPermalink documents :category for site.permalinks.post; the plan validator rejects it in any other permalink.
  • @contentrain/wp-import: posts get a primary_category relation to categories from Yoast's _yoast_wpseo_primary_category or Rank Math's rank_math_primary_category (a term id), which is the category WordPress puts in %category%. A primary that names no imported category is dropped and counted in dropped_relations.

  The astro starter fills :category with the post's primary category, else its category with the lowest term ID, with its parents (news/local); a post with none takes siteConfig.defaultCategory (default uncategorized), as WordPress does.

• d089839: Commit hooks are opt-in, and every local write names its base branch.

  • "git": { "verify": true } in .contentrain/config.json, or CONTENTRAIN_VERIFY=1 for one run, runs the repository's commit hooks (pre-commit, prepare-commit-msg, commit-msg) on Contentrain's machine commits: the content commit, the context.json commit, a reconcile merge commit and the seed commit of an empty repo. A hook that rejects the content commit fails the write with the hook's output; nothing is retried without hooks. A hook that rejects only the follow-up context.json commit is reported in the result's warning. CONTENTRAIN_VERIFY=0 skips hooks over the config. The default is unchanged: commit hooks are skipped, so existing projects keep working (#510).
  • Every local write's git block, and contentrain_merge, report base_branch: the resolved branch an auto-merge advances and, unless pushing is off, pushes. When it is not the checked-out branch the result's warning already says the working tree was not touched (#509).
  • ContentrainConfig.git.verify?: boolean and Commit.base_branch?: string in @contentrain/types.

• 7ec8e1f: Validator and init gaps (#512).

  • validate checks document file names against the slug rule. A file such as Bad_Name.md could be read but never saved, because every write rejects that slug. validate now reports it as an error, once per slug, and suggests the slug to rename it to ("bad-name").
  • contentrain init --locales / --domains. Both take a comma-separated list (--locales tr, --locales en,tr, --domains docs), where the first locale is the default. They work with --yes and skip the matching prompt in interactive mode. An invalid locale or domain stops init before anything is written.
  • A YAML inline comment is no longer read as part of the value. status: draft # todo reads as draft, title: "A" # x as A (quotes resolved) and tags: [a, b] # x as the list. C#, "a # b" and a value that starts with # keep their #. The rule is one exported function, stripFrontmatterComment, used by the content engine and by @contentrain/query's generator and Astro loader alike. A list ends at its own closing bracket, so [a, b] # see [c] is ['a', 'b']. The comment is not written back on save, so validate warns about each such line, dash-list items included (frontmatterCommentKeys).

Patch Changes

• 3bfe833: A document saved without a field change is byte-identical again (#521). parseMarkdownFrontmatter now records the layout around the body — the blank lines after the closing ---, the trailing newlines, the line ending and the final newline — whenever it differs from the default shape, and serializeMarkdownFrontmatter writes it back: no blank line is added after --- or collapsed, \n\n at the end stays \n\n, a plain document without a final newline keeps none, and a plain CRLF document stays CRLF. A document in the default shape (LF, one blank line after ---, one final newline) still has no preserved, and new documents are written as before.

@​contentrain/types@​1.62.0

Minor Changes

• 1553879: PlanSite.chrome.menu?: 'mega': the source's header menu is a mega menu (a wide panel of columns) rather than the starter's flyout. Absent keeps the flyout. The plan validator accepts mega and rejects any other value.

@​contentrain/types@​1.61.0

Minor Changes

• e360392: parseMarkdownFrontmatter now returns preserved: the frontmatter lines it cannot read (a key with a space or a non-ASCII letter, a nested map, a block scalar, a comment), verbatim and anchored to the field they followed. serializeMarkdownFrontmatter(data, body, preserved?) writes them back in place, CRLF included, and preservedKeyConflicts names the blocks a new value replaces. A key above a nested map is no longer read as an empty array.

... (truncated)

Changelog

Sourced from @​contentrain/types's changelog.

1.64.0

Minor Changes

• ad803f7: The header site name takes the source theme's colour where it is not the header's text colour. Header gains brandColor: link paints the name in the site's link colour (a title that is a link styled like every other, as Hello Elementor's is), or a colour (#hex, rgb(), hsl()) is used as it is; anything else is ignored. site.chrome.brandColor carries it in the plan, validated (link or a colour; never a ; or url()), and the starter's BaseLayout passes it through the same guard. Without it the header is exactly as before.

1.63.1

Patch Changes

• 04ce5eb: A WordPress installed in a directory (https://example.com/blog) moves to a site served from that directory.

  • @contentrain/types: validateProjectPlan accepts a sub-directory install as source.origin (https://example.com/blog): its paths keep the prefix. An origin with a trailing slash, a query or a fragment is still refused.
  • @contentrain/astro-kit: KitImage serves a root image address (/media/a.svg) that it does not optimize from the site's directory under Astro's base, where public/ is served. Without base nothing changes.

  The astro starter serves every address under astro.config base (base: '/blog/', which a migration writes for such an install): the route table, links in menus and bodies, redirect pages and _redirects (old and new addresses), WordPress's query addresses, the sitemap, the feed (its channel link too), llms.txt, canonical and Open Graph URLs, JSON-LD, the favicon, search (Pagefind), body images and the file and link fields of a custom type's page. Plan and store paths stay the install's (/about/). scripts/check-dist.mjs fails a site served from a directory when a page or a host rule points outside it. Its wp-query-map.json check accepts an absolute target (an attachment whose file stays at the old site's address). Without base the built site is unchanged, except that an absolute link to the site's own feed (https://example.com/rss.xml) is written as /rss.xml, like every other link to the site.

1.63.0

Minor Changes

• 18f8792: A :category permalink token, so WordPress /%category%/%postname%/ sites keep their post URLs.

  • @contentrain/types: PlanPermalink documents :category for site.permalinks.post; the plan validator rejects it in any other permalink.
  • @contentrain/wp-import: posts get a primary_category relation to categories from Yoast's _yoast_wpseo_primary_category or Rank Math's rank_math_primary_category (a term id), which is the category WordPress puts in %category%. A primary that names no imported category is dropped and counted in dropped_relations.

  The astro starter fills :category with the post's primary category, else its category with the lowest term ID, with its parents (news/local); a post with none takes siteConfig.defaultCategory (default uncategorized), as WordPress does.

• d089839: Commit hooks are opt-in, and every local write names its base branch.

  • "git": { "verify": true } in .contentrain/config.json, or CONTENTRAIN_VERIFY=1 for one run, runs the repository's commit hooks (pre-commit, prepare-commit-msg, commit-msg) on Contentrain's machine commits: the content commit, the context.json commit, a reconcile merge commit and the seed commit of an empty repo. A hook that rejects the content commit fails the write with the hook's output; nothing is retried without hooks. A hook that rejects only the follow-up context.json commit is reported in the result's warning. CONTENTRAIN_VERIFY=0 skips hooks over the config. The default is unchanged: commit hooks are skipped, so existing projects keep working (#510).
  • Every local write's git block, and contentrain_merge, report base_branch: the resolved branch an auto-merge advances and, unless pushing is off, pushes. When it is not the checked-out branch the result's warning already says the working tree was not touched (#509).
  • ContentrainConfig.git.verify?: boolean and Commit.base_branch?: string in @contentrain/types.

• 7ec8e1f: Validator and init gaps (#512).

  • validate checks document file names against the slug rule. A file such as Bad_Name.md could be read but never saved, because every write rejects that slug. validate now reports it as an error, once per slug, and suggests the slug to rename it to ("bad-name").
  • contentrain init --locales / --domains. Both take a comma-separated list (--locales tr, --locales en,tr, --domains docs), where the first locale is the default. They work with --yes and skip the matching prompt in interactive mode. An invalid locale or domain stops init before anything is written.
  • A YAML inline comment is no longer read as part of the value. status: draft # todo reads as draft, title: "A" # x as A (quotes resolved) and tags: [a, b] # x as the list. C#, "a # b" and a value that starts with # keep their #. The rule is one exported function, stripFrontmatterComment, used by the content engine and by @contentrain/query's generator and Astro loader alike. A list ends at its own closing bracket, so [a, b] # see [c] is ['a', 'b']. The comment is not written back on save, so validate warns about each such line, dash-list items included (frontmatterCommentKeys).

Patch Changes

• 3bfe833: A document saved without a field change is byte-identical again (#521). parseMarkdownFrontmatter now records the layout around the body — the blank lines after the closing ---, the trailing newlines, the line ending and the final newline — whenever it differs from the default shape, and serializeMarkdownFrontmatter writes it back: no blank line is added after --- or collapsed, \n\n at the end stays \n\n, a plain document without a final newline keeps none, and a plain CRLF document stays CRLF. A document in the default shape (LF, one blank line after ---, one final newline) still has no preserved, and new documents are written as before.

1.62.0

Minor Changes

• 1553879: PlanSite.chrome.menu?: 'mega': the source's header menu is a mega menu (a wide panel of columns) rather than the starter's flyout. Absent keeps the flyout. The plan validator accepts mega and rejects any other value.

... (truncated)

Commits

• 4e3b984 chore(release): version packages (#558)
• ad803f7 feat(astro-kit,types,astro-starter): the header site name takes the source th...
• 7ffefda chore(release): version packages (#540)
• 04ce5eb fix(types,astro-starter,astro-kit): a WordPress installed in a sub-directory ...
• 069c222 chore(release): version packages (#533)
• d089839 feat(mcp,types): commit hooks are opt-in with git.verify, every local write n...
• 7ec8e1f fix(types,mcp,cli,sdk): validate document slugs, init --locales/--domains, YA...
• 3bfe833 fix(types): a document saved without a field change is byte-identical, blank ...
• 18f8792 feat(types,astro-starter): a :category permalink token, so /%category%/%postn...
• f715f65 chore(release): version packages (#525)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are no longer updatable, so this is no longer needed.