Skip to content

Update devDependencies#7

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/devdependencies
Open

Update devDependencies#7
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/devdependencies

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Feb 9, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@changesets/cli (source) 2.27.12 → 2.31.0 age adoption passing confidence
@types/bun (source) 1.2.2 → 1.3.14 age adoption passing confidence
bun-plugin-dts 0.3.0 → 0.4.0 age adoption passing confidence
typedoc (source) 0.27.7 → 0.28.19 age adoption passing confidence
typedoc-plugin-frontmatter (source) 1.1.2 → 1.3.1 age adoption passing confidence
typedoc-plugin-markdown (source) 4.4.2 → 4.11.0 age adoption passing confidence
typedoc-plugin-mdn-links 4.0.12 → 4.0.15 age adoption passing confidence

Release Notes

changesets/changesets (@​changesets/cli)

v2.31.0

Compare Source

Minor Changes

  • #​1889 96ca062 Thanks @​mixelburg! - Error on unsupported flags for individual CLI commands and print the matching command usage to make mistakes easier to spot.

  • #​1873 42943b7 Thanks @​mixelburg! - Respond to --help on all subcommands. Previously, --help was only handled when it was the sole argument; passing it alongside a subcommand (e.g. changeset version --help) would silently execute the command instead. Now --help always exits early and prints per-command usage when a known subcommand is provided, or the general help text otherwise.

Patch Changes

v2.30.0

Compare Source

v2.29.8

Compare Source

v2.29.7

Compare Source

Patch Changes

v2.29.6

Compare Source

Patch Changes

v2.29.5

Compare Source

Patch Changes

v2.29.4

Compare Source

Patch Changes

v2.29.3

Compare Source

Patch Changes

v2.29.2

Compare Source

Patch Changes

v2.29.1

Compare Source

Patch Changes

v2.29.0

Compare Source

Minor Changes

v2.28.1

Compare Source

Patch Changes

v2.28.0

Compare Source

Minor Changes
Patch Changes
wobsoriano/bun-plugin-dts (bun-plugin-dts)

v0.4.0

Compare Source

TypeStrong/TypeDoc (typedoc)

v0.28.19

Compare Source

Features
  • Added French translations for the TypeDoc interface and help descriptions.
  • Added support for triple-slash comment style, which requires exactly three slashes in the comment, #​3089.
Bug Fixes
  • Corrected handling of icon caching for custom themes which use SVGs with a larger view box than TypeDoc's default theme.
  • Fixed short summary comment handling on module pages when the project source files use Windows line endings, #​3093.
Thanks!

v0.28.18

Compare Source

Features

v0.28.17

Compare Source

Bug Fixes
  • Improved handling of comments for type aliases which have been declaration merged with functions, #​3064.
  • Fixed anchor link generation to members named $, #​3065.
  • Corrected typing of the plugin option to permit functions, #​3066.
  • Warnings about unused @param tags will now be properly suppressed when they come from declaration files and
    the suppressCommentWarningsInDeclarationFiles option is enabled, #​3070.
  • Fixed conversion of types referencing type parameters on functions, #​3071.
Thanks!

v0.28.16

Compare Source

Bug Fixes
  • Fixed an issue causing TypeDoc to fail to generate documentation when implementing interfaces, #​3052.
  • Fixed an issue preventing automatic entry point discovery on Windows, #​3057.
  • Improved vertical positioning of text icons, #​3056.
  • TypeDoc no longer includes source location information for type literal reflections. This could sometimes
    cause TypeDoc to infer the wrong path when resolving base paths for display.
  • Adjusted markdown rendering to allow markdownItLoader to override more rendering #​3055.
Features
  • Added support for regions for @include in .tsx, .cjs, and .mjs file references #​3048.
  • Comments for TS-in-JS @typedef tags may now specify modifier tags with the inline tag syntax {@​mod}.
    This makes it possible to add modifier tags to these members, which previously was not possible as
    TypeScript's parsing stops for these members at the next non-braced tag, #​2916 and #​3050.
  • A typedoc-config.schema.json is now included in the root of the package with a JSON schema for TypeDoc's
    configuration file. The schema for the latest version is also published at https://typedoc.org/schema.json
    and will automatically be picked up when writing typedoc.json files if you are using VSCode, #​3054.
Thanks!

v0.28.15

Compare Source

Features
  • The gitRevision option now accepts the special value {branch}, which indicates source links should use
    the current git branch for links, #​3041.
  • Introduced validation.invalidPath for suppressing warnings caused by referencing relative paths which
    do not exist when building the documentation, #​3033.
  • API: Introduced Logger.validationWarning for validation which occurs during conversion rather than
    during TypeDoc's normal validation step, #​3033.

v0.28.14

Compare Source

Features
  • Introduced the preservedTypeAnnotationTags option to specify tags whose type annotations should
    be copied to the output documentation, #​3020.
    API: Introduced typeAnnotation on CommentTag
  • Added excludePrivateClassFields option to hide #private members while allowing private members, #​3017.
  • Added support for TypeScript's @this tag for JS files which describe this parameters, #​3026.

v0.28.13

Compare Source

Features
  • The basePath option now also affects relative link resolution, TypeDoc will also check for
    paths relative to the provided base path. If you instead want TypeDoc to only change the rendered
    base path for sources, use the displayBasePath option, #​3009.
Bug Fixes
  • Fixed bug introduced in 0.28.8 where TypeDoc could not render docs with some mixin classes, #​3007.
  • @inheritDoc will now correctly overwrite @remarks and @returns blocks on the target comment, #​3012.
  • The externalSymbolLinkMappings option now works properly on links pointing to inherited/overwritten signatures, #​3014.

v0.28.12

Compare Source

Bug Fixes
  • Variables marked with @enum now work for symbols imported from another module, #​3003.
  • Improved magic introduced with #​2999 to work with imported symbols, #​3003.
  • Fixed relative link resolution to file names containing percent encoded URLs, #​3006.
  • Linking to the project's README file with a relative link will now behave as expected, #​3006.
  • Reduced unnecessary HTML element rendering in default theme.
    API: Reflection.hasComment and Comment.hasVisibleComponent now accepts an optional notRenderedTags parameter.

v0.28.11

Compare Source

Features
  • Object properties declared with shorthand property assignment will now use the variable's comment
    if they do not have their own comment, #​2999.
Bug Fixes
  • Fixed link resolution not working correctly in first comment on the file in some cases, #​2994.
  • Optional methods are now rendered with a trailing ? in the reflection preview and signature, #​2995.
  • The compilerOptions option now functions properly with non-boolean options, #​3000.
  • Configuration errors within the compilerOptions option are now handled gracefully, #​3000.
  • Fixed improper casing of "Type Declaration" header, #​3002.

v0.28.10

Compare Source

Bug Fixes
  • Fixed inconsistent anchors on module pages for re-exports, #​2990.
  • Markdown references which appear to be footnotes will no longer be checked for links, #​2991.

v0.28.9

Compare Source

Features
  • Add support for TypeScript 5.9, #​2989.
Bug Fixes
  • Fixed bug introduced in 0.28.8 where TypeDoc could not render docs when members inherited from a complex type alias, #​2982.
  • Fixed automatic discovery of entry points when not running in packages mode, #​2988.
  • Fixed discovery of package.json file when running with entry points containing a glob, #​2985.

v0.28.8

Compare Source

Features
  • If using JS config files, the plugin function can now be given plugin functions to load.
  • Permit - within tag names to support typescript-json-schema's @TJS-type tag, #​2972.
  • Exposed Context.createSymbolId for use by plugins.
Bug Fixes
  • Relative links in <img srcset> will now be discovered by TypeDoc, #​2975.
  • Relative links in <source src> and <source srcset> elements will now be discovered by TypeDoc, #​2975.
  • Improved inherited from/overwrites link discovery to point to parent properties in more cases, #​2978
Thanks!

v0.28.7

Compare Source

Features
  • Introduced the @sortStrategy tag to override the sort option on a specific reflection, #​2965.
Bug Fixes
  • Classes and functions exported with export { type X } are no longer missing comments, #​2970.
  • Setting locale to an unknown value will now cause TypeDoc to operate in English instead of a debug locale.
  • Array options will now report an error if set to a non-array/non-string value.

v0.28.6

Compare Source

Features
  • TypeDoc now supports resolving relative paths in links to the package directory as belonging to the project, #​2961.
  • Declarations without comments will now check for comments on their export specifier, #​2964.
Bug Fixes
  • Attempting to highlight a supported language which is not enabled is now a warning, not an error, #​2956.
  • Improved compatibility with CommonMark's link parsing, #​2959.
  • Classes, variables, and functions exported with export { type X } are now detected and converted as interfaces/type aliases, #​2962.
  • Improved warning messaging for links to symbols which were resolved, but the symbols were not included in the documentation, #​2967.
  • Fixed an issue preventing nested documents from being deserialized from TypeDoc's JSON output or used in packages mode, #​2969.
Thanks!

v0.28.5

Compare Source

Bug Fixes
  • References to type aliases defined as mapped types will now correctly create a reference to the type alias, #​2954.
  • ignoredHighlightLanguages can now be used to prevent warnings for codeblocks containing languages
    which are supported by Shiki but are not loaded, #​2956.

v0.28.4

Compare Source

Features
  • The navigation in the default theme will now attempt to break long names onto multiple lines, #​2940.
  • Added German (de) localization, #​2941.
Bug Fixes
  • TypeDoc's default theme now uses the same chevron for all collapsible elements, #​2924
    The chevronSmall helper is now deprecated and will be removed with v0.29.0.
  • Classes/interfaces marked with @hidden will no longer appear in the
    "Hierarchy" section of the docs.
  • TypeDoc now handles wildcard JSDoc types, #​2949.
Thanks!

v0.28.3

Compare Source

Bug Fixes
  • @inline now functions when referencing tuple types, #​2932.
  • @link links to the current page are now rendered, #​2934.
  • @includeCode now supports regions in TypeScript files with .mts and .cts file extensions, #​2935.
  • Aliased symbols (re-exports) are now resolved before checking if they are excluded/external, #​2937.
  • Improved error reporting when paths including Windows separators are provided as globs, #​2938.

v0.28.2

Compare Source

Features
  • @group none and @category none will now render their children without a section
    heading in the default theme, #​2922.
  • Added @disableGroups tag to completely disable the grouping mechanism for a
    given reflection, #​2922.
Bug Fixes
  • Variables using @class now correctly handle @category, #​2914.
  • Variables using @class now include constructor parameters, #​2914.
  • Variables using @class with a generic first constructor function now adopt
    that function's type parameters as the class type parameters, #​2914.
  • When printing entry point globs which fail to match any paths, TypeDoc will no longer normalize the glob, #​2918.
  • Inlining types can now handle more type variants, #​2920.
  • Fixed behavior of externalSymbolLinkMappings option when URL is set to #, #​2921.
  • Fixed broken links within module pages when structure-dir router was used, #​2928.
  • Type parameters on JS classes defined with @typedef now correctly handle the constraint, #​2929.
  • API: toString on types containing index signatures now behave correctly, #​2917.
  • Added @inlineType to the list of tags excluded by default.

v0.28.1

Compare Source

Features
  • Introduced the preservedTypeAnnotationTags option to specify tags whose type annotations should
    be copied to the output documentation, #​3020.
    API: Introduced typeAnnotation on CommentTag
  • Added excludePrivateClassFields option to hide #private members while allowing private members, #​3017.
  • Added support for TypeScript's @this tag for JS files which describe this parameters, #​3026.

v0.28.0

Compare Source

Breaking Changes
  • TypeDoc now expects all input globs paths to be specified with / path separators, #​2825.
  • TypeDoc's --entryPointStrategy merge mode now requires JSON from at least version 0.28.0.
  • Removed jp translations from lang, to migrate switch to ja.
  • File name references in intentionallyNotExported now use a package name/package relative path instead of an absolute path for matching.
  • The source-order sort ordering now considers package names / package relative paths instead of using the absolute paths to a file.
  • TypeDoc will only check for a project README file next to the discovered package.json file if --readme is not set
    this change improves handling of monorepo setups where some packages have readme files and others do not, #​2875.
  • Function-like variable exports will now only be automatically converted as function types if
    they are initialized with a function expression. TypeDoc can be instructed to convert them as functions
    with the @function tag, #​2881.
  • Object literal type alias types will now be converted in a way which causes them to be rendered more similarly
    to how interfaces are rendered, #​2817.
API Breaking Changes
  • ProjectReflection.getReflectionFromSymbol and ProjectReflection.getSymbolFromReflection have been moved to Context
  • Path and PathArray parameter types now always contain normalized paths.
  • Introduced a Router which is used for URL creation. Reflection.url,
    Reflection.anchor, and Reflection.hasOwnDocument have been removed.
  • Deserializer.reviveProject(s) no longer accepts an option to add project documents.
  • Deserializer.reviveProjects now requires an alwaysCreateEntryPointModule option.
  • Comment.serializeDisplayParts no longer requires a serializer argument.
  • ReflectionSymbolId.fileName is now optional, TypeDoc now stores a combination of a package name and package relative path instead.
    The fileName property will be present when initially created, but is not serialized.
  • Removed DeclarationReflection.relevanceBoost attribute which was added for plugins, but never used.
  • i18n proxy is no longer passed to many functions, instead, reference i18n exported from the module directly.
  • ReflectionKind.singularString and ReflectionKind.pluralString now returns translated strings.
    The methods on Internationalization to do this previously have been removed.
  • The HTML output structure for the search box has changed to support the new modal.
  • DefaultThemeRenderContext's typeDeclaration and typeDetailsIfUseful
    methods now require both a reflection and a type in order to support
    @expandType
Features
  • Add support for TypeScript 5.8.x
  • The search modal in the HTML output has been rewritten to provide better mobile support
  • Added a --router option which can be used to modify TypeDoc's output folder
    structure. This can be extended with plugins, #​2111.
  • Introduced the @primaryExport modifier tag to provide more fine grained
    control over export conversion order, #​2856
  • Introduced packagesRequiringDocumentation option for validation.notDocumented, TypeDoc will expect comments to be present for symbols in the specified packages.
  • TypeDoc now exports a typedoc/browser entrypoint for parsing and using serialized JSON files, #​2528.
  • Type packageOptions as Partial<TypeDocOptions>, #​2878.
  • TypeDoc will now warn if an option which should only be set at the root level is set in packageOptions, #​2878.
  • Introduced @function tag to force TypeDoc to convert variable declarations with a type annotation as functions, #​2881.
  • Exposed a TypeDoc global object in the HTML theme which can be used to prevent TypeDoc from using localStorage, #​2872.
  • Introduced @preventInline and @inlineType tags for further control extending the @inline tag, #​2862.
  • Introduced @preventExpand and @expandType tags for further control extending the @expand tag, #​2862.
  • API: Introduced DefaultThemeRenderContext.reflectionIcon for more granular control over displayed reflection icons.
Bug Fixes
  • TypeDoc will now only create references for symbols re-exported from modules.
  • Variable-functions will now prefer placing the comment on the signature if there is only one signature present, #​2824.
  • User filter settings will no longer sometimes cause the search to have fewer visible results than expected.
  • Fixed handling of expando functions which were also merged with a namespace, #​2876.
  • Fixed rendering of function types within arrays and union types, #​2892.
  • Fixed an issue where if the theme JS didn't load, the page wouldn't be shown, #​2894.
Thanks!

v0.27.9

Compare Source

This will be the last v0.27.x release, see #​2868 for discussion on the 0.28 beta.

Features
  • Added support for TypeScript 5.8

v0.27.8

Compare Source

Features
  • The visibilityFilter option now supports individual signatures, #​2846.
  • The favicon option may now be given a link starting with https?:// instead of a path, #​2851.
  • TypeDoc now supports specifying # as the link in externalSymbolLinkMappings to indicate the type should not be linked to, #​2853.
Bug Fixes
  • Fixed an issue where unrecognized languages would incorrectly be listed in the list of languages with translations, #​2852.
  • Unresolved external type references will no longer incorrectly linked to undefined, #​2854.
Thanks!
typedoc2md/typedoc-plugin-markdown (typedoc-plugin-frontmatter)

v1.3.1

Compare Source

