chore(deps): bump go.uber.org/zap from 1.27.1 to 1.28.0 in /backend#254
chore(deps): bump go.uber.org/zap from 1.27.1 to 1.28.0 in /backend#254dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [go.uber.org/zap](https://github.com/uber-go/zap) from 1.27.1 to 1.28.0. - [Release notes](https://github.com/uber-go/zap/releases) - [Changelog](https://github.com/uber-go/zap/blob/master/CHANGELOG.md) - [Commits](uber-go/zap@v1.27.1...v1.28.0) --- updated-dependencies: - dependency-name: go.uber.org/zap dependency-version: 1.28.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Greptile SummaryThis PR bumps Confidence Score: 5/5Safe to merge — minor version bump with only additive changes and no breaking API modifications. This is a routine dependency bump with a clean minor version increment. The single enhancement is purely additive (a new hook API), and the new transitive dep (go.yaml.in/yaml/v3) is the officially maintained successor to gopkg.in/yaml.v3. No security, logic, or compatibility concerns. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[backend/go.mod] -->|requires| B[go.uber.org/zap v1.28.0]
B -->|transitive dep| C[go.yaml.in/yaml/v3 v3.0.4]
B -->|replaces| D[go.uber.org/zap v1.27.1]
D -->|had transitive dep| E[gopkg.in/yaml.v3 - archived]
C -->|officially maintained successor of| E
Reviews (1): Last reviewed commit: "chore(deps): bump go.uber.org/zap from 1..." | Re-trigger Greptile |
Bumps go.uber.org/zap from 1.27.1 to 1.28.0.
Release notes
Sourced from go.uber.org/zap's releases.
Changelog
Sourced from go.uber.org/zap's changelog.
Commits
5b81b37release v1.28.0 (#1547)0ab0d5azapcore: Add PreWriteHook for transforming entries before write (#1534)d278c59[chore] CI: test on Go 1.26 (#1535)16fb16bchore(dep): replace archived gopkg.in/yaml.v3 with officially maintained go.y...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)