Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Release v2.1.0 final to unlock Scala Center's SCP-026
See original GitHub issueHello,
Coursier v2.1.0-M1 was released 2 months ago, with an M2 a couple weeks later. Since then, there does not appear to have been any changes in the master branch, and it also seems that no critical regression was reported.
May I kindly ask to release Coursier v2.1.0 final?
As long as there is no final release, we cannot merge the following PRs in coursier/apps:
Merging those PRs is required to move forward with the Scala Center Recommendation SCP-026, which has therefore been blocked.
Using the milestone is, in theory, possible. But you need to create your own channel with the changes brought by the two PRs above. This is not something we can recommend to newcomers.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I might cut
2.1.0final then (and probably start using2.2.0milestone versions soon after).For what it’s worth, I’d still recommend doing a stable release. There are places that use coursier that have strict policies on versions that they can use. For example at the client I work at we aren’t allowed to use non-stable versions, meaning we can’t use anything newer than 2.0.16 because everything else is seen as a non-stable version. Please reconsider this. I know “it’s just a number”, but that doesn’t work in a ton of enterprise-type companies. If it doesn’t matter to you like you say, then maybe just release a new stable version?