fix(deps): update docs dependencies by renovate[bot] · Pull Request #126 · archgate/cli

renovate · 2026-03-21T12:13:01Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/starlight (source)	`^0.34.0` → `^0.38.0`
astro (source)	`^5.7.0` → `^6.0.0`

Release Notes

withastro/starlight (@astrojs/starlight)

`v0.38.2`

Compare Source

Patch Changes

#3759 f24ce99 Thanks @MilesChou! - Fixes an issue where monolingual sites using a region-specific locale (e.g., zh-TW) as the default would incorrectly display base language translations (e.g., zh Simplified Chinese) instead of the region-specific ones (e.g., zh-TW Traditional Chinese).
#3768 a4c6c20 Thanks @delucis! - Improves performance of sidebar generation for sites with very large sidebars

`v0.38.1`

Compare Source

Patch Changes

#3751 fb955ff Thanks @pyxelr! - Fixes a regression causing global tableOfContents config to be ignored

`v0.38.0`

Compare Source

Minor Changes

#3644 0d2e7ed Thanks @HiDeoo! - Adds support for Astro v6, drops support for Astro v5.

Upgrade Astro and dependencies

⚠️ BREAKING CHANGE: Astro v5 is no longer supported. Make sure you update Astro and any other official integrations at the same time as updating Starlight:

npx @&#8203;astrojs/upgrade

Community Starlight plugins and Astro integrations may also need to be manually updated to work with Astro v6. If you encounter any issues, please reach out to the plugin or integration author to see if it is a known issue or if an updated version is being worked on.

Update your collections

⚠️ BREAKING CHANGE: Drops support for content collections backwards compatibility.

In Astro 5.x, projects could delay upgrading to the new Content Layer API introduced for content collections because of some existing automatic backwards compatibility that was not previously behind a flag. This meant that it was possible to upgrade from Astro 4 to Astro 5 without updating your content collections, even if you had not enabled the legacy.collections flag. Projects would continue to build, and no errors or warnings would be displayed.

Astro v6.0 now removes this automatic legacy content collections support, along with the legacy.collections flag.

If you experience content collections errors after updating to v6, check your project for any removed legacy features that may need updating to the Content Layer API. See the Starlight v0.30.0 upgrade guide for detailed instructions on upgrading legacy collections to the new Content Layer API.

If you are unable to make any changes to your collections at this time, including Starlight's default docs and i18n collections, you can enable the legacy.collectionsBackwardsCompat flag to upgrade to v6 without updating your collections. This temporary flag preserves some legacy v4 content collections features, and will allow you to keep your collections in their current state until the legacy flag is no longer supported.

#3704 375edcc Thanks @florian-lefebvre! - Fixes autocomplete for components exported from @astrojs/starlight/components/*

⚠️ Potentially breaking change: This change moves some files used in Starlight’s component internals out of the components/ directory. Direct use of these files was not and is not officially supported. If you previously imported TableOfContents/starlight-toc.ts, TableOfContents/TableOfContentsList.astro, Icons.ts, or SidebarPersistState.ts, please review your code when updating.
#3729 3642625 Thanks @delucis! - Improves Starlight’s default body font stack to better support languages such as Chinese, Japanese, and Korean on Windows.
For most users there should be no visible change.

If you would prefer to keep the previous font stack, you can add the following custom CSS to your site:
```
:root {
  --sl-font-system: ui-sans-serif, system-ui, 'Segoe UI', Roboto,
    'Helvetica Neue', Arial, 'Noto Sans', sans-serif, 'Apple Color Emoji',
    'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji';
}
```
#3598 fff38d5 Thanks @HiDeoo! - Makes hover styles consistent in Starlight’s navigation bar

Previously, the social icon links and language/theme switchers in Starlight’s navigation bar, dimmed on hover.
After this change, they now increase in contrast on hover instead.
This matches hover behavior elsewhere, for example in the sidebar, table of contents, or search button.

