Stuck on an issue?
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.
Thoughts on using sbt-ci-release?
See original GitHub issueI wonder if this was considered before? It would be quite useful as every merge to main will automatically publish a SNAPSHOT so users don’t need to wait for a release to use the latest version 😃
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
sbt-ci-release-early - Scaladex
Sbt plugin for fully automated releases, without SNAPSHOT and git sha's in the version. A remix of the best ideas from sbt-ci-release and...
Read more >Open sourcing release plugin `sbt-ci-release-early`
In essence, it allows you to fully automatically release a new version for every successful CI build. The resulting artifacts have normal ...
Read more >scalacenter/sbt-release-early - Gitter
With snapshots this is easy: S depends on a snapshot version of L and you configure CI to trigger the build of S...
Read more >sbt-sonatype: Blazingly Fast Release to Sonatype - Medium
If you are a maintainer of Scala OSS projects and have never tried sbt-sonatype 3.6 (or higher), your release process can be much...
Read more >So, what's wrong with SBT? - Haoyi's Programming Blog
SBT is the default build tool for the Scala programming community: you can build Scala using other tools, but the vast majority of...
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 Free
Top 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
Not at all, the more the merrier @armanbilge. Always good to get another opinion. 😄
I’ll add it to the list of things to do/look into. Tyrian is more framework than library, and I tend to roll everything forward in lock-step (for both Tyrian and Indigo). So as long as you’re doing that too when you upgrade versions, you’re probably fine, but automated checking certainly couldn’t hurt. 👍
A shout-out on a tooling podcast? …well now I’m going to be doubly-embarrassed about the ci setup… 😅 😆