chore(deps): bump github.com/buger/jsonparser from 1.1.1 to 1.1.2 in the go_modules group across 1 directory#1790
Conversation
|
A single node development cluster (infra-pr-1790) was allocated in production infra for this PR. CI will attempt to deploy 🔌 You can connect to this cluster with: 🛠️ And pull infractl from the deployed dev infra-server with: 🚲 You can then use the dev infra instance e.g.: Further Development☕ If you make changes, you can commit and push and CI will take care of updating the development cluster. 🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with: LogsLogs for the development infra depending on your @redhat.com authuser: Or: |
Bumps the go_modules group with 1 update in the / directory: [github.com/buger/jsonparser](https://github.com/buger/jsonparser). Updates `github.com/buger/jsonparser` from 1.1.1 to 1.1.2 - [Release notes](https://github.com/buger/jsonparser/releases) - [Commits](buger/jsonparser@v1.1.1...v1.1.2) --- updated-dependencies: - dependency-name: github.com/buger/jsonparser dependency-version: 1.1.2 dependency-type: direct:production dependency-group: go_modules ... Signed-off-by: dependabot[bot] <support@github.com>
38cad7d to
c4bb279
Compare
Bumps the go_modules group with 1 update in the / directory: github.com/buger/jsonparser.
Updates
github.com/buger/jsonparserfrom 1.1.1 to 1.1.2Release notes
Sourced from github.com/buger/jsonparser's releases.
Commits
a69e7e0Merge pull request #276 from dbarrosop/masterd3eacc0fix: prevent panic on negative slice index in Delete with malformed JSON (GO-...61b32cfMerge pull request #241 from unxcepted/master2181e83Merge pull request #244 from ScaleChamp/patch-21510b51Added latest versions of go to tests6fc2e48fix: eachkey allocationa6f867eMerge pull request #239 from AdamKorcz/cifuzz1cbc01fdFuzzing: Add CIFuzzdc92d69Merge pull request #228 from jonomacd/null-handling2d9d634Merge pull request #231 from carsonip/fix-parseint-overflow-checkDependabot 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.