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

chore(deps): update dependency localforage to v1.10.0 #153

Open
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 27, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
localforage 1.7.3 -> 1.10.0 age adoption passing confidence

Release Notes

localForage/localForage

v1.10.0

Compare Source

  • Avoid uncaught error in dropInstance. You can now catch errors thrown by dropInstance, see #​807.

v1.9.0

Compare Source

  • Fixed TypeScript definition for getItem. It now notes that getItem can return null, so this change may cause TypeScript code that didn't account for null values to fail. See #​980.

v1.8.1

Compare Source

  • Reverted the ESM/module field change in #​940, which broke many builds. See: #​979. Sorry about that! 😓

v1.8.0

Compare Source

  • No changes to code, but added a module field in package.json for better ESM support. See: #​940.

v1.7.4

Compare Source

  • Use openKeyCursor instead of openCursor for key() retrieval. Props to @​MeMark2 for the fix, and thanks to @​lincolnthree and @​f for additional testing!

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title fix(deps): update dependency localforage to v1.9.0 chore(deps): update dependency localforage to v1.9.0 Jan 5, 2021
@renovate renovate bot force-pushed the renovate/localforage-1.x branch from ea59fad to c028c5f Compare October 20, 2021 06:50
@renovate renovate bot changed the title chore(deps): update dependency localforage to v1.9.0 chore(deps): update dependency localforage to v1.10.0 Oct 20, 2021
@renovate
Copy link
Contributor Author

renovate bot commented Oct 20, 2021

⚠ 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 check 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 ERR! Linux 4.15.0-1050-aws
npm ERR! argv "/usr/local/node/14.18.1/bin/node" "/home/ubuntu/.npm-global/bin/npm" "install" "--package-lock-only" "--no-audit" "--ignore-scripts"
npm ERR! node v14.18.1
npm ERR! npm  v3.10.10

npm ERR! cb.apply is not a function
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/renovate/gh/FightForSub/ffs-zera/npm-debug.log

@renovate
Copy link
Contributor Author

renovate bot commented Mar 25, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants