build(deps): bump github.com/BurntSushi/toml from 1.2.1 to 1.6.0

[dependabot]

Bumps github.com/BurntSushi/toml from 1.2.1 to 1.6.0.

Release notes

Sourced from github.com/BurntSushi/toml's releases.

v1.6.0

TOML 1.1 is now enabled by default. The TOML changelog has an overview of changes: https://github.com/toml-lang/toml/blob/main/CHANGELOG.md

Also two small fixes:

• Encode large floats as exponent syntax so that round-tripping things like 5e+22 is correct.

• Using duplicate array keys would not give an error:

  arr = [1]
  arr = [2]
  

  This will now correctly give a "Key 'arr' has already been defined" error.

v1.5.0

Mostly some small bugfixes, with a few small new features:

• Add Position.Col, to mark the column an error occurred (#410)

• Print more detailed errors in the tomlv CLI.

• Ensure ParseError.Message is always set (#411)

• Allow custom string types as map keys (#414)

• Mark meta keys as decoded when using Unmarshaler interface (#426)

• Fix encoding when nested inline table ends with map (#438)

• Fix encoding of several layers of embedded structs (#430)

• Fix ErrorWithPosition panic when there is no newline in the TOML document (#433)

v1.4.0

This version requires Go 1.18

• Add toml.Marshal() (#405)

• Require 2-digit hour (#320)

• Wrap UnmarshalTOML() and UnmarshalText() return values in ParseError for position information (#398)

• Fix inline tables with dotted keys inside inline arrays (e.g. k=[{a.b=1}]) (#400)

v1.3.2

Fix reading BURNTSUSHI_TOML_110 again 😅 The fix for 1.3.1 caused a race issue with multiple decodes being run in parallel.

v1.3.1

This fixes two small bugs:

... (truncated)

Commits

• 5253492 Enable TOML 1.1 by default (#457)
• e954445 Reject duplicate arrays (#455)
• 6b16cbd Update toml-test test cases from upstream (#456)
• 011fa2b Ensure constant format strings in wf calls
• 4b439bf Remove itemNil
• a473c12 Add test for out of range float64
• b535ff8 Add some boring tests for lex.go
• 6011ef0 Remove unreachable condition in lexTableNameStart
• c8ca9e6 Remove unreachable condition
• 1121f81 Make tomlv read from stdin
• Additional commits viewable in compare view

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 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)

[kubesphere-prow]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kubesphere-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign redscholar for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud