chore(deps): bump @tootallnate/once from 2.0.0 to 2.0.1#398
chore(deps): bump @tootallnate/once from 2.0.0 to 2.0.1#398dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@tootallnate/once](https://github.com/TooTallNate/once) from 2.0.0 to 2.0.1. - [Release notes](https://github.com/TooTallNate/once/releases) - [Changelog](https://github.com/TooTallNate/once/blob/v2.0.1/CHANGELOG.md) - [Commits](TooTallNate/once@2.0.0...v2.0.1) --- updated-dependencies: - dependency-name: "@tootallnate/once" dependency-version: 2.0.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![lifeomic-review-bot[bot]](https://avatars.githubusercontent.com/u/29172293?s=60&v=4){kind=small}
There was a problem hiding this comment.
Scope
yarn.lock only: resolves @tootallnate/once to 2.0.1 (patch within 2.x), consistent with Dependabot metadata for the upstream AbortSignal-related hang fix.
Upstream: unknown (author to confirm)
CI
Gathered ciStatus.state is pending with no finished checks in context; merge should still wait on branch-required checks without this review duplicating that gate.
Regression risk
Low for a patch semver on a small transitive helper; no direct package.json churn or application source in changedFiles.
Residual risks / follow-ups
None — because the canonical change set is a single lockfile entry for a patch-level transitive bump with no new network integrations, auth surface, or app code, so remaining exposure is limited to ordinary upstream patch risk that CI is expected to cover once it completes.
This review was generated by review-bot.
Bumps @tootallnate/once from 2.0.0 to 2.0.1.
Release notes
Sourced from @tootallnate/once's releases.
Changelog
Sourced from @tootallnate/once's changelog.
Commits
bcbb21dci: fix OIDC publishing — Node 24, npm latest, provenancedc24387Version Packages (2.x) (#12)b8a6f80CI: test all Node versions on Linux onlydabcc0fci: drop EOL Node.js 14.x/16.x, add 22.xb464efcUpdate CI: modern Node versions, fix macOS ARM64 compata1e5e2dFix promise hang when AbortSignal is abortedMaintainer 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.