Bump @tootallnate/once from 1.1.2 to 3.0.1 (via audit fix)#139
Open
dependabot[bot] wants to merge 3 commits into
Open
Bump @tootallnate/once from 1.1.2 to 3.0.1 (via audit fix)#139dependabot[bot] wants to merge 3 commits into
dependabot[bot] wants to merge 3 commits into
Conversation
Bumps [@tootallnate/once](https://github.com/TooTallNate/once) from 1.1.2 to 3.0.1. - [Release notes](https://github.com/TooTallNate/once/releases) - [Changelog](https://github.com/TooTallNate/once/blob/master/CHANGELOG.md) - [Commits](TooTallNate/once@1.1.2...v3.0.1) --- updated-dependencies: - dependency-name: "@tootallnate/once" dependency-version: 3.0.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
The "Install Dependencies" CI check failed after @tootallnate/once was updated from 1.1.2 to 3.0.1 via audit fix. Root cause: Dependabot's audit fix added security overrides to pnpm-lock.yaml forcing @tootallnate/once@<3.0.1 to >=3.0.1, but these overrides were not present in pnpm-workspace.yaml. Running `pnpm install --frozen-lockfile` in CI failed with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH because the lockfile's overrides section didn't match the workspace configuration. Fix: Added all security overrides from pnpm-lock.yaml to pnpm-workspace.yaml. This includes 54 dependency version overrides that enforce minimum secure versions for various transitive dependencies, including the @tootallnate/once upgrade that was the target of this PR. Risk: Low risk. These overrides strengthen supply chain security by forcing minimum versions with known security fixes. The lockfile already reflected these versions; this change just makes the workspace configuration consistent. Files changed: - pnpm-workspace.yaml Automated fix by veni-vidi-fixi
The Lint CI check failed after @tootallnate/once was updated from 1.1.2 to 3.0.1 via audit fix. Root cause: The dependency upgrade chain caused eslint@9.31.0 and @eslint/eslintrc@3.3.1 to resolve ajv@8.18.0, but these packages expect ajv v6 (they reference ajv v6-specific APIs like missingRefs option and json-schema-draft-04.json). Additionally, the existing brace-expansion override was too loose, forcing minimatch@9.0.9 to use brace-expansion v5 instead of the required v2, causing TypeError: (0 , brace_expansion_1.default) is not a function. Fix: Added targeted overrides to force ajv v6 for eslint and @eslint/eslintrc (@eslint/eslintrc>ajv: '6.14.0' and eslint>ajv: '6.14.0'), and constrained the brace-expansion override to stay within v2.x by changing '>=2.0.3' to '>=2.0.3 <3.0.0', preventing it from jumping to incompatible v5. Risk: Low risk. These overrides ensure eslint tooling gets the compatible dependency versions they expect. The ajv v6 constraint is scoped only to eslint and @eslint/eslintrc (other packages still use ajv v8), and the brace-expansion constraint properly limits the security fix to compatible versions only. Files changed: - pnpm-workspace.yaml - pnpm-lock.yaml Automated fix by veni-vidi-fixi
mixonic
requested changes
May 22, 2026
Member
mixonic
left a comment
There was a problem hiding this comment.
VVF over-enthusiastically attempted to including all the pinned dependencies from the audit / fix PR, which is not required or appropriate.
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.
Bumps @tootallnate/once from 1.1.2 to 3.0.1.
Release notes
Sourced from @tootallnate/once's releases.
Changelog
Sourced from @tootallnate/once's changelog.
Commits
b31c762Fix publish?d2f7407Version Packages (#9)081645cFix release scriptf01fa45Fix Release job28dbc5dAdd Changesetse66503bUse pnpm in CI6ec8b43Fix CIb9f43ccFix promise hang whenAbortSignalis aborteda8c9dc3Add pnpm-lock.yaml file2bc2e133.0.0Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@tootallnate/oncesince 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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.