Skip to content

Update npm packages (minor and patch) - #58

Merged
ecv merged 2 commits into
mainfrom
renovate/npm-minor-patch
Nov 9, 2026
Merged

Update npm packages (minor and patch)#58
ecv merged 2 commits into
mainfrom
renovate/npm-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Nov 3, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/node (source) 11.1.3 → 11.1.11 age confidence
@astrojs/starlight (source) ^0.41.0 → ^0.42.0 age confidence
@astrojs/ts-plugin (source) 1.10.6 → 1.10.12 age confidence
@tailwindcss/typography 0.5.19 → 0.5.20 age confidence
@tailwindcss/vite (source) 4.2.1 → 4.3.5 age confidence
@typescript-eslint/parser (source) 8.66.0 → 8.72.1 age confidence
astro (source) 7.3.3 → 7.4.7 age confidence
astro-seo 1.1.0 → 1.2.0 age confidence
eslint (source) 10.0.2 → 10.14.0 age confidence
eslint-plugin-astro (source) 3.1.0 → 3.2.1 age confidence
markdownlint-cli2 ^0.23.0 → ^0.24.0 age confidence
prettier (source) 3.8.1 → 3.9.10 age confidence
tailwindcss (source) 4.2.1 → 4.3.5 age confidence
typescript-eslint (source) 8.66.0 → 8.72.1 age confidence

Release Notes

withastro/astro (@​astrojs/node)

v11.1.11

Compare Source

Patch Changes

v11.1.10

Compare Source

Patch Changes

v11.1.9

Compare Source

Patch Changes
  • #​18382 c75e897 Thanks @​Llois41! - Fixes the standalone server not logging Server listening on … when HOST is an IP address, which happens on Node.js 26.12 and later

v11.1.8

Compare Source

Patch Changes

v11.1.7

Compare Source

Patch Changes

v11.1.6

Compare Source

Patch Changes

v11.1.5

Compare Source

Patch Changes

v11.1.4

Compare Source

Patch Changes
withastro/starlight (@​astrojs/starlight)

v0.42.10

Compare Source

Patch Changes

  • #​4354 56b8587 Thanks @​jasikpark! - Improves the color contrast of the search input placeholder text

  • #​4337 c5d0a7f Thanks @​moonmeister! - Fixes search not loading when the search script runs after the page has finished loading, for example when a Content Security Policy requires scripts to be added dynamically

  • #​4352 3edab29 Thanks @​delucis! - Fixes the Astro trailingSlash and build.format options not being applied correctly to sidebar links that include a query string or hash

v0.42.9

Compare Source

Patch Changes

  • #​4218 effea21 Thanks @​delucis! - Reduces install size by ~400 KB by switching the YAML parser used internally for projects using Astro 7.3.6 or later

  • #​4316 8679b1c Thanks @​clean99! - Fixes localized routes and language switcher links for pages in directories named like Object.prototype properties, such as constructor.

  • #​4341 e1ac1b4 Thanks @​delucis! - Prevents tables overflowing and clipping when printing a page

v0.42.8

Compare Source

Patch Changes

  • #​4309 3490c80 Thanks @​athulsreekumar! - Fixes autogenerated sidebar groups omitting directories whose names match Object.prototype properties, such as constructor or toString

  • #​4290 bf93823 Thanks @​RaphaelFakhri! - Fixes missing last-updated dates in production builds for pages whose file path contains special characters

  • #​4295 af9557e Thanks @​delucis! - Fixes a formatting issue in some error messages impacting projects with Zod ≥4.5 installed

  • #​4299 a103f38 Thanks @​clean99! - Fixes empty sidebars when autogenerating entries from the docs root directory using directory: ''

v0.42.7

Compare Source

Patch Changes

  • #​4264 94e0985 Thanks @​chrispezza! - Fixes a layout shift where the table of contents could be painted at the start of the content area and then jump to the end when a page's HTML arrived in several chunks

  • #​4285 6f22edd Thanks @​tunetheweb! - Improves hero image loading by adding fetchpriority="high" hint for browsers

v0.42.6

Compare Source

Patch Changes

  • #​4252 40a2584 Thanks @​olafur-andri! - Adds Icelandic language support

  • #​4229 e4a3d82 Thanks @​HiDeoo! - Fixes a potential issue with icons being cut off in Firefox when pinch-zooming.

  • #​4226 fb562dd Thanks @​HiDeoo! - Fixes an issue where pages not importing components from @astrojs/starlight/components included styles of Starlight components used on other pages.

  • #​4250 531af7d Thanks @​HiDeoo! - Fixes Failed to resolve dependency warnings logged when running the development server in projects using the Cloudflare adapter.

  • #​4229 e4a3d82 Thanks @​HiDeoo! - Fixes the codePen and node icons slightly extending beyond their bounding box.

v0.42.5

Compare Source

Patch Changes

v0.42.4

Compare Source

Patch Changes

v0.42.3

Compare Source

Patch Changes

v0.42.2

Compare Source

Patch Changes

v0.42.1

Compare Source

Patch Changes

  • #​4354 56b8587 Thanks @​jasikpark! - Improves the color contrast of the search input placeholder text

  • #​4337 c5d0a7f Thanks @​moonmeister! - Fixes search not loading when the search script runs after the page has finished loading, for example when a Content Security Policy requires scripts to be added dynamically

  • #​4352 3edab29 Thanks @​delucis! - Fixes the Astro trailingSlash and build.format options not being applied correctly to sidebar links that include a query string or hash

v0.42.0

Compare Source

Minor Changes

  • #​3572 292fb17 Thanks @​HiDeoo! - Distributes package as JavaScript files with dedicated type declaration files instead of TypeScript source files.

  • #​4121 2623ae6 Thanks @​delucis! - Simplifies markup for Starlight’s mobile menu toggle

    ⚠️ Potentially breaking change: If you use a theme plugin, custom styles, or component overrides targeting the MobileMenuToggle button or PageFrame components, you may need to adjust these for the new markup. The button is no longer wrapped in a <starlight-menu-button> custom element and no longer uses the aria-expanded attribute. Instead, you can use the .sl-menu-button class name to target the button and the :popover-open pseudo-class to style the menu open state specifically.

    In the following example, custom styles for the menu button are updated for the new approach:

    - starlight-menu-button button {
+ .sl-menu-button {
  color: var(--sl-color-text);
}

- starlight-menu-button[aria-expanded='true'] button {
+ .sl-menu-button:has(~ :popover-open) {
  color: var(--sl-color-text-accent-high);
}

    See MobileMenuToggle.astro and PageFrame.astro on GitHub for the full source code of the updated components.

  • #​3572 292fb17 Thanks @​HiDeoo! - Removes the tagline configuration option, which was never used.

    If your configuration included a tagline option, you can safely remove it without any replacement.

  • #​4134 6135f01 Thanks @​HiDeoo! - Updates internal @astrojs/mdx, @astrojs/markdown-satteri, and satteri dependencies.

    ⚠️ BREAKING CHANGE: The following minimum versions are now required:

    • astro v7.2.10 or later
    • @astrojs/markdown-satteri 0.4.0 or later (if you use it)
    • @astrojs/markdown-remark 7.3.0 or later (if you use it)

    Please update Starlight and Astro together:

    npx @astrojs/upgrade

  • #​4121 2623ae6 Thanks @​delucis! - Refactors Starlight’s mobile menu toggle to work when JavaScript fails or is disabled

    ⚠️ BREAKING CHANGE: This release drops official support for Chromium-based browsers prior to version 116 (released August 2023), Safari-based browsers prior to version 17.0 (released September 2023), and Firefox prior to version 125 (released April 2024). You can find a list of currently supported browsers and their versions using this browserslist query.

    This change also removes the data-mobile-menu-expanded attribute, which was previously added to <body> while the mobile menu is open. If you have custom code that was depending on this attribute, you will need to update it to use a new selector to check if the mobile menu is open.

    In the following example, a custom background colour for the site header while the menu is open is updated for the new approach:

    - [data-mobile-menu-expanded] header {
+ body:has(sl-sidebar-pane:popover-open) header {
  background-color: var(--sl-color-bg);
}

v0.41.11

Compare Source

Patch Changes

  • #​4167 32a5e29 Thanks @​HiDeoo! - Fixes a layout issue and anchor links appearing for hidden headings, e.g. footnote headings, when markdown.headingLinks is enabled or the <AnchorHeading> component is used.

  • #​4148 cdfafd8 Thanks @​ematipico! - Optimizes sidebar data generation logic to speed up sites with large sidebars

v0.41.10

Compare Source

Patch Changes

v0.41.9

Compare Source

Patch Changes

v0.41.8

Compare Source

Patch Changes

v0.41.7

Compare Source

Patch Changes
  • #​4114 3e486fb Thanks @​delucis! - Fixes processing of code examples in RTL languages when using Astro’s Sätteri Markdown processor
withastro/astro (@​astrojs/ts-plugin)

v1.10.12

Compare Source

Patch Changes

v1.10.11

Compare Source

Patch Changes
  • #​17668 bef9db5 Thanks @​lazerg! - Fixes Astro's ambient types leaking into unrelated TypeScript projects. In a monorepo with hoisted node_modules, the plugin found the shared astro install from any project and injected env.d.ts and astro-jsx.d.ts into it, which pulled @types/node into projects that never asked for it. The plugin now only injects those types when the project actually depends on astro or has an astro.config.* file.

v1.10.10

Compare Source

Patch Changes
  • #​17269 c72d4f2 Thanks @​matthewp! - Fixes "Go To References" from .ts files missing usages inside .astro files that are reached through Astro.locals. The plugin now injects Astro's ambient types so type chains like Astro.locals.utils.toUpper() resolve, matching the language server.

v1.10.9

Compare Source

Patch Changes

v1.10.8

Patch Changes

v1.10.7

Patch Changes
tailwindlabs/tailwindcss-typography (@​tailwindcss/typography)

v0.5.20

Compare Source

Fixed
  • Support installing with stable versions of Tailwind CSS v4 (#​424)
tailwindlabs/tailwindcss (@​tailwindcss/vite)

v4.3.5

Compare Source

Fixed
  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#​20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#​20658, #​20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#​20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#​20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#​20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#​20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#​20632)

v4.3.4

Compare Source

Added
  • Add @tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js (#​20367)
Fixed
  • Ensure watch mode detects changes to symlinked @source files whose real paths aren't otherwise scanned (#​20356)
  • Ensure variants using @scope wrap generated utilities instead of nesting inside them (#​20369)
  • Ensure nested @scope rules preserve their scoping semantics when flattened (#​20369)
  • Preserve declarations directly inside @scope by wrapping them in :where(:scope) (#​20369)
  • Ensure generated utilities include a space in empty var() fallbacks (e.g. var(--tw-blur,) → var(--tw-blur, )) (#​20373)
  • Canonicalization: convert arbitrary breakpoint and container query variants to named equivalents (e.g. max-[64rem]:flex → max-lg:flex) (#​20380)
  • Prevent @tailwindcss/vite from crashing on every edit under Vite's experimental bundledDev mode (#​20379)
  • Ensure @tailwindcss/oxide falls back to WASM on platforms without native bindings (#​20383)
  • Extract class candidates from Ruby %w and %W literals using angle brackets or custom delimiters (e.g. %w<flex>, %w|flex|), including in Slim and Haml templates (#​20387)
  • Preserve whitespace in --default(…) values in functional @utility definitions (e.g. --default(box alphabetic) no longer becomes boxalphabetic) (#​20392)
  • Ensure automatic source detection respects negation-based .gitignore files (e.g. /* followed by !/… patterns) (#​20397)
  • Ensure root theme('…') namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of its DEFAULT key (#​20399)
  • Skip ignored directories when generating watch globs instead of walking their contents on every rebuild (#​20408)
  • Drop invalid UTF-8 candidates during class detection (#​20389)
  • Prevent @tailwindcss/vite from forcing full-page reloads for scanned files that Vite does not handle as modules (e.g. .php files) (#​20414)
  • Canonicalization: don't merge utilities that reference different theme variables set to CSS-wide keywords like unset (#​20417)
  • Don't generate utilities when a modifier is used that would otherwise be silently ignored (e.g. rounded-sm/[5], shadow-sm/foo, stroke-2/50) (#​20419)
  • Preserve and, or, and not inside selectors in supports-[…] variants (e.g. supports-[selector(a:not(.foo))]:flex) (#​20420)
  • Don't warn about Angular's ::ng-deep and :host-context() when optimizing CSS (#​20434)
  • Don't generate CSS for candidates containing an empty additional modifier (e.g. bg-red-500/50/ and group-hover/foo//bar:flex) (#​20466)
  • Ensure min-*, max-*, and container query variants with decimal values are sorted numerically (e.g. min-[40.25rem] before min-[40.5rem]) (#​20512)
  • Ensure CSS comments ending with \*/ are closed correctly instead of swallowing the CSS that follows (e.g. /* C:\temp\*/) (#​20508)
  • Improve style invalidation performance of group-* and peer-* variants (#​20513)
  • Ensure cached compilers release their loadModule and loadStylesheet callbacks after compilation (#​20531)
  • Canonicalization: preserve & when moving a pseudo-element into * or ** (e.g. [&_::before]:flex → **:[&::before]:flex) (#​20550)
  • Ensure the Set.prototype.intersection polyfill in canonicalizeCandidates(…) returns the intersection instead of the first set on Node.js < 22 (#​20562)
  • Canonicalization: ensure inline theme(…) alphas with more than 2 decimals migrate to a percentage modifier with the same opacity (e.g. theme(colors.red.500/.12345) → text-red-500/[12.345%], not text-red-500/[12.345]) (#​20563)
  • Canonicalization: preserve inline theme(…) alphas as an arbitrary percentage when a custom --opacity-* theme value would change the opacity (e.g. theme(colors.red.500/50%) → text-red-500/[50%] with --opacity-50: 10%) (#​20563)
  • Ensure the @property fallback isn't applied in Safari versions that no longer support margin-trim: inline (#​20569)
  • Treat viewport units like dvmin and svi and font-relative units like cap and rex as lengths in arbitrary values (e.g. text-[10dvmin] generates font-size instead of color) (#​20516)
  • Write plugin logs to stderr in tailwindcss canonicalize so they don't end up in the results on stdout (#​20561)
  • Extract class shorthands on later lines when Pug text, comments, or quoted attribute values contain unbalanced brackets, or a quote that doesn't start a string (e.g. input(pattern=/"/.source)) (#​20547, #​20572)
  • Underline the correct occurrence of an unsupported data type in --value(…) warnings (#​20554)
  • Canonicalization: prefer an existing candidate when collapsing utilities over another utility with the same default theme value (e.g. text-foreground text-primary → text-primary, not text-card-checked-border) (#​20540)
  • Canonicalization: don't collapse utilities into a utility that uses another theme variable with the same default value (e.g. mt-card mb-card → my-card, not my-4) (#​20574)
  • Ensure @tailwindcss/postcss rewrites relative url(…)s of stylesheets that are inlined before it runs (e.g. @imports in Vite) in optimized builds (#​20576)
  • Drop nested rules that put a combinator after a pseudo-element when using pseudo-element variants (e.g. selection:* on a utility with a nested & > * rule) (#​20575)
  • Don't generate CSS for arbitrary values with unbalanced parentheses or brackets (e.g. w-[calc(1px] or [--x:a[b]) (#​20577)
  • Canonicalization: prevent collapse: true from taking exponentially longer when classes are linked through a utility that sets many properties (e.g. sr-only) (#​20558)
  • Ensure & is substituted inside :-moz-any(…) and :-webkit-any(…) in custom variants (e.g. @custom-variant firefox (:-moz-any(&));) (#​20486)
  • Ensure the standalone macOS binaries have a valid code signature, so macOS 27 no longer kills them at launch ([#​20578](

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • 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.

@renovate renovate Bot added the renovate label Nov 3, 2026
@renovate

renovate Bot commented Nov 3, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code EALLOWREMOTE
npm error Fetching packages of type "remote" have been disabled
npm error Refusing to fetch "https://registry.npmjs.org/@tailwindcss/oxide-wasm32-wasi/-/oxide-wasm32-wasi-4.3.5.tgz"
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-07T14_43_43_189Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/npm-minor-patch branch 2 times, most recently from cd09849 to c9e6644 Compare November 3, 2026 20:27
@renovate
renovate Bot force-pushed the renovate/npm-minor-patch branch from c9e6644 to c4a914a Compare November 7, 2026 14:44
@ecv
fix: Regenerate lock file for npm minor updates
06d5aef 
Renovate bumped @astrojs/starlight and markdownlint-cli2 in package.json but
failed to refresh package-lock.json (EALLOWREMOTE in its npm), so npm ci in
CI refused the out-of-sync lock.

Key features/changes:
- Regenerate package-lock.json with npm install, then npm update to pull
  every in-range transitive dependency to its latest release
- Clears the open Dependabot alerts for vite, devalue, fast-uri, js-yaml,
  markdown-it, smol-toml, svgo, yaml, lodash and others
@renovate

renovate Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@ecv
ecv requested a review from andrewb3000 November 9, 2026 13:29
@ecv
ecv merged commit d7b0cab into main Nov 9, 2026
2 checks passed
@ecv
ecv deleted the renovate/npm-minor-patch branch November 9, 2026 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@andrewb3000 andrewb3000 andrewb3000 approved these changes

Assignees

No one assigned

Labels

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@andrewb3000 @ecv