chore: Bump github.com/go-openapi/swag/jsonname from 0.26.1 to 0.27.0 in /cfn-resources#1680
Conversation
Bumps [github.com/go-openapi/swag/jsonname](https://github.com/go-openapi/swag) from 0.26.1 to 0.27.0. - [Release notes](https://github.com/go-openapi/swag/releases) - [Commits](go-openapi/swag@v0.26.1...v0.27.0) --- updated-dependencies: - dependency-name: github.com/go-openapi/swag/jsonname dependency-version: 0.27.0 dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
🤖 Augment PR SummarySummary: Updates the Go module dependencies for 🤖 Was this summary useful? React with 👍 or 👎 |
| github.com/davecgh/go-spew v1.1.1 // indirect | ||
| github.com/go-openapi/jsonpointer v0.23.1 // indirect | ||
| github.com/go-openapi/swag/jsonname v0.26.1 // indirect | ||
| github.com/go-openapi/jsonpointer v0.24.0 // indirect |
There was a problem hiding this comment.
PR title/description says this bumps github.com/go-openapi/swag/jsonname to v0.27.0, but go.mod instead removes swag/jsonname and bumps github.com/go-openapi/jsonpointer to v0.24.0. Can you confirm this is intentional (e.g., due to upstream deprecation/move) and that the resulting module graph ends up on the expected replacement version?
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
Bumps github.com/go-openapi/swag/jsonname from 0.26.1 to 0.27.0.
Release notes
Sourced from github.com/go-openapi/swag/jsonname's releases.
... (truncated)
Commits
4f9e718chore: prepare release v0.27.0014eae7chore: deprecated the jsonname module (moved to jsonpointer) (#216)d4bd1affeat: factory for generic sync.Pool usage, with safety test mode. (#215)23df065build(deps): bump the go-openapi-dependencies group across 15 directories wit...ce8f066ci: post README announcements to discord + bump ci-workflows to v0.4.0 (#213)ea59449chore(ci): run contributors workflow monthly instead of weekly (#212)b623b89build(deps): bump go-openapi/ci-workflows/.github/workflows/monitor-bot-pr.yml3eac5b8doc: updated contributors file95a4653build(deps): bump the development-dependencies group with 8 updatesDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)