馃Ч Cleanup CI / CD / build issues and prepare for release of v0.15.1 馃殌 #403
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
tlBaseVersion
from1.15
to0.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.4
to0.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