⚠️ Potentially breaking change: this is a subtle change to the hover style colors.
If you want to preserve the previous styling, you can add the following custom CSS to your site:
```
starlight-theme-select label,
starlight-lang-select label {
  color: var(--sl-color-gray-1);

  &:hover {
    color: var(--sl-color-white);
  }
}

.social-icons a:hover {
  color: var(--sl-color-text-accent);
  opacity: 0.66;
}
```

`v0.37.7`

Compare Source

Patch Changes

#3726 8a09b60 Thanks @delucis! - Fixes an issue using components containing scripts inside Starlight’s steps component in versions of Astro >= 5.16.9

`v0.37.6`

Compare Source

Patch Changes

#3645 a562096 Thanks @mschoeffmann! - Adds icons for Chrome, Edge, Firefox, and Safari

`v0.37.5`

Compare Source

Patch Changes

#3675 0ba556d Thanks @controversial! - Excludes the accessible labels for heading anchor links from Pagefind results

`v0.37.4`

Compare Source

Patch Changes

#3534 703fab0 Thanks @HiDeoo! - Fixes support for running builds when npx is unavailable.

Previously, Starlight would spawn a process to run the Pagefind search indexing binary using npx. On platforms where npx isn’t available, this could cause issues. Starlight now runs Pagefind using its Node.js API to avoid a separate process. As a side effect, you may notice that logging during builds is now less verbose.
#3656 a0e6368 Thanks @delucis! - Fixes several edge cases in highlighting the current page heading in Starlight’s table of contents
#3663 00cbf00 Thanks @lines-of-codes! - Adds Thai language support
#3658 ac79329 Thanks @delucis! - Avoids adding redundant aria-current="false" attributes to sidebar entries
#3382 db295c2 Thanks @trueberryless! - Fixes an issue where the mobile table of contents is unable to find the first heading when a page has a tall banner.

`v0.37.3`

Compare Source

Patch Changes

#3648 292666c Thanks @maxchang3! - Prevents unwanted font size adjustments on iOS after orientation changes.

`v0.37.2`

Compare Source

Patch Changes

#3647 9f4efc3 Thanks @gerstenbergit! - Adds Greek language support

`v0.37.1`

Compare Source

Patch Changes

#3603 30f6e7f Thanks @delucis! - Fixes support for providing an absolute URL to Starlight’s favicon configuration option

`v0.37.0`

Compare Source

Minor Changes

#3491 28810f0 Thanks @JusticeMatthew! - Changes text overflow styling in Markdown content

⚠️ Potentially breaking change: This release switches the overflow-wrap CSS style for common elements to break-word. In most cases, there should be little visual impact, but this change can impact how layouts with implicit sizing (such as tables) look, improving legibility in how words wrap.

If you want to preserve the previous styling, you can add the following custom CSS to your site:
```
p,
h1,
h2,
h3,
h4,
h5,
h6,
code {
  overflow-wrap: anywhere;
}
```
#3351 239698c Thanks @HiDeoo! - Ensures that Starlight CSS layer order is predictable in custom pages using the <StarlightPage> component.

Previously, due to how import order works in Astro, the <StarlightPage> component had to be the first import in custom pages to set up cascade layers used internally by Starlight to manage the order of its styles.

With this change, this restriction no longer applies and Starlight’s styles will be applied correctly regardless of the import order of the <StarlightPage> component.
#3521 ca7b771 Thanks @shubham-padia! - Fixes an issue where a vertical scrollbar could be displayed on the Starlight <Tabs> component when zooming the page

⚠️ Potentially breaking change: The <Tabs> component no longer uses margin-bottom and border-bottom to highlight the current tab. This is now done with a box-shadow. If you have custom styling for your tabs, you may need to update it.

If you want to preserve the previous styling, you can add the following custom CSS to your site:
```
starlight-tabs .tab {
  margin-bottom: -2px;
}

starlight-tabs .tab > [role='tab'] {
  border-bottom: 2px solid var(--sl-color-gray-5);
  box-shadow: none;
}

starlight-tabs .tab [role='tab'][aria-selected='true'] {
  border-color: var(--sl-color-text-accent);
}
```
#3549 1cf50eb Thanks @jacobdalamb! - Updates the default sans-serif system font stack, dropping support for the -apple-system and BlinkMacSystemFont font names used in older browsers. These are no longer needed in browsers officially supported by Starlight.

If you still need to support older browsers, you can add the following custom CSS to your site:
```
:root {
  --sl-font-system: ui-sans-serif, system-ui, -apple-system,
    BlinkMacSystemFont, 'Segoe UI', Roboto, 'Helvetica Neue', Arial,
    'Noto Sans', sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji',
    'Segoe UI Symbol', 'Noto Color Emoji';
}
```
#3332 f61f99d Thanks @HiDeoo! - Adds a new markdown.processedDirs configuration option to specify additional directories where files should be processed by Starlight’s Markdown pipeline.

By default, Starlight’s processing only applies to Markdown and MDX content loaded using Starlight’s docsLoader(). This new option allows to extend this processing to other directories, which can be useful if you are rendering content from a custom content collection using the <StarlightPage> component and expect Starlight’s Markdown processing to be applied to that content as well.

`v0.36.3`

Compare Source

Patch Changes

#3555 547dc30 Thanks @Its-Just-Nans! - Improves the error message thrown when using a file in the public/ directory with Starlight’s customCss configuration option
#3496 b78fda4 Thanks @delucis! - Fixes invalid <head> output when configuration is missing:
- Omits <meta property="og:description" /> if Starlight’s description option is unset
- Omits <link rel="canonical" /> and <meta property="og:url" /> if Astro’s site option is unset
#3511 8727df1 Thanks @astrobot-houston! - Updates the seti:gitlab icon to match latest version from Seti UI Icons

`v0.36.2`

Compare Source

Patch Changes

#3500 7700456 Thanks @delucis! - This is the first release published with OIDC trusted publishing.
#3484 620fb38 Thanks @gboubeta-uvigo! - Improves Spanish UI translations

`v0.36.1`

Compare Source

Patch Changes

#3479 2fec483 Thanks @gboubeta-uvigo! - Updates Galician UI translations
#3457 c6c0c51 Thanks @HiDeoo! - Deduplicates sitemap link tags in the head.

When enabling sitemap in Starlight, a <link rel="sitemap" href="/sitemap-index.xml"> tag is automatically added to the head of each page. Manually specifying sitemap link tags using the Starlight head configuration option or the head frontmatter field will now override the default sitemap link tag added by Starlight.

This change ensures that users manually adding the @astrojs/sitemap integration to the Astro integrations array for more fine-grained control over sitemap generation and also using the filenameBase integration option can customize the sitemap link tag in the head.
#3448 1fc7501 Thanks @dionysuzx! - Enlarges the Farcaster icon to better match other social icons
#3473 07204dd Thanks @gboubeta! - Fixes a typo in Galician table of contents label

`v0.36.0`

Compare Source

Minor Changes

#3427 c3b2d0f Thanks @delucis! - Fixes styling of labels that wrap across multiple lines in <Tabs> component

⚠️ Potentially breaking change: Tab labels now have a narrower line-height and additional vertical padding. If you have custom CSS targetting the <Tabs> component, you may want to double check the visual appearance of your tabs when updating.

If you want to preserve the previous styling, you can add the following custom CSS to your site:
```
.tab > [role='tab'] {
  line-height: var(--sl-line-height);
  padding-block: 0;
}
```
#3380 3364af3 Thanks @HiDeoo! - Makes head entry parsing stricter in Starlight config and content frontmatter.

⚠️ Potentially breaking change: Previously Starlight would accept a head entry for a meta tag defining some content which generates invalid HTML as <meta> is a void element which cannot have any child nodes. Now, it is an error to define a meta tag including some content.

If you see errors after updating, look for head entries in the Starlight configuration in the astro.config.mjs file or in the frontmatter of your content files that include a content property for a meta tag. To fix the error, move the content property to the attrs object with at least an additional attribute to identify the kind of metadata it represents:
```
head: {
  tag: 'meta',
- content: 'foo',
  attrs: {
    name: 'my-meta',
+   content: 'foo',
  },
},
```
#3340 2018c31 Thanks @HiDeoo! - Adds missing vertical spacing between Markdown content and UI Framework components using client directives.

⚠️ Potentially breaking change: By default, Starlight applies some vertical spacing (--sl-content-gap-y) between Markdown content blocks. This change introduces similar spacing between Markdown content blocks and UI Framework components using client directives which was not present before.

If you were relying on the previous behavior, you can manually override the spacing by manually specifying the top margin on the component using custom CSS, e.g. by relying on a CSS class to target the component.
```
.my-custom-component {
  margin-top: 0;
}
```

Patch Changes

#3423 a0d0670 Thanks @andersk! - Fixes HTML validity in sidebar groups by ensuring <summary> is the first child of <details>

`v0.35.3`

Compare Source

Patch Changes

#3416 fcc0633 Thanks @randomguy-2650! - Updates German UI translations to be more idiomatic.
#1640 d1b3828 Thanks @hippotastic! - Refactors various internal systems, improving code quality and maintainability.
#3421 97e8103 Thanks @andersk! - Removes an invalid value attribute from the language and theme selectors
#3422 9200fac Thanks @andersk! - Refactors collapsible sidebar sections and “on this page” dropdown to use <span> instead of <div>

`v0.35.2`

Compare Source

Patch Changes

#3341 10f6fe2 Thanks @HiDeoo! - Prevents potential build issues with the Astro Cloudflare adapter due to the dependency on Node.js builtins.
#3327 bf58c60 Thanks @delucis! - Fixes a routing bug for docs pages with a slug authored with non-normalized composition. This could occur for filenames containing diacritics in some circumstances, causing 404s.

`v0.35.1`

Compare Source

Patch Changes

#3325 4cf28f2 Thanks @mniinio! - Adds Finnish language support

`v0.35.0`

Compare Source

Minor Changes

#2261 778b743 Thanks @shubham-padia! - Adds support for using any of Starlight’s built-in icons in asides.
#3272 e7fe267 Thanks @delucis! - Adds a new generateId option to Starlight’s docsLoader()

This enables overriding the default sluggifier used to convert content filenames to URLs.
#3276 3917b20 Thanks @delucis! - Excludes banner content from search results

Previously, content set in banner in page frontmatter was indexed by Starlight’s default search provider Pagefind. This could cause unexpected search results, especially for sites setting a common banner content on multiple pages. Starlight’s default Banner component is now excluded from search indexing.

This change does not impact Banner overrides using custom components.
#3266 1161af0 Thanks @HiDeoo! - Adds support for custom HTML attributes on autogenerated sidebar links using the autogenerate.attrs option.
#3274 80ccff7 Thanks @HiDeoo! - Fixes an issue where some Starlight remark and rehype plugins were transforming Markdown and MDX content in non-Starlight pages.

⚠️ BREAKING CHANGE:

Previously, some of Starlight’s remark and rehype plugins, most notably the plugin transforming Starlight's custom Markdown syntax for rendering asides, were applied to all Markdown and MDX content. This included content from individual Markdown pages and content from content collections other than the docs collection used by Starlight.

This change restricts the application of Starlight’s remark and rehype plugins to only Markdown and MDX content loaded using Starlight's docsLoader(). If you were relying on this behavior, please let us know about your use case in the dedicated #starlight channel in the Astro Discord or by opening an issue.

Patch Changes

#3266 1161af0 Thanks @HiDeoo! - Ensures invalid sidebar group configurations using the attrs option are properly reported as a type error.

Previously, invalid sidebar group configurations using the attrs option were not reported as a type error but only surfaced at runtime. This change is only a type-level change and does not affect the runtime behavior of Starlight which does not support the attrs option for sidebar groups.
#3274 80ccff7 Thanks @HiDeoo! - Prevents Starlight remark and rehype plugins from transforming Markdown and MDX content when using the Astro renderMarkdown() content loader API.

withastro/astro (astro)

`v6.0.8`

Compare Source

Patch Changes

#15978 6d182fe Thanks @seroperson! - Fixes a bug where Astro Actions didn't properly support nested object properties, causing problems when users used zod functions such as superRefine or discriminatedUnion.
#16011 e752170 Thanks @matthewp! - Fixes a dev server hang on the first request when using the Cloudflare adapter
#15997 1fddff7 Thanks @ematipico! - Fixes Astro.rewrite() failing when the target path contains duplicate slashes (e.g. //about). The duplicate slashes are now collapsed before URL parsing, preventing them from being interpreted as a protocol-relative URL.

`v6.0.7`

Compare Source

Patch Changes

#15950 acce5e8 Thanks @matthewp! - Fixes a build regression in projects with multiple frontend integrations where server:defer server islands could fail at runtime when all pages are prerendered.
#15988 c93b4a0 Thanks @ossaidqadri! - Fix styles from dynamically imported components not being injected on first dev server load.
#15968 3e7a9d5 Thanks @chasemccoy! - Fixes renderMarkdown in custom content loaders not resolving images in markdown content. Images referenced in markdown processed by renderMarkdown are now correctly optimized, matching the behavior of the built-in glob() loader.
#15990 1e6017f Thanks @ematipico! - Fixes an issue where Astro.currentLocale would always be the default locale instead of the actual one when using a dynamic route like [locale].astro or [locale]/index.astro. It now resolves to the correct locale from the URL.
#15990 1e6017f Thanks @ematipico! - Fixes an issue where visiting an invalid locale URL (e.g. /asdf/) would show the content of a dynamic [locale] page with a 404 status code, instead of showing your custom 404 page. Now, the correct 404 page is rendered when the locale in the URL doesn't match any configured locale.
#15960 1d84020 Thanks @matthewp! - Fixes Cloudflare dev server islands with prerenderEnvironment: 'node' by sharing the serialized manifest encryption key across dev environments and routing server island requests through the SSR runtime.
#15735 9685e2d Thanks @fa-sharp! - Fixes an EventEmitter memory leak when serving static pages from Node.js middleware.

When using the middleware handler, requests that were being passed on to Express / Fastify (e.g. static files / pre-rendered pages / etc.) weren't cleaning up socket listeners before calling next(), causing a memory leak warning. This fix makes sure to run the cleanup before calling next().

`v6.0.6`

Compare Source

Patch Changes

#15965 2dca307 Thanks @matthewp! - Fixes client hydration for components imported through Node.js subpath imports (package.json#imports, e.g. #components/*), for example when using the Cloudflare adapter in development.
#15770 6102ca2 Thanks @jpc-ae! - Updates the create astro welcome message to highlight the graceful dev/preview server quit command rather than the kill process shortcut
#15953 7eddf22 Thanks @Desel72! - fix(hmr): eagerly recompile on style-only change to prevent stale slots render
#15916 5201ed4 Thanks @trueberryless! - Fixes InferLoaderSchema type inference for content collections defined with a loader that includes a schema
#15864 d3c7de9 Thanks @florian-lefebvre! - Removes temporary support for Node >=20.19.1 because Stackblitz now uses Node 22 by default
#15944 a5e1acd Thanks @fkatsuhiro! - Fixes SSR dynamic routes with .html extension (e.g. [slug].html.astro) not working
#15937 d236245 Thanks @ematipico! - Fixes an issue where HMR didn't correctly work on Windows when adding/changing/deleting routes in pages/.
#15931 98dfb61 Thanks @Strernd! - Fix skew protection query params not being applied to island hydration component-url and renderer-url, and ensure query params are appended safely for asset URLs with existing search/hash parts.
Updated dependencies []:
- @astrojs/markdown-remark@7.0.1

`v6.0.5`

Compare Source

Patch Changes

#15891 b889231 Thanks @matthewp! - Fix dev routing for server:defer islands when adapters opt into handling prerendered routes in Astro core. Server island requests are now treated as prerender-handler eligible so prerendered pages using prerenderEnvironment: 'node' can load island content without 400 errors.
#15890 765a887 Thanks @matthewp! - Fixes astro:actions validation to check resolved routes, so projects using default static output with at least one prerender = false page or endpoint no longer fail during startup.
#15884 dcd2c8e Thanks @matthewp! - Avoid a MaxListenersExceededWarning during astro dev startup by increasing the shared Vite watcher listener limit when attaching content server listeners.
#15904 23d5244 Thanks @jlukic! - Emit the before-hydration script chunk for the client Vite environment. The chunk was only emitted for prerender and ssr environments, causing a 404 when browsers tried to load it. This broke hydration for any integration using injectScript('before-hydration', ...), including Lit SSR.
#15933 325901e Thanks @ematipico! - Fixes an issue where <style> tags inside SVG components weren't correctly tracked when enabling CSP.
#15875 c43ef8a Thanks @matthewp! - Ensure custom prerenderers are always torn down during build, even when getStaticPaths() throws.
#15887 1861fed Thanks @ematipico! - Fixes an issue where the build incorrectly leaked server entrypoint into the client environment, causing adapters to emit warnings during the build.
#15888 925252e Thanks @matthewp! - Fix a bug where server:defer could fail at runtime in prerendered pages for some adapters (including Cloudflare), causing errors like serverIslandMap?.get is not a function.
#15901 07c1002 Thanks @delucis! - Fixes JSON schema generation for content collection schemas that have differences between their input and output shapes.
#15882 759f946 Thanks @matthewp! - Fix Astro.url.pathname for the root page when using build.format: "file" so it resolves to /index.html instead of /.html during builds.

`v6.0.4`

Compare Source

Patch Changes

#15870 920f10b Thanks @matthewp! - Prebundle astro/toolbar in dev when custom dev toolbar apps are registered, preventing re-optimization reloads that can hide or break the toolbar.
#15876 f47ac53 Thanks @ematipico! - Fixes redirectToDefaultLocale producing a protocol-relative URL (//locale) instead of an absolute path (/locale) when base is '/'.
#15767 e0042f7 Thanks @matthewp! - Fixes server islands (server:defer) not working when only used in prerendered pages with output: 'server'.
#15873 35841ed Thanks @matthewp! - Fix a dev server bug where newly created pages could miss layout-imported CSS until restart.
#15874 ce0669d Thanks @ematipico! - Fixes a warning when using prefetchAll
#15754 58f1d63 Thanks @rururux! - Fixes a bug where a directory at the project root sharing the same name as a page route would cause the dev server to return a 404 instead of serving the page.
#15869 76b3a5e Thanks @matthewp! - Update the unknown file extension error hint to recommend vite.resolve.noExternal, which is the correct Vite 7 config key.

`v6.0.3`

Compare Source

Patch Changes

#15711 b2bd27b Thanks @OliverSpeir! - Improves Astro core's dev environment handling for prerendered routes by ensuring route/CSS updates and prerender middleware behavior work correctly across both SSR and prerender environments.

This enables integrations that use Astro's prerender dev environment (such as Cloudflare with prerenderEnvironment: 'node') to get consistent route matching and HMR behavior during development.
#15852 1cdaf9f Thanks @ematipico! - Fixes a regression where the the routes emitted by the astro:build:done hook didn't have the distURL array correctly populated.
#15765 ca76ff1 Thanks @matthewp! - Hardens server island POST endpoint validation to use own-property checks for improved consistency

`v6.0.2`

Compare Source

Patch Changes

#15832 95e12a2 Thanks @Princesseuh! - Fixes return; syntax not working in the frontmatter correctly in certain contexts

`v6.0.1`

Compare Source

Patch Changes

#15827 a4c0d0b Thanks @matthewp! - Fixes astro add so the tsconfig preview shows the actual pending changes before confirmation

`v6.0.0`

Compare Source

Major Changes

#14446 ece667a Thanks @florian-lefebvre! - Removes entryPoints on astro:build:ssr hook (Integration API) - (v6 upgrade guidance)
#15535 dfe2e22 Thanks @florian-lefebvre! - Deprecates loadManifest() and loadApp() from astro/app/node (Adapter API) - (v6 upgrade guidance)
#15006 f361730 Thanks @florian-lefebvre! - Removes session test driver - (v6 upgrade guidance)
#15461 9f21b24 Thanks @florian-lefebvre! - BREAKING CHANGE to the v6 beta Adapter API only: renames entryType to entrypointResolution and updates possible values

Astro 6 introduced a way to let adapters have more control over the entrypoint by passing entryType: 'self' to setAdapter(). However during beta development, the name was unclear and confusing.

entryType is now renamed to entrypointResolution and its possible values are updated:
- legacy-dynamic becomes explicit.
- self becomes auto.
If you are building an adapter with v6 beta and specifying entryType, update it:
```
setAdapter({
    // ...
-    entryType: 'legacy-dynamic'
+    entrypointResolution: 'explicit'
})

setAdapter({
    // ...
-    entryType: 'self'
+    entrypointResolution: 'auto'
})
```
#14426 861b9cc Thanks @florian-lefebvre! - Removes the deprecated emitESMImage() function - (v6 upgrade guidance)
#15006 f361730 Thanks [

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

cloudflare-workers-and-pages · 2026-03-21T12:13:02Z

Deploying archgate-cli with Cloudflare Pages

Latest commit:	`5272d85`
Status:	✅ Deploy successful!
Preview URL:	https://6f6839c5.archgate-cli.pages.dev
Branch Preview URL:	https://renovate-docs-dependencies.archgate-cli.pages.dev

View logs

rhuanbarreto mentioned this pull request Mar 21, 2026

fix(config): unify docs dependencies into a single Renovate PR #129

Merged

2 tasks

fix(deps): update docs dependencies

5272d85

renovate Bot force-pushed the renovate/docs-dependencies branch from 1f96b3e to 5272d85 Compare March 21, 2026 12:56

renovate Bot changed the title ~~fix(deps): update dependency @astrojs/starlight to ^0.38.0~~ fix(deps): update docs dependencies Mar 21, 2026

rhuanbarreto merged commit 4c7008a into main Mar 21, 2026
8 of 9 checks passed

rhuanbarreto deleted the renovate/docs-dependencies branch March 21, 2026 18:45

github-actions Bot mentioned this pull request Mar 21, 2026

chore(release): 0.17.2 #128

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update docs dependencies#126

fix(deps): update docs dependencies#126
rhuanbarreto merged 1 commit into
mainfrom
renovate/docs-dependencies

renovate Bot commented Mar 21, 2026 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages Bot commented Mar 21, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

renovate Bot commented Mar 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Minor Changes

Upgrade Astro and dependencies

Update your collections

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Configuration

Uh oh!

cloudflare-workers-and-pages Bot commented Mar 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying archgate-cli with Cloudflare Pages

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate Bot commented Mar 21, 2026 •

edited

Loading

cloudflare-workers-and-pages Bot commented Mar 21, 2026 •

edited

Loading