chore(deps): bump @tootallnate/once from 1.1.2 to 2.0.1

[dependabot]

Bumps @tootallnate/once from 1.1.2 to 2.0.1.

Release notes

Sourced from @​tootallnate/once's releases.

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.

2.0.1

Patch Changes

• a1e5e2d: Fix promise hang when AbortSignal is aborted

Commits

• bcbb21d ci: fix OIDC publishing — Node 24, npm latest, provenance
• dc24387 Version Packages (2.x) (#12)
• b8a6f80 CI: test all Node versions on Linux only
• dabcc0f ci: drop EOL Node.js 14.x/16.x, add 22.x
• b464efc Update CI: modern Node versions, fix macOS ARM64 compat
• a1e5e2d Fix promise hang when AbortSignal is aborted
• b71b6e8 2.0.0
• 4460bff Big refactor for v2 (#5)
• c4862ce Remove test script (#4)
• de4a704 Create LICENSE (#2)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​tootallnate/once since 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 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.

[rtibblesbot]

Dependency Update Review

Package: @tootallnate/once 2.0.0 → 2.0.1 (the PR title says 1.1.2 → 2.0.1, but the actual lockfile change is a patch bump from 2.0.0 to 2.0.1; the 1.1.2 version remains in the lockfile, used by http-proxy-agent@4.0.1)
Semver risk: Patch
Dependency type: Indirect/transitive — dependency of http-proxy-agent@5.0.0 → make-fetch-happen (dev tooling)
CI status: Failing, but failures are pre-existing infrastructure issue (pnpm requires Node.js ≥22.13, runner has v20.20.2) — unrelated to this PR

Changelog Analysis

Sources consulted:

• PR body (release notes from dependabot)
• Lockfile diff

Breaking changes: None — this is 2.0.0 → 2.0.1, a patch release.

Security fixes: None listed.

Other notable changes:

• Fix promise hang when AbortSignal is aborted (from commit a1e5e2d)

Compatibility Assessment

• Only pnpm-lock.yaml changed — no source code migration needed
• Both @tootallnate/once@1.1.2 (via http-proxy-agent@4.0.1) and @tootallnate/once@2.0.1 (via http-proxy-agent@5.0.0) coexist in the lockfile after this update
• Peer dependency changes: none
• Code changes required: none
• Prior failed attempts: none found

Recommendation

APPROVE — patch fix on an indirect dev-tooling dependency, no code changes required, CI failures are pre-existing and unrelated.

---

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Reviewed the pull request diff checking for:

• Correctness: bugs, edge cases, undocumented behavior, resource leaks, hardcoded values
• Design: unnecessary complexity, naming, readability, comment accuracy, redundant state
• Architecture: duplicated concerns, minimal interfaces, composition over inheritance
• Testing: behavior-based assertions, mocks only at hard boundaries, accurate coverage
• Completeness: missing dependencies, unupdated usages, i18n, accessibility, security
• Principles: DRY (same reason to change), SRP, Rule of Three (no premature abstraction)
• Checked CI status and linked issue acceptance criteria
• For UI changes: inspected screenshots for layout, visual completeness, and consistency