Skip to content

Bump @tootallnate/once from 1.1.2 to 3.0.1 (via audit fix)#139

Open
dependabot[bot] wants to merge 3 commits into
masterfrom
dependabot-npm_and_yarn-tootallnate-once-3.0.1
Open

Bump @tootallnate/once from 1.1.2 to 3.0.1 (via audit fix)#139
dependabot[bot] wants to merge 3 commits into
masterfrom
dependabot-npm_and_yarn-tootallnate-once-3.0.1

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 21, 2026

Bumps @tootallnate/once from 1.1.2 to 3.0.1.

Release notes

Sourced from @​tootallnate/once's releases.

v3.0.1

Patch Changes

  • 28dbc5d: Fix promise hang when AbortSignal is aborted

3.0.0

Major Changes

  • Output as ESM: #6

Patches

  • Remove as cast: a6a69bc2d24e1584b75ee00bfad94405ddaf8bcc

v2.0.1

Patch Changes

  • a1e5e2d: Fix promise hang when AbortSignal is aborted

2.0.0

Major Changes

  • Big refactor for v2: #5
    • Returns a regular Promise instead of CancelablePromise.
    • The Promise is strongly typed when posssible. This is the main new feature.
    • Always returns the full array of arguments passed to the event handler (i.e. what was previously once.spread() is now the regular once()).
    • Compatible with AbortController to remove event listeners before the Promise has been fulfilled.
    • Requires TypeScript v4 or newer.
    • Jest tests running CI via GitHub Actions.

Minor Changes

  • Add README.md: d00821f35b44ed48466b8e5d202c2788e3688df6
  • Create LICENSE: #2

Patches

  • Fix: c3260138d77811bde3823cebd490ff59b35fe32f
  • Remove test script: #4

Credits

Huge thanks to @​lewish and @​vivekkj123 for helping!

Changelog

Sourced from @​tootallnate/once's changelog.

3.0.1

Patch Changes

  • 28dbc5d: Fix promise hang when AbortSignal is aborted
Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​tootallnate/once since your current version.


Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will 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.

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>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label May 21, 2026
@dependabot dependabot Bot requested a review from a team as a code owner May 21, 2026 17:22
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label May 21, 2026
mixonic added 2 commits May 22, 2026 11:32
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
Copy link
Copy Markdown
Member

@mixonic mixonic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VVF over-enthusiastically attempted to including all the pinned dependencies from the audit / fix PR, which is not required or appropriate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant