Update ghostscript to 10.07.1

[bryan-minimal]

Update ghostscript 10.06.0 → 10.07.1

Source: github:ArtifexSoftware/ghostpdl-downloads (release)
Release: https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/tag/gs10071
Changelog: ArtifexSoftware/ghostpdl-downloads@gs10060...gs10071

Pkgscan (Layer-1 attack detection)

Scanned the 10.06.0 → 10.07.1 source diff. No gating (Critical/High) findings.

Auto-applied structural fix: rewrote the GitHub release-download tag gs10060 → gs10071. ghostscript's download tag is the version with the dots stripped (10.06.0 → gs10060), so a plain version bump leaves it stale and the URL 404s. The updater now points it at the resolved upstream tag (gominimal/pkgmgr-rs#578) — at both fetch time and in the committed build.ncl, so it builds and stays correct across future bumps.

Changes

	Old	New
Version	10.06.0	10.07.1
URL tag	gs10060	gs10071
sha256	64352648…	1cdb766d…

Direct GitHub release download (no gs:// mirror). Tarball sha256 verified.

Advisory partition (cleared / still-affecting) is computed by the runner against the vuln DB; this PR was cut from a laptop without DB reachability, so that section is omitted here — the runner's re-scan on merge populates it.

Merge gate: build + tests must pass, AND a separate human reviewer's approval — the bot only cuts the PR.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 780b1338-126c-4092-a65c-846fbcb8aa20

📥 Commits

Reviewing files that changed from the base of the PR and between 2b2005f and f2f25cc.

📒 Files selected for processing (1)

• packages/ghostscript/build.ncl

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch gs-update

---

_{Comment @coderabbitai help to get the list of available commands.}