Build(deps): bump express-rate-limit from 8.6.0 to 8.6.2 - #28
Build(deps): bump express-rate-limit from 8.6.0 to 8.6.2#28dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [express-rate-limit](https://github.com/express-rate-limit/express-rate-limit) from 8.6.0 to 8.6.2. - [Release notes](https://github.com/express-rate-limit/express-rate-limit/releases) - [Commits](express-rate-limit/express-rate-limit@v8.6.0...v8.6.2) --- updated-dependencies: - dependency-name: express-rate-limit dependency-version: 8.6.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Closes Dependabot alerts #23, #24, #26 (ip-address) and #28 (js-yaml). - ip-address 10.2.0 -> 10.5.0 (runtime, transitive via express-rate-limit): leading-zero octet decoding (#26, high), IPv4-mapped/NAT64 misclassification (#23), CIDR suffix suppressing special-use classification (#24) - js-yaml 3.15.0 -> 3.15.1 (dev, transitive via @istanbuljs/load-nyc-config): quadratic CPU in !!omap resolution (#28, high) - brace-expansion -> 1.1.18/2.1.4/5.0.9, clearing the auto-dismissed #25/#27 - express-rate-limit 8.6.0 -> 8.6.2 and playwright 1.61.1 -> 1.62.1, folding in the pending Dependabot PRs Playwright 1.62 dropped Debian 11, which is what failed the CI build on the Playwright bump PR, so both images move from node:26-bullseye to node:26-bookworm. Add .dockerignore: without it `COPY . .` copied a host node_modules over the tree installed by `npm ci`, so the container's Playwright could disagree with the browser revision baked into the image and every browser-launching integration test failed with a 500. Bound PlaywrightManager.close() at 10s per resource and drop handles in a finally. Unbounded closes were hanging /test/cleanup on slow runners, which intermittently killed the keepalive integration hooks at their 60s limit, and would also block the SIGTERM/SIGINT graceful-shutdown path. Covered by tests/unit/playwright-shutdown.test.js. 136/136 tests pass in the test container; npm audit reports 0 vulnerabilities.
|
Superseded by #29, which includes express-rate-limit 8.6.2. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps express-rate-limit from 8.6.0 to 8.6.2.
Release notes
Sourced from express-rate-limit's releases.
Commits
c416f788.6.2defb334v8.6.2 changelog7dd82cffix: key IPv4-in-IPv6 addresses by range, not notation (#667)4e23dbbchore(deps): bump ip-address from 10.3.1 to 10.4.0 (#666)607ef1fchore(deps): bump ip-address from 10.2.0 to 10.3.1 (#664)d2370f6chore(deps-dev): bump the development-dependencies group with 5 updates (#663)c7fced58.6.1b21110echore: deprecate millisecond-based time constants (#662)fad3d85chore(deps-dev): bump the development-dependencies group with 4 updates (#660)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)