commit-status-updater
commit-status-updater copied to clipboard
build(deps): bump cacheable-request from 10.2.1 to 10.2.7
Bumps cacheable-request from 10.2.1 to 10.2.7.
Release notes
Sourced from cacheable-request's releases.
v10.2.6
Fix for memory leak on Listeners
The listener was not being removed on
responseand just error but new handlers were being added causing a memory leak.line 220 in src/index.ts was modified to remove the listener on response also
if (this.cache instanceof Keyv) { const cachek = this.cache; cachek.once('error', errorHandler); ee.on('error', () => cachek.removeListener('error', errorHandler)); ee.on('response', () => cachek.removeListener('error', errorHandler)); }What's Changed
- upgrading jest and components to latest by
@jaredwrayin jaredwray/cacheable-request#220- upgrading
@types/jestto 29.2.6 by@jaredwrayin jaredwray/cacheable-request#221- fixing listener memory leak - issue #222 by
@jaredwrayin jaredwray/cacheable-request#223Full Changelog: https://github.com/jaredwray/cacheable-request/compare/v10.2.5...v10.2.6
v10.2.5
Types definition issue with http-cache-sematics as that type definition needs to be in dependencies. Thanks
@Maxim-MazurokWhat's Changed
- Move
@types/http-cache-semanticsfrom dev to deps by@Maxim-Mazurokin jaredwray/cacheable-request#219Full Changelog: https://github.com/jaredwray/cacheable-request/compare/v10.2.4...v10.2.5
v10.2.4
Minor updates with one exception is that we removed
@types/http-cache-semanticsfrom the main dependencies as it does not look to be needed.What's Changed
- upgrading typescript to 4.9.4 by
@jaredwrayin jaredwray/cacheable-request#214- upgrading jest types and eslint for jest to latest by
@jaredwrayin jaredwray/cacheable-request#215- upgrading sqlite3 to 5.1.4 by
@jaredwrayin jaredwray/cacheable-request#216- removing
@types/http-cache-semanticsfrom the dependencies and moving… by@jaredwrayin jaredwray/cacheable-request#217Full Changelog: https://github.com/jaredwray/cacheable-request/compare/v10.2.3...v10.2.4
v10.2.3 Maintenance Release
Upgrading core modules in the system such as keyv and also a minor fix to an uncaught exception that we were seeing referenced here: sindresorhus/got#1925
Additional update is moving
normalize-urlto8.0.0which after testing it looks to not affect anything but will post the release notes here: https://github.com/sindresorhus/normalize-url/releases/tag/v8.0.0
... (truncated)
Commits
- See full diff in compare view
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
@dependabot[bot]: Invalid title for the PR, the title needs to be like:
refactor: this is a refactor commit=> if using semantic-release will trigger a patch releasefix: this is a fix commit=> if using semantic-release will trigger a patch releasefeat: this is a feature commit=> if using semantic-release will trigger a minor releasemajor: this is a major commit=> if using semantic-release will trigger a major releasedoc: this is a doc commit=> if using semantic-release won't trigger a new releasebuild: this is a build commit=> if using semantic-release will trigger a patch releaseno-release: this is a no-release commit=> won't trigger a new release
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign givanov for approval by writing /assign @givanov in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/hold
Hi @dependabot[bot]. Thanks for your PR.
I'm waiting for a ouzi-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/hold cancel