Skip to content

chore: sync Cargo.lock to aprender@0.35.1 (post-publish)#1896

Closed
noahgift wants to merge 3 commits into
mainfrom
chore/sync-cargo-lock-aprender-0.35.1
Closed

chore: sync Cargo.lock to aprender@0.35.1 (post-publish)#1896
noahgift wants to merge 3 commits into
mainfrom
chore/sync-cargo-lock-aprender-0.35.1

Conversation

@noahgift

Copy link
Copy Markdown
Contributor

Summary

Post-publish housekeeping: bump aprender entry in Cargo.lock to 0.35.1 to match the aprender@0.35.1 that shipped to crates.io after PR #1895.

Why

Workspace Cargo.toml says version = "0.35.1" (since #1895 merged), but Cargo.lock still listed aprender 0.35.0. Downstream cargo install --git users would see the right code but the wrong manifest version. This 3-line lockfile delta closes the drift.

Diff

[[package]]
 name = "aprender"
-version = "0.35.0"
+version = "0.35.1"
 dependencies = [
  "apr-cli",
  "aprender-core",
]

Plus two transitive aprender 0.35.0 → 0.35.1 references in the deps of aprender-monte-carlo and aprender-tsp.

🤖 Generated with Claude Code

@noahgift noahgift enabled auto-merge (squash) May 23, 2026 04:19
@noahgift

Copy link
Copy Markdown
Contributor Author

Subsumed by #1898 (mega-bundle hiatus close-out). Squash-merge preserves the per-PR commit message — see #1898 commit log.

@noahgift noahgift closed this May 23, 2026
auto-merge was automatically disabled May 23, 2026 07:09

Pull request was closed

noahgift added a commit that referenced this pull request May 23, 2026
, #1896, #1897) (#1898)

* docs(spec): SPEC-DISTILL-001 §87 — PMAT-704 post-mortem on Bug B wrong turn (#1880)

* chore(distill): Stage D dispatch wrapper with PMAT-701 lessons baked in (#1883)

* chore(distill): Phase 5 HumanEval dispatch wrapper (#1886)

* chore: bundle PMAT-702..705 distill cascade + clippy fix (#1897)

* fix(cli): point 7B qwen models to single-file GGUF artifacts and align caches (#1891)

* fix(chat): preserve original path in FileNotFound for filesystem paths

PR #1891 wrapped all path_arg through HF alias resolution. For inputs
that look like filesystem paths (absolute or starts with ./, ../) and
don't exist, the alias resolver was rewriting them as hf:// URIs and
returning a mangled path in the FileNotFound error.

Fix: short-circuit with the original path_arg in the error BEFORE alias
resolution kicks in. Preserves the contract that test_run_file_not_found
and test_run_nonexistent_path_without_trace assert.

Closes the workspace-test failure on bundle PR #1898.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant