chore(sync): full sync v0.34.7 to upstream v0.43.0#10
Merged
Conversation
Full sync from v0.34.7 to upstream v0.43.0, carrying forward the re-applied token-diet integration patches (rtk-disabled sentinel on the native `rtk hook claude` path, telemetry policy verified, test-suite git-hook-environment fix, doctor command re-wired, mvn-build.toml filter-count fix, grep_cmd.rs dead-code allow). See CHANGELOG.md for full detail and docs/PLAN-fork-upstream-sync.md (token-diet repo) for the sync plan. CHANGELOG.md: restored all pre-sync fork-only entries (0.34.2-security.1 through 0.34.7, plus this session's earlier permission-engine-hardening and Codex/project-hooks entries) that the wholesale tree checkout silently dropped, repositioned to preserve append-only diff compliance. Fixed 3 false-positive pre-commit blockers from this being a genuine 9-version upstream sync: secret-scanner false positive on a benchmark fixture's placeholder credentials (.no-secrets-scan marker), hardcoded local-path false positives on generic ~/.claude doc examples (changed to $HOME/.claude in INSTALL.md, README_fr.md, one test fixture). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
👋 Thanks for the PR! It looks like this targets Please update the base branch:
See CONTRIBUTING.md for details. |
celstnblacc
pushed a commit
that referenced
this pull request
Jul 10, 2026
Content already synced via tree-merge in PR #10 — this commit records upstream's v0.43.0 tag as a real git ancestor with no content change, so 'git log HEAD..upstream/master' (used by token-diet upstream check/diff and the weekly drift-detection workflow) reports only genuinely new upstream commits going forward instead of the whole pre-sync history.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Full sync from this fork's v0.34.7 to upstream rtk-ai/rtk v0.43.0 (9 minor versions), per the token-diet fork-upstream-sync plan (iterations 1-3).
rtk-disabledsentinel on the nativertk hook claudepath, telemetry-off policy verified against upstream's own default, and a test-suite fix for a git-hook-environment leak (GIT_DIR/GIT_INDEX_FILEpollution corrupting isolated test git operations).rtk doctor(fork-only feature) after the wholesale tree merge silently dropped itsmain.rsCLI registration.src/filters/mvn-build.toml(superseded by upstream's nativemvn_cmd.rs), fixing a filter-count test mismatch.#![allow(dead_code)]ongrep_cmd.rs— pre-existing dead code in the v0.43.0 tag itself (superseded bysearch.rs), unrelated to this fork.~/doc paths).Full detail in CHANGELOG.md's
[Unreleased]sections.Test plan
cargo fmt --check,cargo clippy --all-targets— zero errorscargo test(all 7 test binaries, 2262+ tests) — 0 failures🤖 Generated with Claude Code