Skip to content

build(deps): bump github.com/nicksnyder/go-i18n/v2 from 2.5.1 to 2.6.1 - #24

Closed
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/go_modules/github.com/nicksnyder/go-i18n/v2-2.6.1
Closed

build(deps): bump github.com/nicksnyder/go-i18n/v2 from 2.5.1 to 2.6.1#24
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/go_modules/github.com/nicksnyder/go-i18n/v2-2.6.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 29, 2026

Copy link
Copy Markdown
Contributor

Bumps github.com/nicksnyder/go-i18n/v2 from 2.5.1 to 2.6.1.

Release notes

Sourced from github.com/nicksnyder/go-i18n/v2's releases.

v2.6.1

What's Changed

New Contributors

Full Changelog: nicksnyder/go-i18n@v2.6.0...v2.6.1

v2.6.0

Key changes

  • go-i18n extract will error if it finds a message ID that has been duplicated but contains different content.
  • Upgraded to CLDR v47 data
  • Minimum version of Go increased from 1.18 to 1.23.

All changes

New Contributors

Full Changelog: nicksnyder/go-i18n@v2.5.1...v2.6.0

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/nicksnyder/go-i18n/v2](https://github.com/nicksnyder/go-i18n) from 2.5.1 to 2.6.1.
- [Release notes](https://github.com/nicksnyder/go-i18n/releases)
- [Changelog](https://github.com/nicksnyder/go-i18n/blob/main/CHANGELOG.md)
- [Commits](nicksnyder/go-i18n@v2.5.1...v2.6.1)

---
updated-dependencies:
- dependency-name: github.com/nicksnyder/go-i18n/v2
  dependency-version: 2.6.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Aug 29, 2026
donislawdev added a commit that referenced this pull request Aug 31, 2026
…th it (#26)

Dependabot proposed the version bump in #24. This carries it on top of the
current main and does the two things the bot cannot: name the new module, and
say what its licence is.

The bump is not just a version. Taking github.com/nicksnyder/go-i18n/v2 from
2.5.1 to 2.6.1 pulls go.yaml.in/yaml/v3 into the module graph - the same yaml
library as gopkg.in/yaml.v3, under the module path that project has moved to.
Both are in the graph now, because other modules still ask for the old path.
That is the case .github/dependabot.yml warns about in its second paragraph,
and it is why a gomod pull request goes red until somebody looks.

Read from the pinned module rather than off a web page, as immutable rule 11
asks: go.yaml.in/yaml/v3 carries MIT and Apache-2.0 together - the files ported
from libyaml keep the MIT of the original C, the rest is Apache-2.0 with a
NOTICE from Canonical - and both are one way compatible with GPL-3.0. go-i18n
itself is still MIT with the same copyright line as before.

The new module is in the GRAPH and linked into NEITHER binary, measured rather
than assumed. So it belongs in the list this workflow pins and not in the
notices, which track what actually ships. The notices do move for go-i18n
itself, which the window links, and its version there now says 2.6.1.

D11 holds: every pinned hash is unchanged, so this is tidying rather than a
major version question. Checked the way dependabot.yml asks for - the full
suite locally, not a green tick.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
@dependabot @github

dependabot Bot commented on behalf of github Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/go_modules/github.com/nicksnyder/go-i18n/v2-2.6.1 branch August 31, 2026 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant