Repository navigation
chore(deps): move to go-utils v1.3.0 - #2
Merged
Merged
Conversation
v1.3.0 rewrote the logger in go-utils. confy uses none of the API that was removed, so this is a version bump with no code changes: all three packages build and test clean against it. Worth knowing that v1.3.0 removed exported symbols despite being a minor version, so `go get -u` picks it up without warning. Repositories that used ZapField, Object, Array, ValidateField, SanitizeFields, FieldMap, MergeFields, BeautifulLogger, FormatConfig, NewDevelopmentLoggerWithLevel or FieldsToZap need code changes. confy did not. Logging output also now picks its own format: a terminal gets aligned coloured columns, anything else gets JSON, and FORGE_LOG_FORMAT overrides both.
juicycleff
added a commit
that referenced
this pull request
Sep 6, 2026
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.
go-utils v1.3.0 rewrote its logger. confy uses none of the API that was
removed, so this is a version bump with no code changes. All three packages
build and test clean against it.
Worth knowing for other repos: v1.3.0 removed exported symbols despite shipping
as a minor version, so
go get -upicks it up without warning. Anythingusing
ZapField,Object,Array,ValidateField,SanitizeFields,FieldMap,MergeFields,BeautifulLogger,FormatConfig,NewDevelopmentLoggerWithLevelorFieldsToZapneeds code changes first.confy used none of them.
Logging output also now selects its own format: a terminal gets aligned
coloured columns, anything else gets JSON, and
FORGE_LOG_FORMAToverridesboth.