Skip to content

chore: upgrade to Go 1.26.4#222

Merged
EnriqueL8 merged 1 commit into
hyperledger-firefly:mainfrom
dan-r:chore/upgrade-go-1.26
Jun 26, 2026
Merged

chore: upgrade to Go 1.26.4#222
EnriqueL8 merged 1 commit into
hyperledger-firefly:mainfrom
dan-r:chore/upgrade-go-1.26

Conversation

@dan-r

@dan-r dan-r commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Updates common to Go 1.26.4.

  • go.mod go directive 1.23.01.26.4
  • CI go-version 1.231.26.4
  • Fix two non-constant format strings in tests that Go 1.26's vet now rejects (pkg/fswatcher/fswatcher_test.go, pkg/i18n/errors_test.go)

golangci-lint (v1.64.8) and all tests pass on Go 1.26.4. Note: bumping the module go directive requires downstream consumers of hyperledger-firefly/common to build with Go 1.26.4+.

@dan-r dan-r requested a review from a team as a code owner June 26, 2026 09:21
Comment thread go.mod Outdated
module github.com/hyperledger-firefly/common

go 1.23.0
go 1.26.0

@EnriqueL8 EnriqueL8 Jun 26, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

latest is 1.26.4 - can you upgrade to that please

Signed-off-by: Daniel Raper <daniel.raper@kaleido.io>
@dan-r dan-r force-pushed the chore/upgrade-go-1.26 branch from 056f5ac to 9ed41dd Compare June 26, 2026 12:28
@dan-r dan-r changed the title chore: upgrade to Go 1.26 chore: upgrade to Go 1.26.4 Jun 26, 2026

@EnriqueL8 EnriqueL8 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to put in the release notes that this completely breaking and that if anyone upgrade to the new version of common they will break

@EnriqueL8 EnriqueL8 merged commit fcbde81 into hyperledger-firefly:main Jun 26, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants