Repository navigation
fix(deps): release the go-utils v1.3.0 bump - #3
Merged
Merged
Conversation
The bump itself landed in #2, but that PR was titled `chore(deps):` and squash-merged, so the commit subject on main is a chore. This repository's .releaserc.json maps chore to no release, so the run finished green and produced no tag, leaving v1.0.2 pointing at the old dependency. Titling a dependency bump as a chore was the wrong call on my part. Renovate and Dependabot both use fix(deps) for production dependency updates precisely so that they ship, and this one should: consumers of confy pulling v1.0.2 still get go-utils v1.2.2 and the old logger. No code change. The bump is already on main; this only carries a subject semantic-release can act on. What consumers get: go-utils v1.3.0, whose logger picks its own output format. A terminal gets aligned coloured columns, anything else gets JSON, and FORGE_LOG_FORMAT overrides both.
Contributor
|
🎉 This PR is included in version 1.0.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
#2 bumped go-utils to v1.3.0 but did not release, so
v1.0.2still points atthe old dependency.
The cause is the PR title. #2 was titled
chore(deps): …and squash-merged, sothat became the commit subject on
main, and.releaserc.jsonmapschoreto"release": false. The release workflow ran, finished green, and produced notag.
That was my mistake in titling #2. Renovate and Dependabot both use
fix(deps):for production dependency updates specifically so they ship, andthis one should ship: anyone on
v1.0.2still resolves go-utils v1.2.2.This PR has no code change. The bump is already on
main. It only supplies asubject semantic-release can act on, which takes confy to v1.0.3.
Keep this PR title as the squash subject when merging — it is what the
release reads.