James version causes renovate bot issue
See original GitHub issueSo this one is kind of interesting…
For some quick context, we installed renovate bot in our repo which contains the apollo client beta and we saw this upgrade from it:
It wants to upgrade to the james version!
Intended outcome:
It should match the latest tag on npm which is 3.0.0-beta.43
at the time of this writing.
Actual outcome:
My guess is the renovate uses the semver package and according to that, the james
version is the latest!
I don’t really know how to go about this. I see that this repo also uses renovate bot so maybe you know a solution. Maybe a possible approach is to unpublish or deprecate that version?? 😅
Thanks a bunch! ❤️
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Automatic Dependency Updates with renovate - GitLab.org
Bots like renovate or dependabot try to solve this by creating a new MR as soon as a new version of a dependency...
Read more >Troubleshooting - Renovate Docs
Learn how to troubleshoot problems with Renovate, where to find the logging output, ... Renovate only makes logs for the last 3 days...
Read more >How to Keep Your App Dependencies Up-To-Date?
One aspect of software development is often overlooked: maintaining dependencies. It raises two huge issues: security and performance, ...
Read more >chevrotain-parser/Lobby - Gitter
I have a version that is a token Version that is a prefix of IPv4. is this ... on website with certain content...
Read more >Updatebot - Jenkins Plugins
... Releases; Issues; Dependencies. This plugin makes it easy to upgrade downstream projects when you release a new version via UpdateBot ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is definitely annoying 🙁. The good news is we’re publishing the AC3 RC sometime between tomorrow and Sunday, so at least switching to the RC will get past this. Instead of figuring out a way around this (since we can’t unpublish the infamous
James
package), and since the RC is imminent, we’re probably going to leave this as is.This issue was resolved - thanks!