Repository navigation
chore: update Go setup and govern Node type majors - #220
Merged
Merged
Conversation
This was referenced Oct 27, 2026
Closed
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
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.
Update the pinned Go setup action to v7.0.0 across CI, editor publishing, Pages, and npm release workflows, retaining Go 1.27.3 and the existing cache settings. The official v7 action still uses the Node 24 runner runtime and preserves the inputs used here.
Keep Node 24 declarations as the development baseline and require an explicit review for type-major upgrades against the supported runtime matrix. Dependabot continues proposing updates within that major. Correct the maintainer host-test documentation to the actual pinned VS Code 1.140.0.
This supersedes the action-only update in #215 and records the policy behind declining the automatic Node 26 type-major update in #206. No package behavior, versions, or release tags change.
Validation: focused Biome and whitespace checks passed. Required CI verifies the pinned action through real builds, database consumers, and editor host checks on Linux, macOS, and Windows.