🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of registry-auth-token.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Coverage remained the same at 77.778% when pulling dd8a40e6bcf311d6f171c6b9038419a9634a54ca on greenkeeper-registry-auth-token-3.3.1 into b0fb0e2c047329a84ddae1bf6c2a6ba476fde7cd on master.
Hello lovely humans,
registry-auth-token just published its new version 3.3.1.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of registry-auth-token. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 17 commits .
bc7fe19
3.3.1
d34ea32
Merge pull request #17 from destroyerofbuilds/fix/auth/legacy
6a2cb60
fix(auth): legacy token is basic auth
ea4b498
3.3.0
fd5f155
Update changelog [skip-ci]
effbbea
Use safe-buffer for consistent base64 encoding/decoding
27ff1e7
Change to standard style
4530c8e
Merge pull request #16 from zkochan/legacy-auth
d96d422
feat: support legacy auth token config key
1833b2a
3.2.0
0e1605f
Merge pull request #15 from zkochan/feat/config
31c1034
feat: allow to pass in the parsed npmrc from outside
1f325f0
3.1.2
3a91e0c
Merge pull request #11 from zkochan/master
4817785
fix: avoid infinite loop on invalid URL
There are 17 commits in total. See the full diff.