This is an automated email from the ASF dual-hosted git repository.
viirya pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/spark-connect-gateway.git
The following commit(s) were added to refs/heads/main by this push:
new 027bc88 [SPARK-60852] Update pulldown-cmark in Cargo.lock to pick up
recent RustSec advisories
027bc88 is described below
commit 027bc88c4ee8c507e97c4aabcc9e907f35ddee96
Author: Liang-Chi Hsieh <[email protected]>
AuthorDate: Tue Nov 3 23:17:36 2026 -0800
[SPARK-60852] Update pulldown-cmark in Cargo.lock to pick up recent RustSec
advisories
### What changes were proposed in this pull request?
Update `pulldown-cmark` 0.13.4 -> 0.13.6 in `Cargo.lock`. Lockfile-only; no
`Cargo.toml` change, since `prost-build` requires `pulldown-cmark ^0.13`.
Only the entry's `version` and `checksum` lines change. The dependencies and
features of 0.13.6 are identical to 0.13.4 (bitflags, memchr, unicase; the
same
optional ones), so no other lockfile entry changes. The resolved set stays
at
431 crates.
### Why are the changes needed?
The scheduled `cargo audit` run on `main` has failed every day since
2026-10-29 because of two advisories against `pulldown-cmark` 0.13.4:
| Advisory | Issue | Fixed in |
|---|---|---|
| RUSTSEC-2026-0414 | Exponential event growth with `ENABLE_WIKILINKS` |
0.13.5 |
| RUSTSEC-2026-0433 | Quadratic parsing of nested image wikilinks with
`ENABLE_WIKILINKS` | 0.13.6 |
`pulldown-cmark` is a build-time dependency only:
`scg-genproto` (build script) -> `tonic-prost-build` -> `prost-build`, which
cleans up the markdown in `.proto` comments. `prost-build` parses with
`Options::all()`, which includes `ENABLE_WIKILINKS`, so the affected code
does
run, but only at build time and only on the vendored `.proto` files in this
repository. The crate is not linked into the gateway binary.
This is the last failure in the scheduled run: with it fixed, `cargo audit`
on
`main` exits 0.
### Does this PR introduce _any_ user-facing change?
No. Build-time dependency only.
### How was this patch tested?
- The checksum was checked against three sources: the crates.io API, the
SHA-256 of `pulldown-cmark-0.13.6.crate` downloaded from static.crates.io,
and the new lockfile line, all `3db2be46...69bb7b`.
- The dependency and feature sets were compared between 0.13.4 and 0.13.6
using both the crates.io API and the `Cargo.toml` inside the downloaded
`.crate`.
- `cargo audit` exits 0, with only the two existing allowed warnings
(`unsafe-libyaml` unmaintained, `chacha20` yanked).
- `dev/audit-new-advisories.sh` against `main`'s `Cargo.lock` (what this
PR's
`cargo audit` check runs) lists RUSTSEC-2026-0414 and RUSTSEC-2026-0433 as
resolved and nothing introduced.
- The CI build exercises the new version: `scg-genproto`'s build script runs
`prost-build` on every `.proto` file.
- License unchanged: MIT.
### Was this patch authored or co-authored using generative AI tooling?
Yes, co-authored with Claude Code.
Closes #58 from viirya/SPARK-60852.
Authored-by: Liang-Chi Hsieh <[email protected]>
Signed-off-by: Liang-Chi Hsieh <[email protected]>
---
Cargo.lock | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Cargo.lock b/Cargo.lock
index c91b330..68423d0 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -2519,9 +2519,9 @@ dependencies = [
[[package]]
name = "pulldown-cmark"
-version = "0.13.4"
+version = "0.13.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "e9f068eba8e7071c5f9511831b44f32c740d5adf574e990f946ddb53db2f314e"
+checksum = "3db2be46835f013dd3f4fa7f5f7402c537787b54ebb6fe2b94bbdd7e2669bb7b"
dependencies = [
"bitflags 2.13.1",
"memchr",
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]