Release problem with 0.9.24?
See original GitHub issueVersion 0.9.24
seems to be incompletely published:
➜ ~ cs complete org.creativescala:doodle_3:0.9.24
➜ ~ cs complete org.creativescala:doodle_3:0.9.2
➜ ~ cs complete org.creativescala:doodle_3:
➜ ~ cs complete org.creativescala:doodle_2.13
doodle_2.13
➜ ~ cs complete org.creativescala:doodle_2.13:
0.9.16
0.9.17
0.9.18
0.9.19
0.9.20
0.9.21
0.9.22
0.9.23
If I use Maven’s Central web UI then for this version I only see Scala JS artifacts
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
LightBurn 0.9.24 released - Comms issues for MacOS ...
This primarily affected Ruida and TopWisdom controllers, and was significantly worse on MacOS. This release includes a number of improvements ...
Read more >LightBurn - 0.9.24 has been released, fixing known issues...
0.9.24 has been released, fixing known issues with serial/USB connections on Ruida and TopWisdom controllers.
Read more >[openssl][0.9.24] Fail to build on hosts with openssl 1.1.1
Got the following failure: error: failed to run custom build command for `openssl ... It needs to be upgraded to openssl-sys last releases....
Read more >0.9.24 Release - Blog
This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled. The recommended fix...
Read more >0.9.24 Release Candidate 1
Hello again! There was a indeed a problem with the Windows package. A new version has been uploaded. No new version number. Windows...
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
Thanks for that suggestion. It seems to work. I’ve published 0.9.25.
Ah, this is something different than I expected.
After
++2.13.6
,rootJVM/update
is sufficient to reproduce the problem.I think you need to either:
commonSettings
inroot
libraryDependencies
incommonSettings
, handle that separatelyMaybe you could add the dependencies on cats-effect et al to
coreJVM
only, since the other projects depend on it? That’s how I would normally write it in the first place, actually.