chore(deps): bump github.com/google/go-jsonnet from 0.21.0 to 0.22.0

[dependabot]

Bumps github.com/google/go-jsonnet from 0.21.0 to 0.22.0.

Release notes

Sourced from github.com/google/go-jsonnet's releases.

v0.22.0

The Python module can be found at https://pypi.org/project/gojsonnet/0.22.0/

What's Changed (since v0.21.0)

• Updates since Release Candidate 1

  • Apply nesting depth limit when manifesting objects to TOML, YAML, or JSON (#866)
  • Publish pre-built Python wheels (binary packages) for Linux aarch64 (ARM) (#865)

• Possibly breaking changes

  • Required Go version is increased to 1.24 (https://go.dev/doc/devel/release#go1.24.0) (#850)
  • When evaluating in --multi --string mode, output files now have an extra (trailing) newline added. If you do not want this, you can use --no-trailing-newline. (#819, #843)
  • Output files in --multi mode are restricted to the specified output directory (and subdirectories)
  • Pre-built binary archive names have changed (#848, #814)

• Language changes, new features, etc

  • Numbers in Jsonnet code can now be written with underscore used to separate groups of digits (e.g., 1_500_000) (#760)
  • New function std.isNull (#806)
  • Bitwise operation arguments are now limited to the "safe-integer" range (google/go-jsonnet#859)
  • jsonnet CLI: New flag --no-trailing-newline - this disables the final newline that is normally included in the output of any Jsonnet evaluation. This option is also added to the API (#819, #843)
  • jsonnetfmt CLI: Names of unclean files are printed to stdout when using --test or --in-place mode (#863)
  • API: FindDependencies can now optionally follow symlinks (#730)
  • Restrict file writes to the specified output directory for --multi (google/go-jsonnet#850)

• Bug fixes

  • The index expression of a super[e] access (#849)
  • Function std.objectRemoveKey has been re-implemented to fix several bugs and unexpected behaviours (#837)
  • Missing trailing newline when using both --multi and --string options (google/go-jsonnet#819)
  • Fix implicit-to-explicit-plus conversion in jsonnetfmt (google/go-jsonnet#853)
  • Improve handling of YAML document streams in std.parseYaml (google/go-jsonnet#862)
  • Unchecked error in std.manifestYamlDoc(). (google/go-jsonnet#800)
  • Cache the error too in importAST(). (google/go-jsonnet#823)
  • Do not mutate std.removeAt parameters (google/go-jsonnet#812)
  • Handle negative range by returning an empty array (google/go-jsonnet#839)
  • Return null if parseYaml does not yield any result (google/go-jsonnet#841)
  • Linter: Support std.clamp function (google/go-jsonnet#840)
  • Linter: add optional parameters to std.manifestJsonEx in (google/go-jsonnet#842)
  • Linter: Optimize runtime complexity when passing in multiple snippets (google/go-jsonnet#725)

• Build systems, testing, CI, internal

  • chore: fix bazel example by @​y1hao in google/go-jsonnet#820
  • Make CI build the bazel example with multiple Bazel versions (google/go-jsonnet#832)
  • Remove Go Releaser archive naming overrides (google/go-jsonnet#848)

Full commit history: google/go-jsonnet@v0.21.0...v0.22.0

New Contributors

• @​y1hao made their first contribution in google/go-jsonnet#820
• @​shrred26 made their first contribution in google/go-jsonnet#806
• @​hofbi made their first contribution in google/go-jsonnet#815

... (truncated)

Commits

• 567b61a release: v0.22.0
• 456331f refactor: use MaxStack as depth limit instead of fixed constant
• 502106b fix: add missing linter golden files for cyclic tests
• 033195b fix: add stack frame accounting to manifest builtins
• 86c6dc1 Extend "Build and Publish Python Package" workflow to build Linux aarch64 wheels
• b5ef4cd release: prepare to release v0.22.0-rc1
• 160987f deps: update referenced github actions to latest
• 7b3fbdd update cpp-jsonnet to (unreleased) 3a7b2a565827635615f8a9432d94941e2a827c70
• 154626d print names of reformatted files when using jsonnetfmt --test or --in-place
• 509404f update cpp-jsonnet to (unreleased) 833f18402b6b6a2da0b2fae75446a1e14b9116dd
• 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)