chore(deps): update ghcr.io/docspec/api docker tag to v1.21.9

[renovate]

This PR contains the following updates:

Package	Update	Change
ghcr.io/docspec/api	patch	1.21.2 → 1.21.9

---

Release Notes

docspec/docspec (ghcr.io/docspec/api)

v1.21.9

Compare Source

Fixed

• (deps) update rust crate posthog-rs to 0.23.0
• (cli) correct DOCX support in convert help

Other

• (html-writer) cover orphan end document

v1.21.8

Compare Source

Fixed

• (docspec) compile the reader doc examples only with their format
• (docspec) gate the Send assertions on a reader being compiled in
• (docspec) derive the reader and writer cfgs in build.rs
• (docspec) compile under every reader and writer feature selection

Other

• (docspec) trim the comments around the derived cfgs
• (docx-reader) split document parsing into text, props, and media modules
• (http) extract conversion analytics into a private module

v1.21.7

Compare Source

Other

• (docx-reader) use a where clause for the extend trait bound
• (docx-reader) extract XmlCursor, EmitState, and PackageContext

v1.21.6

Compare Source

Fixed

• (blocknote-writer) close open child paragraph before emitting sibling block
• (http) adapt Sentry client options to 0.49 builder API
• (deps) update rust crate sentry to 0.49

Other

• assert JSON output as readable documents
• (memory) resolve memtest child binaries via Cargo's target directory
• distinguish supported from experimental formats

v1.21.5

Compare Source

Fixed

• (docspec) stream DOCX in AnyReader::from_path instead of buffering
• (http) avoid panic when serializing error responses

Other

• correct invalid commands, nonexistent APIs, and false capability claims
• (markdown-reader) drop dead_code allow and unused classify_start_tag
• (http) remove redundant inline allows already set workspace-wide

v1.21.4

Compare Source

Fixed

• (deps) update rust crate base64 to 0.23

Other

• improve documentation

v1.21.3

Compare Source

Fixed

• (deps) update rust crate posthog-rs to 0.21.0
• (deps) update rust crate posthog-rs to 0.20.0

Other

• fix clippy warnings

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 was generated by Mend Renovate. View the repository job log.

[kody-ai]

WHAT: The default image tag is set to 1.21.8 even though this dependency update targets 1.21.7. WHY/HOW: Default chart installs therefore render ghcr.io/docspec/api:1.21.8, deploying the wrong release or entering ImagePullBackOff if that tag is unavailable; set the tag to 1.21.7.

tag: "1.21.7"

Prompt for LLM

File charts/api/values.yaml:

Line 11:

WHAT: The default image tag is set to 1.21.8 even though this dependency update targets 1.21.7. WHY/HOW: Default chart installs therefore render `ghcr.io/docspec/api:1.21.8`, deploying the wrong release or entering `ImagePullBackOff` if that tag is unavailable; set the tag to `1.21.7`.

Suggested Code:

tag: "1.21.7"

_{Talk to Kody by mentioning @kody}

_{Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.}

​

​

[kody-ai]

WHAT: The committed tag value "1.21.8" does not match the PR title/description which states the update targets v1.21.7. WHY: The diff ships a different image version than what the PR advertises, so reviewers and downstream consumers cannot trust the stated version range (and Renovate/release tooling that pins to the described version will resolve to the wrong image). HOW: Align the tag with the stated target — set tag: "1.21.7" if 1.21.7 was intended, or update the PR title to v1.21.8 if 1.21.8 was intentional.

tag: "1.21.7"

Prompt for LLM

File charts/api/values.yaml:

Line 11:

WHAT: The committed tag value "1.21.8" does not match the PR title/description which states the update targets v1.21.7. WHY: The diff ships a different image version than what the PR advertises, so reviewers and downstream consumers cannot trust the stated version range (and Renovate/release tooling that pins to the described version will resolve to the wrong image). HOW: Align the tag with the stated target — set `tag: "1.21.7"` if 1.21.7 was intended, or update the PR title to v1.21.8 if 1.21.8 was intentional.

Suggested Code:

tag: "1.21.7"

_{Talk to Kody by mentioning @kody}

_{Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.}

​

​

[kody-ai]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​