Repository navigation
chore(deps): bump @astrojs/starlight from 0.33.2 to 0.41.7 in /apps/docs in the npm_and_yarn group - #126
chore(deps): bump @astrojs/starlight from 0.33.2 to 0.41.7 in /apps/docs in the npm_and_yarn group#126dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the npm_and_yarn group in /apps/docs with 1 update: [@astrojs/starlight](https://github.com/withastro/starlight/tree/HEAD/packages/starlight). Updates `@astrojs/starlight` from 0.33.2 to 0.41.7 - [Release notes](https://github.com/withastro/starlight/releases) - [Changelog](https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md) - [Commits](https://github.com/withastro/starlight/commits/@astrojs/starlight@0.41.7/packages/starlight) --- updated-dependencies: - dependency-name: "@astrojs/starlight" dependency-version: 0.41.7 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
…en wording Three fixes from Copilot + CodeRabbit review of #137: 1. `@astrojs/starlight` ships on a 0.x cadence, so Dependabot classifies 0.33.x -> 0.41.x as `semver-minor`, not `semver-major`. The previous `semver-major`-only ignore did not catch #126 — the grouped minor PR would keep re-opening. Add `version-update:semver-minor` to the Starlight entry (both scopes) so 0.x breaking releases are held with everything else in the #115 migration. 2. The expanded ignore list was only under the `/apps/docs` (npm) entry, but #131 was `@astrojs/starlight-tailwind` at the workspace root via `dependabot/bun/*`. Mirror the ignore block under the `bun` ecosystem entry at `/` so the coordinated migration blocks both scopes (root + docs) rather than leaking through one. 3. The original comment hardcoded "Astro 7" while #115's title still reads "Astro 6 upgrade tracker" — a mismatch that ages badly if the ecosystem shifts. Reword to keep the concrete ecosystem grounding ("the current 0.41.x line peer-deps the current astro major") without pinning the config to a specific major, and enumerate which PR each ignore entry blocks so future readers see the mapping. No behavior change to the vitest ignore under `bun/` (still tracks #120).
|
·@·d·ependabot c·lose Subsumed by #115 — the Generated by Claude Code |
|
·@·d·ependabot i·gnore t·his major version Subsumed by #115. Generated by Claude Code |
|
·@·d·ependabot i·gnore t·his major version Subsumed by the Astro 5 → 7 coordinated docs migration tracker #115 — Starlight 0.41.x peers The 2026-09-19 audit comment on #141 posted this same command with middle-dot obfuscation and Dependabot didn't parse it — reposting properly this run. Generated by Claude Code |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
…(refs #115) The /apps/docs ignore block previously only silenced `astro` majors, but the Starlight/Tailwind coordinated migration tracked in #115 also subsumes @astrojs/starlight, @astrojs/starlight-tailwind, @astrojs/react, @astrojs/tailwind, tailwindcss, and zod (v3→v4 transitively via astro:content). Today's Dependabot run (2026-08-13) filed six of those as separate PRs (#126, #128, #130, #131, #133, #134) and they will keep recurring weekly until the migration lands. Extend the ignore list to cover each peer, mirroring the existing comment's "remove once the migration lands" pattern. No workspace-root changes; the vitest ignore under `bun/` is untouched.
…en wording Three fixes from Copilot + CodeRabbit review of #137: 1. `@astrojs/starlight` ships on a 0.x cadence, so Dependabot classifies 0.33.x -> 0.41.x as `semver-minor`, not `semver-major`. The previous `semver-major`-only ignore did not catch #126 — the grouped minor PR would keep re-opening. Add `version-update:semver-minor` to the Starlight entry (both scopes) so 0.x breaking releases are held with everything else in the #115 migration. 2. The expanded ignore list was only under the `/apps/docs` (npm) entry, but #131 was `@astrojs/starlight-tailwind` at the workspace root via `dependabot/bun/*`. Mirror the ignore block under the `bun` ecosystem entry at `/` so the coordinated migration blocks both scopes (root + docs) rather than leaking through one. 3. The original comment hardcoded "Astro 7" while #115's title still reads "Astro 6 upgrade tracker" — a mismatch that ages badly if the ecosystem shifts. Reword to keep the concrete ecosystem grounding ("the current 0.41.x line peer-deps the current astro major") without pinning the config to a specific major, and enumerate which PR each ignore entry blocks so future readers see the mapping. No behavior change to the vitest ignore under `bun/` (still tracks #120).
Bumps the npm_and_yarn group in /apps/docs with 1 update: @astrojs/starlight.
Updates
@astrojs/starlightfrom 0.33.2 to 0.41.7Release notes
Sourced from @astrojs/starlight's releases.
... (truncated)
Changelog
Sourced from @astrojs/starlight's changelog.
... (truncated)
Commits
656ffd5[ci] release (#4115)612fd0aUpdate dependencies (#4113)3e486fbRefactor Sätteri RTL code support plugin (#4114)ae0838f[ci] release (#4106)f1dddc0Add Forgejo icon (#4102)5b06909[ci] release (#4097)bb06434Fix union schemaextendregression (#4095)ab2792b[ci] release (#4090)712eeddfix: invalid option error when modifying enums in docsSchema's extend (#3936)0896b91Support links with any protocol in sidebars (#4092)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@astrojs/starlightsince 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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