search

ipfs-shipyard / pinning-service-compliance

This repo checks the compliance of IPFS Pinning Services against the pinning spec
https://ipfs-shipyard.github.io/pinning-service-compliance/
Other
14 stars 10 forks source link

chore(deps): bump ipfs from 0.63.3 to 0.63.5 #139

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps ipfs from 0.63.3 to 0.63.5.

Release notes

Sourced from ipfs's releases.

ipfs ipfs-v0.63.5

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • ipfs-cli bumped from ^0.13.4 to ^0.13.5
      • ipfs-core bumped from ^0.15.3 to ^0.15.4
    • devDependencies
      • interface-ipfs-core bumped from ^0.155.1 to ^0.155.2
      • ipfs-client bumped from ^0.8.2 to ^0.8.3
      • ipfs-http-client bumped from ^57.0.2 to ^57.0.3

ipfs ipfs-v0.63.4

Bug Fixes

  • use default ws filters instead of connecting to everything (#4142) (7be50bd), closes #4141

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • ipfs-cli bumped from ^0.13.3 to ^0.13.4
      • ipfs-core bumped from ^0.15.2 to ^0.15.3
    • devDependencies
      • interface-ipfs-core bumped from ^0.155.0 to ^0.155.1
      • ipfs-client bumped from ^0.8.1 to ^0.8.2
      • ipfs-core-types bumped from ^0.11.0 to ^0.11.1
      • ipfs-http-client bumped from ^57.0.1 to ^57.0.2
Commits


Dependabot compatibility score

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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
lidel commented 2 years ago

I already regret merging #144 :skull:

@SgtPooki @hacdias is there any way to exclude dependabot from asking team for a review or notifications?

If i get dependabot noise from multiplerepos, my https://github.com/notifications?query=reason%3Areview-requested will become useless (afaik no way to filter it out).

hacdias commented 2 years ago

@lidel @SgtPooki oh, ugh. I just triggered another one by mistake on another @dependabot PR. I took the freedom to merge some of the dependabot PRs in this repo for patch or minor versions that passed tests, which created a cascade effect as you can see on your notifications. Sorry for that. Regarding the present issue of the notifications, we could:

  1. Try to exclude PRs that only change package.json and package-lock.json via the CODEOWNERS file ^1. I'm not exactly sure if it's possible to ignore specific files.
  2. Reduce @dependabot PRs by changing the options to security updates only and limiting the amount of open PRs per repository ^2

--

Not only do we get a notification from @dependabot, but also from @github-actions indicating the PR was included in the release, which can be useful, but not necessarily for @dependabot PRs.

github-actions[bot] commented 2 years ago

:tada: This PR is included in version 1.1.6 :tada:

The release is available on:

Your semantic-release bot :package::rocket: