Repository navigation
Bump dev dependencies for security advisories - #515
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes the open Dependabot alerts for dev dependencies. Runtime
dependenciesand the published API do not change. The builtdistoutput is byte-for-byte the same as onmain.Packages
Other lockfile changes come with these: the rest of the
@vitest/*4.1.12 packages, rolldown 1.2.16 and its platform bindings,@oxc-project/types, postcss 8.5.32, nanoid 3.3.20, chai 6.3.0, std-env 4.3.0, tinyrainbow 3.2.0, obug 2.2.1. They are all dev-only. No new package names enter the lockfile. Every new version was published at least 4 days ago.node-forge 1.4.1 fixes GHSA-86w9-cpqp-85rv (see the forge changelog), so the alert closes although the advisory lists no patched version.
Not fixed
4.2.0 - 4.3.1: no fixed version is published.Test
Same results on this branch and on
main:npm ci,npm run lint,tsc --noEmit: pass.npm testandnpm run test:coverage: 202 passed, 16 skipped. Coverage numbers are the same.npm run build: passes. Thedistfile hashes are the same as onmain.blazeentry points, create aMixinApiclient, calluniqueConversationID. The export counts and output are the same.npm run size:dist/index.jsis 83.94 kB against an 80 kB limit on both branches. This failure already exists onmain.