bittorrent-tracker@7.3.1 breaks build 🚨

[greenkeeperio-bot]

Hello 👋

🚨🚨🚨

bittorrent-tracker just published its new version 7.3.1, which is covered by your current version range. After updating it in your project the build went from success to failure.

This means your software is now malfunctioning, because of this update. Use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴

---

The new version differs by 45 commits .

• 7ad6837 7.3.1
• caa6d45 Merge pull request #119 from alxhotel/master
• 4142e8c Remove info_hash from failure reason
• 00e84cb readme
• 79898ab 7.3.0
• 3485f22 update documentation for #107
• 48d1f38 test/server: use common.createServer
• 4207d80 test/scrape: use common.createServer
• 3342c20 test: add test for ws tracker for filter tests
• 5dcdf9c ws tracker: don't crash with filter function
• 2abab6c test: test http/ws trackers in magnet test
• fe4a672 test: make large torrent test more thorough
• 012b315 test: add large torrent tests for ws tracker
• e15125c test: add tests forgetAnnounceOpts(#107)
• 7893d5c remove failing ws test

There are 45 commits in total. See the full diff.

---

This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

_{Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡️}

[feross]

npm registry fluke

[solderzzc]

Can not install webtorrent due to the bittorrent-tracker-7.3.1 for webtorrent-app.

$ npm install \ npm ERR! fetch failed https://registry.npmjs.org/bittorrent-tracker/-/bittorrent-tracker-7.3.1.tgz npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 504

[feross]

looks like there was a bad publish - republished as 7.3.2 last week and this was fixed

[lock]

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.