fix(deps): patch hickory-resolver to 0.26.3

[tobyhede]

Bumps hickory-resolver (and its lockstep siblings hickory-proto / hickory-net) from 0.26.1 to 0.26.3 to address:

• GHSA-5j98-2g5x-46v6 (High)
• GHSA-6w6g-hm98-mhgm (High)
• GHSA-6f2x-v7q7-m7m5 (Medium)

All affect hickory-resolver < 0.26.2. It is pulled in transitively via reqwest.

Lockfiles changed

• Cargo.lock
• languages/typescript/packages/protect-ffi/Cargo.lock
• packages/stack-auth/fuzz/Cargo.lock

(packages/eql/Cargo.lock was already on 0.26.3.)

Lockfile-only change: each file changes just the version and checksum of the three hickory crates. cargo update also rewired some windows-sys references, which has nothing to do with this fix, so I left those out. The hickory crates' dependency lists are identical between 0.26.1 and 0.26.3.

Verification

• cargo tree --locked accepts all three lockfiles unchanged
• cargo check --locked -p stack-auth -p stack-kms -p stack-encrypt (root workspace) passes
• cargo check --locked passes in languages/typescript/packages/protect-ffi and packages/stack-auth/fuzz
• No Cargo.lock in the repo still references hickory-resolver < 0.26.2

[changeset-bot]

⚠️ No Changeset found

Latest commit: a855d50

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-12T01:14:11.161226Z	a855d50	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (3)

• Cargo.lock is excluded by !**/*.lock
• languages/typescript/packages/protect-ffi/Cargo.lock is excluded by !**/*.lock
• packages/stack-auth/fuzz/Cargo.lock is excluded by !**/*.lock

---

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: d415e8e1-16c9-480a-b823-103567720e32

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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

[github-actions]

Mutation testing (cargo-mutants, --in-diff, stack-auth + stack-encrypt)

No mutants were generated for the changed lines.