Upgrade to Go 1.27, modernize code, and standardize CI badges - #16
Merged
Conversation
This was referenced Sep 11, 2026
markmnl
changed the title
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.
Require Go 1.27 and run CI on the latest 1.27 patch. Standardize the README badges as “Build & Test” and “Go 1.27+”, with build status scoped to
main. CI builds, runs race tests, and vets the module on pull requests and pushes tomain.Apply the reviewed results of two
go fix ./...passes with Go 1.27.1. Useany, slice and string helpers, and simplified loops. Remove the ineffectiveomitemptyoption on thetime.Timecredentials field; JSON output is preserved.Add the missing build/test workflow so the status badge reflects an actual check.
Validation after modernization on Go 1.27.1:
go build ./...,go test -race ./...,go vet ./..., and workflow linting pass.The coordinated stack passed all 15 integration tests during the version upgrade. Integration CI is rerunning against the modernized companion branches with
FMSG_CHALLENGE_MODE=ALWAYS.Companion stack PRs: fmsgd #46, fmsg-webapi #46, fmsgid #5, fmsg-docker #22.