build(deps): bump golang to 1.27.0

[slack-cli-releaser]

Automatic update to the latest release of Go

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.19%. Comparing base (b589377) to head (e210cca).
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #644      +/-   ##
==========================================
+ Coverage   72.59%   78.19%   +5.60%     
==========================================
  Files         239      239              
  Lines       20228    18135    -2093     
==========================================
- Hits        14684    14181     -503     
+ Misses       4274     3954     -320     
+ Partials     1270        0    -1270     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[zimeg]

The "Unmarshal Error" case in Test_HookScript_UnmarshalJSON now expecting three blank commands is fallout from Go 1.27 rewiring encoding/json onto the v2 implementation. From the Go 1.27 release notes, under "New encoding/json/v2 and encoding/json/jsontext packages":

The encoding/json package is now backed by the v2 implementation. Marshaling and unmarshaling behavior is preserved, but the exact text of error messages may differ. The package also gains a number of new Options that can configure v2 to operate with v1 semantics to avoid requiring a full migration to the new API. The v1 API will continue to be supported and users are not required to migrate.

For json.Unmarshal([]byte("[1, 2, 3]"), &hookScripts): the decoder walks the JSON array and grows the []HookScript slice one element at a time, calling HookScript.UnmarshalJSON per element. Each element (1, 2, 3) is a number, so the inner json.Unmarshal(data, &cmd) into a string returns a *json.UnmarshalTypeError before s.Command is assigned — leaving each element at its zero value {Command: ""}. The v2 decoder leaves the slice grown to all three positions when it errors, so the residual state is three blank entries, not one. Hence the expectation change from {{Command: ""}} → {{Command: ""}, {Command: ""}, {Command: ""}}. The returned error type (*json.UnmarshalTypeError) is unchanged.

Unrelated nit, pre-existing (not from this PR): require.IsType(t, err, tc.expectedErrorType) has the args reversed — testify's signature is IsType(t, expectedType, object), so it should be require.IsType(t, tc.expectedErrorType, err). Passes either way when they match, but a mismatch would print an inverted message.

[zimeg]

🚀 LGTM! Thanks @dependabot!

[zimeg]

⭐ praise: Nice to find this included with the above dependencies!

[zimeg]

🗃️ note: Here's the aforementioned change to tests.

🔗 https://go.dev/doc/go1.27