fork: establish algolia/rtk identity with no-telemetry CI guard#1
Merged
fork: establish algolia/rtk identity with no-telemetry CI guard#1
Conversation
- install.sh now points to algolia/rtk at pinned v0.22.2 (overridable via RTK_VERSION env var) - All docs, scripts, CI workflows updated from rtk-ai/rtk to algolia/rtk - CHANGELOG historical upstream links preserved for attribution - All GitHub Actions workflows target 'main' branch (not 'master') - New ci.yml: build/test/clippy/fmt on ubuntu + macOS - New telemetry-guard CI job: blocks telemetry.rs, ureq, sha2, hostname deps, and phone-home patterns in source - CLAUDE.md documents fork maintenance strategy, sync policy, and telemetry exclusion rules
…re-commit hook to match CI
PLNech
force-pushed
the
fork/algolia-identity
branch
from
b6823a7 to
1a4b175
Compare
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
1 participant
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
Addresses the issue raised by Emma D'Arcy (2026-03-10): install script was fetching from upstream
rtk-ai/rtkinstead of our fork, risking telemetry-enabled releases.algolia/rtkat pinnedv0.22.2(overridable viaRTK_VERSION=vX.Y.Z)ci.yml: build/test/clippy/fmt on ubuntu + macOS, plus dedicatedtelemetry-guardjobsrc/telemetry.rs, forbidden deps (ureq,reqwest,sha2,hostname), phone-home source patternsalgolia/rtk(CHANGELOG historical links preserved)main(notmaster)git remote set-url --push upstream no-push-to-upstreamFor Security Review
See CHANGELOG entry
0.22.3-algolia.1for full scope. Key facts:grep -r "ureq\|reqwest\|telemetry" src/returns nothingtelemetry-guardjob enforces this on every PR going forwardsrc/telemetry.rsin v0.29.0: daily HTTP ping with device hash, OS, command usage statsTest plan
ci.yml+telemetry-guard)install.shpoints toalgolia/rtkreleases0.22.3-algolia.1