chore(deps): update dependency google/jsonnet to v0.19.1

[renovate]

This PR contains the following updates:

Package	Update	Change
google/jsonnet	minor	v0.17.0 -> v0.19.1

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

google/jsonnet

v0.19.1

Compare Source

The previous v0.19.0 release had a small change in the C bindings to allow importbin to function, but missing from the release notes was mention of the fact that the Python bindings had also changed in a similar way - to require the content of the file to be provided as a bytes type instead of a str. To convert from str to bytes, simply call .encode() on the str.

In order to write Python code that works for both Jsonnet versions, the Jsonnet version is now provided as a field of the _jsonnet module, which allows writing code like the following:

import _jsonnet
import semver

import_returns_bytes = semver.compare(getattr(_jsonnet, 'version', 'v0.18.0')[1:], '0.18.0') > 0

def no_nl_eof(directory, rel):
    if import_returns_bytes:
        return "foo.jsonnet", b"42"
    else:
        return "foo.jsonnet", "42"

_jsonnet.evaluate_snippet("test.jsonnet", "{\nlocal foo = import 'foo.jsonnet',\n \n 'bar': foo\n }\n", import_callback=no_nl_eof)

This release also fixes an off-by-one truncation error in the import callback logic of the Python bindings introduced in the previous release. This was only noticeable if the imported file had no trailing \n, or if you were using importbin with a Python import callback.

v0.19.0

Compare Source

Language

• importbin feature for loading binary files

Tooling

• In order to support importbin, it was necessary to change the C API for import callbacks so that
  they can return arbitrary binary blobs (that can contain \0) as opposed to just strings. This
  change is not binary compatible with previous versions of libjsonnet. If you build against
  libjsonnet.h and you use import callbacks then you will have to make a small adjustment to your
  code.

• The emscripten build rules are now gone.

• Fixed memory leak in libjsonnet++.cpp

• Fixed lack of jsonnet_realloc in Go C bindings

• There are many more native implementations of library functions on the Go side, resulting in better
  performance for Jsonnet code calling those library functions.

Standard library

• std.all
• std.any
• std.split and std.splitLimit support multi-character split strings
• std.splitLimitR

v0.18.0

Compare Source

WASM

• The Jsonnet website now uses a WASM build of go-jsonnet for its online demos instead of an emscripten build of the C++ implementation. This is part of the ongoing migration towards go-jsonnet and away from C++ Jsonnet.

Language

• Unicode characters outside the "basic multilingual plane" (i.e. beyond the first 64k of them) now supported in unicode escapes in string literals that use unicode surrogate pairs.

Tooling

• Formatter now strips excess newlines after a comment at the end of a file.

Standard library

• Performance improvement to std.stripChars
• New: std.objectGetOrDefault and std.objectGetOrDefaultAll
• New: quote_keys parameter for std.manifestYamlDoc
• New: std.manifestToml
• New: std.manifestJsonMinified
• New: std.parseYaml

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[suzuki-shunsuke]

• jsonnet has no asset #3144

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (v0.19.1). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.