Included the upgrade to sbt-circe-org out of concern for an out-dated release process, however, the issue was a simple fix of changing tlBaseVersion from 1.15 to 0.15 (which was my bad 🤦 )
A 1.15.0 artifact was released which I cannot undo. Instead I am going to mark note it in the releases and suggest people upgrade to 0.15.1 which will contain all of these changes.
I'm not really sure how to deal with all of the damage downstream from Scala Steward upgrades... Is there a way to mark a release as broken?
About this PR
Included the upgrade to sbt-circe-org out of concern for an out-dated release process, however, the issue was a simple fix of changing
tlBaseVersionfrom1.15to0.15(which was my bad 🤦 )A 1.15.0 artifact was released which I cannot undo. Instead I am going to mark note it in the releases and suggest people upgrade to 0.15.1 which will contain all of these changes.
I'm not really sure how to deal with all of the damage downstream from Scala Steward upgrades... Is there a way to mark a release as broken?
📦 Updates io.circe:sbt-circe-org from
0.1.4to0.2.1📜 GitHub Release Notes - Version Diff
labels: sbt-plugin-update, early-semver-major, semver-spec-minor, version-scheme:early-semver, commit-count:n:2