Skip to content

chore(deps): bump hf-xet from 1.5.1 to 1.6.0 - #913

Closed
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/pip/main/hf-xet-1.6.0
Closed

chore(deps): bump hf-xet from 1.5.1 to 1.6.0#913
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/pip/main/hf-xet-1.6.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 10, 2026

Copy link
Copy Markdown
Contributor

Bumps hf-xet from 1.5.1 to 1.6.0.

Release notes

Sourced from hf-xet's releases.

[hf-xet v1.6.0] Stream shard finalization progress

Improvements

  • Stream shard finalization progress via POST /v2/shards, so large-shard validation/commit is visible instead of blocking silently after upload
  • Expose shard upload progress (validation, commit stages, completion) through upload progress tracking, including Python ShardUploadProgressReport
  • Minor upload efficiency: avoid cloning xorb bytes before streaming
  • Reduce xet_session future size to avoid compilation failure and stack overflows
  • Allow selecting the reqwest TLS backend via hf-xet features
  • Drop pyo3 auto-initialize feature to avoid build failures when that feature is combined with a Python built --disable-shared

New Contributors

Full Changelog: huggingface/xet-core@v1.5.2...v1.6.0

[hf-xet v1.5.2] Fix HTTP Request Retry

Problems addressed

  • This release fixes a bug in HTTP request retry configuration that could cause apparent hangs under poor network conditions when a request was retried more than twice. Related PR: huggingface/xet-core#893

New Contributors

Full Changelog: huggingface/xet-core@v1.5.1...v1.5.2

Commits
  • de71453 bump hf-xet Python to 1.6.0 (#924)
  • 0f689ef chore: bump crate versions to 1.6.0 (#925)
  • 1284224 Local simulation test for v2 shards upload API (#910)
  • f3d85bd fix: scope pyo3 auto-initialize to dev-dependencies (#891) (#923)
  • 7a26750 Allow selecting the reqwest TLS backend via hf-xet features (#917)
  • a3f7e87 Embed input in the DataHash parse Error (#914)
  • fe93e98 fix: stack overflow in xet-session from unboxed futures (#908)
  • 87ca7ad Stream shard finalization progress via POST /v2/shards (#884)
  • 075687d chore: bump crate versions to 1.5.4 (#907)
  • 98e9348 Fix bump-crates-version workflow (#906)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [hf-xet](https://github.com/huggingface/xet-core) from 1.5.1 to 1.6.0.
- [Release notes](https://github.com/huggingface/xet-core/releases)
- [Commits](huggingface/xet-core@v1.5.1...v1.6.0)

---
updated-dependencies:
- dependency-name: hf-xet
  dependency-version: 1.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Aug 10, 2026
@dependabot
dependabot Bot requested a review from seonghobae as a code owner August 10, 2026 13:36
@dependabot dependabot Bot added the python Pull requests that update python code label Aug 10, 2026
@seonghobae
seonghobae marked this pull request as draft August 11, 2026 06:54

Copy link
Copy Markdown
Contributor

Fail-closed quality gate (exact head 670bb7a973efcf634723ba62deaaaf8fd56b8eaa against independently resolved live main 6eb06cdd08c79a06f7b390069d4ffa49e2eb7dba):

  • The only changed path is requirements-strix-ci-hashes.txt.
  • Eight generic security/supply-chain workflows are terminal-success, but no Strix Changed Path Quality CI run exists for this head.
  • Root cause: protected-main .github/workflows/strix-changed-path-quality-ci.yml does not include requirements-strix-ci-hashes.txt in its pull_request.paths filter, even though the lock controls Strix CI dependencies.
  • Direct path-filter repair is not safe in this lane because open PRs fix(coverage): retry transient trusted uv downloads #790 and fix(coverage): replace stale LLVM runtime-boundary repair #827 already target that workflow path. The workflow also has no manual-dispatch trigger, and an empty commit merely to retrigger evidence is rejected.

This PR is therefore Draft until a single authoritative workflow-path repair reaches protected main, Dependabot refreshes this exact dependency change against that base, and the resulting unchanged head receives an actual terminal-success Strix quality run. Existing generic checks are not semantic/runtime compatibility evidence.

@seonghobae
seonghobae marked this pull request as ready for review August 12, 2026 04:07

Copy link
Copy Markdown
Contributor

@opencode-agent review

Review exact current head 670bb7a973efcf634723ba62deaaaf8fd56b8eaa against independently resolved live main 6eb06cdd08c79a06f7b390069d4ffa49e2eb7dba. 16 exact-head hosted workflows are terminal-success and no review thread is unresolved. Verify the hf-xet dependency update is limited to the declared artifact and exact lock evidence, with compatibility and supply-chain behavior preserved. Automated judgment is not qualifying independent human approval or merge authorization.

@seonghobae seonghobae left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exact-head dependency review: the one-file diff only changes hf-xet and its published wheel hashes in requirements-strix-ci-hashes.txt, and the observed generic workflows are successful. The exact head has no Strix Changed Path Quality result because the permanent manifest trigger is missing. #935 is the bounded prerequisite. After it reaches main, recreate or rebase this branch so Strix validates the resulting exact head; then reacquire review and branch-protection evidence. Approval and auto-merge are withheld until that evidence exists.

Copy link
Copy Markdown
Contributor

Exact-head gate status for 670bb7a973efcf634723ba62deaaaf8fd56b8eaa: the generic CodeQL, Python Security, Security Scan, Semgrep, Secret Scan, OSV, Scorecard, and SBOM workflows are terminal-success, but this PR changes only requirements-strix-ci-hashes.txt and no exact-head Strix dependency-lock quality workflow ran.

Do not approve or merge from the generic green set alone. The permanent trigger repair in #935 must first reach protected main, after which this unchanged/rebased head must receive and pass the full Strix hash-locked installation, import, model-pool, syntax, and clean-worktree contract. Any rebase or Dependabot recreation invalidates current evidence and requires a fresh exact-head cycle.

@seonghobae
seonghobae enabled auto-merge (squash) August 13, 2026 04:32
CWE-494/CWE-829: the Strix --require-hashes lock must keep every
published platform-wheel digest and must not retain 1.5.1.
Materialize a base Python lock only when every package line is an exact
SHA-256 pin or a two-token relative -r/--requirement include of a
candidate lock path. A lone --require-hashes directive, ./dotted paths,
and -r other-hashes.txt no longer enter the trusted build context.
@seonghobae

Copy link
Copy Markdown
Contributor

@opencode-agent review

Re-evaluate exact current head d8d1b0ffff67f8b6f2c4f78b087e2233dc157ac3. 리뷰 확인 for the bounded-include increment; do not treat Checks wait as a blocker.

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

  • Problem: Failed same-head checks remain for d8d1b0ffff67f8b6f2c4f78b087e2233dc157ac3.
  • Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
  • Fix: Read and fix the failed check logs below, then rerun the current-head checks.
  • Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (5 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (5 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Docs: strix-hf-xet-pin.md"]
  S2 --> I2["operator or user guidance"]
  I2 --> R2["Review risk: Docs: strix-hf-xet-pin.md"]
  R2 --> V2["docs review"]
  Evidence --> S3["CI script: materialize_base_python_requirements.py"]
  S3 --> I3["review and security gate shell path"]
  I3 --> R3["Review risk: CI script: materialize_base_python_requirements.py"]
  R3 --> V3["bash -n plus Strix self-test"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> R4["Review risk: Test (2 files)"]
  R4 --> V4["targeted test run"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: d8d1b0ffff67f8b6f2c4f78b087e2233dc157ac3
  • Workflow run: 31754698018
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode could not approve from deterministic current-head evidence because GitHub Checks have failed.

Findings

1. HIGH Current-head GitHub Checks - Fix failed required checks before approval

  • Problem: Failed same-head checks remain for d8d1b0ffff67f8b6f2c4f78b087e2233dc157ac3.
  • Root cause: The model-unavailable evidence fallback is allowed only when peer GitHub Checks are complete and clean.
  • Fix: Read and fix the failed check logs below, then rerun the current-head checks.
  • Regression test: Keep the model-unavailable fallback gated on an empty failed-check rollup.

Failed checks:

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file (5 files)"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file (5 files)"]
  R1 --> V1["required checks"]
  Evidence --> S2["Docs: strix-hf-xet-pin.md"]
  S2 --> I2["operator or user guidance"]
  I2 --> R2["Review risk: Docs: strix-hf-xet-pin.md"]
  R2 --> V2["docs review"]
  Evidence --> S3["CI script: materialize_base_python_requirements.py"]
  S3 --> I3["review and security gate shell path"]
  I3 --> R3["Review risk: CI script: materialize_base_python_requirements.py"]
  R3 --> V3["bash -n plus Strix self-test"]
  Evidence --> S4["Test (2 files)"]
  S4 --> I4["regression suite"]
  I4 --> R4["Review risk: Test (2 files)"]
  R4 --> V4["targeted test run"]
Loading

@opencode-agent
opencode-agent Bot disabled auto-merge August 14, 2026 02:38
@seonghobae
seonghobae marked this pull request as draft August 14, 2026 08:50

Copy link
Copy Markdown
Contributor

Returned to Draft because this is no longer a clean Dependabot dependency update.

The intended slice is the hf-xet 1.5.1→1.6.0 hash-pin update with its focused compatibility/lock verification and bounded doctoring. Head d8d1b0ffff67f8b6f2c4f78b087e2233dc157ac3 also carries unrelated trusted-uv materializer source/tests and broad governance-document changes. Those additions prevent Dependabot from safely rebasing/recreating the dependency PR and obscure the actual supply-chain delta.

Recreate or rebuild from protected main so the effective diff contains only requirements-strix-ci-hashes.txt, the focused hf-xet pin contract, and directly attributable doctoring/changelog evidence. Preserve materializer work in its authoritative PR, then run exact-head Strix/security/supply-chain checks and obtain independent review.

Copy link
Copy Markdown
Contributor

Closing this dependency PR instead of merging its current branch. The intended hf-xet lock update is valid in principle, but the branch is no longer a clean dependency-only delta: it also carries central trusted-uv materializer source/tests and governance docs that overlap the actively verified #790 trust-boundary repair. Its current OpenCode review also correctly records non-clean same-head check history. Recreate the hf-xet update from protected main after #790 and the permanent Strix manifest-trigger line (#935) integrate; require the resulting branch to contain only the lock/update contract and fresh exact-head Strix/security evidence. No dependency downgrade or ignore rule is being introduced.

@seonghobae seonghobae closed this Aug 14, 2026
@dependabot @github

dependabot Bot commented on behalf of github Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/pip/main/hf-xet-1.6.0 branch August 14, 2026 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant