Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency debounce-fn to v5 #137

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 15, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
debounce-fn ^4.0.0 -> ^5.0.0 age adoption passing confidence

Release Notes

sindresorhus/debounce-fn

v5.0.0

Compare Source

Breaking
Improvements

Renovate configuration

📅 Schedule: "before 3am on Monday" (UTC).

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

♻️ Rebasing: Whenever PR becomes conflicted, 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 has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/debounce-fn-5.x branch from 003016e to e4a1cd1 Compare March 15, 2021 09:48
@erezrokah
Copy link

Can't update until we drop support for Node.js 10

@erezrokah erezrokah closed this Mar 15, 2021
@erezrokah erezrokah deleted the renovate/debounce-fn-5.x branch March 15, 2021 10:13
@renovate
Copy link
Contributor Author

renovate bot commented Mar 15, 2021

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 5.x releases. However, if you upgrade to 5.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

@lindsaylevine
Copy link

@erezrokah when would be an appropriate time to drop support for node 10?

serhalp pushed a commit that referenced this pull request Apr 5, 2024
* fix: ensure cdn cache control only for get and head

* test: pass requests in tests and add HEAD and POST test cases

---------

Co-authored-by: Michal Piechowiak <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants