-
Notifications
You must be signed in to change notification settings - Fork 608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(deps): bump github.com/goccy/go-yaml from 1.13.6 to 1.15.3 #2949
build(deps): bump github.com/goccy/go-yaml from 1.13.6 to 1.15.3 #2949
Conversation
Bumps [github.com/goccy/go-yaml](https://github.com/goccy/go-yaml) from 1.13.6 to 1.15.2. - [Release notes](https://github.com/goccy/go-yaml/releases) - [Changelog](https://github.com/goccy/go-yaml/blob/master/CHANGELOG.md) - [Commits](goccy/go-yaml@v1.13.6...v1.15.2) --- updated-dependencies: - dependency-name: github.com/goccy/go-yaml dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Since https://github.com/goccy/go-yaml/releases/tag/v1.14.0 Signed-off-by: Jan Dubois <[email protected]>
Signed-off-by: Jan Dubois <[email protected]>
Turned into a draft because it has 2 test failures (I'll report upstream):
|
The load_test.go error has a changed error message. The validate_test.go was using incorrect YAML that wasn't detected before. Signed-off-by: Jan Dubois <[email protected]>
I've fixed the failures. One was a change in the error message, so I had to adapt the assert. And the other was a bug in out test that wasn't detected before. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since I added commits to the PR I think it needs another approval from another maintainer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jandubois
@jandubois: I've added a commit to fix the incompatibilities (
yaml.DisallowDuplicateKey
no longer exists, and is the default now), and bumped to the latest 1.15.3 release.I've also adjusted for 2 test failures:
Bumps github.com/goccy/go-yaml from 1.13.6 to 1.15.2.
Release notes
Sourced from github.com/goccy/go-yaml's releases.
... (truncated)
Commits
3584ab7
guard stack overflow at decoding (#549)23c9234
add fuzzing test (#548)639f493
inventorying test cases (#547)3399084
Fix parser (#546)deb129a
Refactor parser (#545)ff5d41f
Fix parser by using yaml-test-suite (#542)c312882
Add YAML Test Suite (#541)69159b3
clear pathMap keys (#539)d7847db
fix parsing of tab character in double-quote (#538)8b2110b
fix invalid token error (#536)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)