Skip to content

Conversation

@bufdev
Copy link
Member

@bufdev bufdev commented Dec 3, 2025

Quick and dirty.

Before:

Failure: decode buf.yaml: invalid as version v2: could not unmarshal as YAML: yaml: unmarshal errors:
  line 14: field foo not found in type bufconfig.externalBufYAMLFileV2
  line 15: field baz not found in type bufconfig.externalBufYAMLFileV2

After:

Failure: decode buf.yaml: yaml: unmarshal errors:
  line 14: field foo not found
  line 15: field baz not found

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedDec 4, 2025, 5:50 PM

@bufdev
Copy link
Member Author

bufdev commented Dec 3, 2025

Error has to do with the fact that 1.25.4 is being used for some reason (GHA hasn't updated to 1.25.5 maybe? cache?) and our builds don't appear to be deterministic in some way w.r.t. golangci-lint? The windows failure looks to be flaky. @emcfarlane can you take a look?

@emcfarlane
Copy link
Contributor

Added check-latest so the lastest patch is fetched. This avoids using the local cache and golangci-lint failing on the older version issue: #4202

@bufdev bufdev merged commit 665e37d into main Dec 4, 2025
10 checks passed
@bufdev bufdev deleted the yaml-error-improvement branch December 4, 2025 23:04
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.

3 participants