Patch Changes
  • Correctly resolve frontmatterCommentTags for signatures (#​848).

v1.3.0

Compare Source

Minor Changes
  • typedoc-plugin-markdown 4.5 compatibility fixes.

v1.2.1

Compare Source

Patch Changes
  • Prevent line wrapping as default in yaml.stringify() options (#​771).

v1.2.0

Compare Source

Minor Changes
  • Expose "yamlStringifyOptions" option (#​771).
typedoc2md/typedoc-plugin-markdown (typedoc-plugin-markdown)

v4.11.0

Compare Source

Minor Changes
  • Improved rendering of union types when documented type details are present (#​857).
  • Improved rendering of union types used in parameter declarations.
  • When a function returns another function, full documentation for the returned function is now only shown when meaningful comments are present, aligning with the default theme.
  • Index signature declarations are now rendered as blockquotes for improved consistency.
Patch Changes
  • Added locale translations for grouped @example headings (#​858).
  • Function-typed properties are now rendered without parentheses in headings. This avoids implying that the member is a method and more accurately reflects that it is a property whose type is a function.
  • Optional properties are now indicated with ? in the property name, making the optionality explicit.
  • All pipe characters (|) in union type output are now escaped.

v4.10.0

Compare Source

Minor Changes
  • A JSON schema to be consumed by typedoc.json is now published to the package root.
  • Mark parameters with default values as optional, matching the default TypeDoc theme.
Patch Changes
  • Fixed markdownlint errors related to empty table cells and invalid link fragments.
  • Anchors inside table cells (when property formats equal "table") are now namespaced by reflection kind (for example property-foo) to prevent collisions with Markdown heading slugs and ensure stable in-page links (#​856).
  • Resolve "does not have an anchor but one was requested" warnings in verbose log mode (#​850).
  • Guard against undefined types causing errors in complex types in tables (thanks @​ilyabo).

v4.9.0

Compare Source

Minor Changes
  • Exposed new option navigationJson that can be used to write navigation structure as JSON to disk.
Patch Changes
  • Remove type params from inline reflection titles when router=module to resolve anchoring issues (#​843).

v4.8.1

Compare Source

Patch Changes
  • Correctly handle empty markdown links (#​836).

v4.8.0

Compare Source

Minor Changes
  • Exposed additional placeholders in pageTitleTemplates and adjusted default templates (#​831).
  • Tweaked the format of abstract class page titles to include the translated abstract keyword (e.g., "Abstract Class: MyClass") for improved readability.
  • Added strikeDeprecatedPageTitles option.
Patch Changes
  • Fix incorrect link fragments (#​832).

v4.7.1

Compare Source

Patch Changes
  • Escape square brackets in index signature types (#​829).
  • Fix missing segments in declaration titles that contain periods.

v4.7.0

Compare Source

Minor Changes
  • Added useCustomAnchors and customAnchorsFormat options - thanks @​ocavue.
Patch Changes
  • Fix incorrect overload function comments (#​827).

v4.6.4

Compare Source

Patch Changes
  • Added theme translations for "de" locale.
  • Fix navigation items without group or categories (@group/@&#8203;category=none) (#​815).
  • Correctly handle sidebar groups for packages with merged modules.

v4.6.3

Compare Source

Patch Changes
  • Correctly ha

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Feb 9, 2026 •
edited
Loading

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updated@​types/​bun@​1.2.2 ⏵ 1.3.141001004993100
Updatedtypedoc-plugin-frontmatter@​1.1.2 ⏵ 1.3.199 +1010073 +381 +1100
Updatedtypedoc-plugin-markdown@​4.4.2 ⏵ 4.11.0100 +110080 +186100
Updatedtypedoc-plugin-mdn-links@​4.0.12 ⏵ 4.0.1510010083 +293100
Updatedbun-plugin-dts@​0.3.0 ⏵ 0.4.090 +3100100 +486 +6100
Updatedtypedoc@​0.27.7 ⏵ 0.28.191001009793 -1100
Updated@​changesets/​cli@​2.27.12 ⏵ 2.31.096100100 +195 -1100

View full report

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Feb 9, 2026 •
edited
Loading

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm entities is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: ? → npm/typedoc@0.28.19 → npm/typedoc-plugin-mdn-links@4.0.15 → npm/entities@4.5.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm markdown-it is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: ? → npm/typedoc@0.28.19 → npm/typedoc-plugin-mdn-links@4.0.15 → npm/markdown-it@14.1.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/markdown-it@14.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Medium
System shell access: npm @inquirer/external-editor in module child_process

Module: child_process

Location: Package overview

From: ? → npm/@changesets/cli@2.31.0 → npm/@inquirer/external-editor@1.0.3

ℹ Read more on: This package | This alert | What is shell access?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@inquirer/external-editor@1.0.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Medium
System shell access: npm cross-spawn in module child_process

Module: child_process

Location: Package overview

From: ? → npm/@changesets/cli@2.31.0 → npm/cross-spawn@7.0.6

ℹ Read more on: This package | This alert | What is shell access?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/cross-spawn@7.0.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Medium
Potential vulnerability: npm picomatch with risk level "medium"

Location: Package overview

From: ? → npm/@changesets/cli@2.31.0 → npm/picomatch@2.3.2

ℹ Read more on: This package | This alert | Navigating potential vulnerabilities

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: It is advisable to proceed with caution. Engage in a review of the package's security aspects and consider reaching out to the package maintainer for the latest information or patches.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/picomatch@2.3.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Medium
System shell access: npm term-size in module child_process

Module: child_process

Location: Package overview

From: ? → npm/@changesets/cli@2.31.0 → npm/term-size@2.2.1

ℹ Read more on: This package | This alert | What is shell access?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/term-size@2.2.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm argparse was last published 6 years ago

Last Publish: 8/28/2020, 9:14:26 PM

From: ? → npm/@changesets/cli@2.31.0 → npm/argparse@1.0.10

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/argparse@1.0.10. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm argparse was last published 6 years ago

Last Publish: 8/28/2020, 9:14:26 PM

From: ? → npm/typedoc@0.28.19 → npm/@changesets/cli@2.31.0 → npm/typedoc-plugin-mdn-links@4.0.15 → npm/argparse@2.0.1

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/argparse@2.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm array-union was last published 5 years ago

Last Publish: 3/1/2021, 6:43:09 PM

From: ? → npm/@changesets/cli@2.31.0 → npm/array-union@2.1.0

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/array-union@2.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm common-path-prefix was last published 7 years ago

Last Publish: 11/3/2019, 5:04:02 PM

From: ? → npm/bun-plugin-dts@0.4.0 → npm/common-path-prefix@3.0.0

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/common-path-prefix@3.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm dir-glob was last published 7 years ago

Last Publish: 6/29/2019, 4:22:06 PM

From: ? → npm/@changesets/cli@2.31.0 → npm/dir-glob@3.0.1

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/dir-glob@3.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm esprima was last published 8 years ago

Last Publish: 7/13/2018, 8:39:14 AM

From: ? → npm/@changesets/cli@2.31.0 → npm/esprima@4.0.1

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/esprima@4.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm extendable-error was last published 6 years ago

Last Publish: 7/15/2020, 4:16:37 PM

From: ? → npm/@changesets/cli@2.31.0 → npm/extendable-error@0.1.7

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/extendable-error@0.1.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm get-caller-file was last published 7 years ago

Last Publish: 3/9/2019, 9:48:30 PM

From: ? → npm/bun-plugin-dts@0.4.0 → npm/get-caller-file@2.0.5

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/get-caller-file@2.0.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm is-extglob was last published 9 years ago

Last Publish: 12/11/2016, 4:04:24 AM

From: ? → npm/@changesets/cli@2.31.0 → npm/is-extglob@2.1.1

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/is-extglob@2.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm is-number was last published 8 years ago

Last Publish: 7/4/2018, 3:08:58 PM

From: ? → npm/@changesets/cli@2.31.0 → npm/is-number@7.0.0

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/is-number@7.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm is-windows was last published 8 years ago

Last Publish: 2/14/2018, 7:36:43 AM

From: ? → npm/@changesets/cli@2.31.0 → npm/is-windows@1.0.2

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/is-windows@1.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm lodash.startcase was last published 10 years ago

Last Publish: 8/13/2016, 5:45:05 PM

From: ? → npm/@changesets/cli@2.31.0 → npm/lodash.startcase@4.4.0

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/lodash.startcase@4.4.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm lunr was last published 6 years ago

Last Publish: 8/19/2020, 8:30:07 PM

From: ? → npm/typedoc@0.28.19 → npm/typedoc-plugin-mdn-links@4.0.15 → npm/lunr@2.3.9

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/lunr@2.3.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm merge2 was last published 6 years ago

Last Publish: 6/3/2020, 7:39:10 AM

From: ? → npm/@changesets/cli@2.31.0 → npm/merge2@1.4.1

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/merge2@1.4.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm outdent was last published 5 years ago

Last Publish: 12/16/2020, 10:50:08 PM

From: ? → npm/@changesets/cli@2.31.0 → npm/outdent@0.5.0

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/outdent@0.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm path-key was last published 5 years ago

Last Publish: 4/9/2021, 12:04:51 PM

From: ? → npm/@changesets/cli@2.31.0 → npm/path-key@3.1.1

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/path-key@3.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm queue-microtask was last published 5 years ago

Last Publish: 3/22/2021, 5:37:10 AM

From: ? → npm/@changesets/cli@2.31.0 → npm/queue-microtask@1.2.3

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/queue-microtask@1.2.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm require-directory was last published 11 years ago

Last Publish: 5/28/2015, 8:31:04 AM

From: ? → npm/bun-plugin-dts@0.4.0 → npm/require-directory@2.1.1

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/require-directory@2.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm resolve-from was last published 7 years ago

Last Publish: 4/15/2019, 4:06:25 AM

From: ? → npm/@changesets/cli@2.31.0 → npm/resolve-from@5.0.0

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/resolve-from@5.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm run-parallel was last published 5 years ago

Last Publish: 2/10/2021, 2:58:08 AM

From: ? → npm/@changesets/cli@2.31.0 → npm/run-parallel@1.2.0

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/run-parallel@1.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm safer-buffer was last published 8 years ago

Last Publish: 4/8/2018, 10:42:42 AM

From: ? → npm/@changesets/cli@2.31.0 → npm/safer-buffer@2.1.2

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm shebang-command was last published 7 years ago

Last Publish: 9/6/2019, 2:53:25 PM

From: ? → npm/@changesets/cli@2.31.0 → npm/shebang-command@2.0.0

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/shebang-command@2.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm strip-bom was last published 5 years ago

Last Publish: 4/16/2021, 6:54:19 PM

From: ? → npm/@changesets/cli@2.31.0 → npm/strip-bom@3.0.0

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/strip-bom@3.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Low
Unmaintained: npm to-regex-range was last published 7 years ago

Last Publish: 4/7/2019, 6:04:37 AM

From: ? → npm/@changesets/cli@2.31.0 → npm/to-regex-range@5.0.1

ℹ Read more on: This package | This alert | What are unmaintained packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/to-regex-range@5.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

See 1 more row in the dashboard

View full report

@renovate renovate Bot force-pushed the renovate/devdependencies branch 2 times, most recently from df2b23e to f681374 Compare February 14, 2026 11:12
@renovate renovate Bot force-pushed the renovate/devdependencies branch from f681374 to 151d5be Compare March 8, 2026 11:12
@renovate renovate Bot force-pushed the renovate/devdependencies branch from 151d5be to 3d25c48 Compare April 15, 2026 11:19
@renovate renovate Bot changed the title chore(deps): update devdependencies Update devDependencies Apr 15, 2026
@renovate renovate Bot force-pushed the renovate/devdependencies branch from 3d25c48 to dfe3c69 Compare April 19, 2026 05:57
@renovate renovate Bot force-pushed the renovate/devdependencies branch from dfe3c69 to 64fe861 Compare April 30, 2026 03:11
@renovate renovate Bot force-pushed the renovate/devdependencies branch from 64fe861 to 3ac6d1e Compare May 13, 2026 07:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@thewilloftheshadow thewilloftheshadow Awaiting requested review from thewilloftheshadow thewilloftheshadow is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants