Update dependency async to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
async (source)	^2.6.4 → ^3.0.0

---

Release Notes

caolan/async (async)

v3.2.6

Compare Source

v3.2.5

Compare Source

• Ensure Error objects such as AggregateError are propagated without modification (#​1920)

v3.2.4

Compare Source

• Fix a bug in priorityQueue where it didn't wait for the result. (#​1725)
• Fix a bug where unshiftAsync was included in priorityQueue. (#​1790)

v3.2.3

Compare Source

• Fix bugs in comment parsing in autoInject. (#​1767, #​1780)

v3.2.2

Compare Source

• Fix potential prototype pollution exploit

v3.2.1

Compare Source

• Use queueMicrotask if available to the environment (#​1761)
• Minor perf improvement in priorityQueue (#​1727)
• More examples in documentation (#​1726)
• Various doc fixes (#​1708, #​1712, #​1717, #​1740, #​1739, #​1749, #​1756)
• Improved test coverage (#​1754)

v3.2.0

Compare Source

• Fix a bug in Safari related to overwriting func.name
• Remove built-in browserify configuration (#​1653)
• Varios doc fixes (#​1688, #​1703, #​1704)

v3.1.1

Compare Source

• Allow redefining name property on wrapped functions.

v3.1.0

Compare Source

• Added q.pushAsync and q.unshiftAsync, analagous to q.push and q.unshift, except they always do not accept a callback, and reject if processing the task errors. (#​1659)
• Promises returned from q.push and q.unshift when a callback is not passed now resolve even if an error ocurred. (#​1659)
• Fixed a parsing bug in autoInject with complicated function bodies (#​1663)
• Added ES6+ configuration for Browserify bundlers (#​1653)
• Various doc fixes (#​1664, #​1658, #​1665, #​1652)

v3.0.1

Compare Source

Bug fixes

• Fixed a regression where arrays passed to queue and cargo would be completely flattened. (#​1645)
• Clarified Async's browser support (#​1643)

v3.0.0

Compare Source

The async/await release!

There are a lot of new features and subtle breaking changes in this major version, but the biggest feature is that most Async methods return a Promise if you omit the callback, meaning you can await them from within an async function.

const results = await async.mapLimit(urls, 5, async url => {
    const resp = await fetch(url)
    return resp.body
})

Breaking Changes

• Most Async methods return a Promise when the final callback is omitted, making them await-able! (#​1572)
• We are now making heavy use of ES2015 features, this means we have dropped out-of-the-box support for Node 4 and earlier, and many old versions of browsers. (#​1541, #​1553)
• In queue, priorityQueue, cargo and cargoQueue, the "event"-style methods, like q.drain and q.saturated are now methods that register a callback, rather than properties you assign a callback to. They are now of the form q.drain(callback). If you do not pass a callback a Promise will be returned for the next occurrence of the event, making them await-able, e.g. await q.drain(). (#​1586, #​1641)
• Calling callback(false) will cancel an async method, preventing further iteration and callback calls. This is useful for preventing memory leaks when you break out of an async flow by calling an outer callback. (#​1064, #​1542)
• during and doDuring have been removed, and instead whilst, doWhilst, until and doUntil now have asynchronous test functions. (#​850, #​1557)
• limits of less than 1 now cause an error to be thrown in queues and collection methods. (#​1249, #​1552)
• memoize no longer memoizes errors (#​1465, #​1466)
• applyEach/applyEachSeries have a simpler interface, to make them more easily type-able. It always returns a function that takes in a single callback argument. If that callback is omitted, a promise is returned, making it awaitable. (#​1228, #​1640)

New Features

• Async generators are now supported in all the Collection methods. (#​1560)
• Added cargoQueue, a queue with both concurrency and payload size parameters. (#​1567)
• Queue objects returned from queue now have a Symbol.iterator method, meaning they can be iterated over to inspect the current list of items in the queue. (#​1459, #​1556)
• A ESM-flavored async.mjs is included in the async package. This is described in the package.json "module" field, meaning it should be automatically used by Webpack and other compatible bundlers.

Bug fixes

• Better handle arbitrary error objects in asyncify (#​1568, #​1569)

Other

• Removed Lodash as a dependency (#​1283, #​1528)
• Miscellaneous docs fixes (#​1393, #​1501, #​1540, #​1543, #​1558, #​1563, #​1564, #​1579, #​1581)
• Miscellaneous test fixes (#​1538)

---

---

Configuration

📅 Schedule: Branch creation - Between 04:00 PM and 07:59 PM, Monday through Friday ( * 16-19 * * 1-5 ) in timezone Europe/London, Automerge - Between 02:00 PM and 06:59 PM, Monday through Thursday ( * 14-18 * * 1-4 ) in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-config-airbnb-base@14.2.1
npm error Found: eslint@9.39.3
npm error node_modules/eslint
npm error   dev eslint@"9.39.3" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.9.1
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.8.0" from eslint@9.39.3
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^5.16.0 || ^6.8.0 || ^7.2.0" from eslint-config-airbnb-base@14.2.1
npm error node_modules/eslint-config-airbnb-base
npm error   dev eslint-config-airbnb-base@"^14.0.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@7.32.0
npm error node_modules/eslint
npm error   peer eslint@"^5.16.0 || ^6.8.0 || ^7.2.0" from eslint-config-airbnb-base@14.2.1
npm error   node_modules/eslint-config-airbnb-base
npm error     dev eslint-config-airbnb-base@"^14.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-28T02_56_43_364Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-28T02_56_43_364Z-debug-0.log