Skip to content

chore(main): release 0.22.5#4

Open
github-actions[bot] wants to merge 18 commits intomainfrom
release-please--branches--main--components--rtk
Open

chore(main): release 0.22.5#4
github-actions[bot] wants to merge 18 commits intomainfrom
release-please--branches--main--components--rtk

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented Mar 18, 2026

🤖 I have created a release beep boop

0.22.5 (2026-03-19)

Bug Fixes

  • correct git_cmd() doc comment per PR #5 review feedback (3c4126d)
  • passthrough --json in gh commands and -c in grep (d5f3cfa)

This PR was generated with Release Please. See documentation.

PLNech and others added 10 commits March 17, 2026 21:15
- 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
fork: establish algolia/rtk identity with no-telemetry CI guard
@github-actions github-actions Bot changed the title chore(main): release 1.0.0 chore(main): release 0.23.0 Mar 18, 2026
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--rtk branch from 7e4b2d7 to f2f76b4 Compare March 18, 2026 18:10
@github-actions github-actions Bot changed the title chore(main): release 0.23.0 chore(main): release 0.22.5 Mar 19, 2026
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--rtk branch from f2f76b4 to 390f04b Compare March 19, 2026 11:15
PLNech and others added 2 commits March 19, 2026 15:45
gh: when --json flag is present, bypass all filtering and passthrough
raw JSON output. RTK was reformatting structured JSON into lossy
human-readable summaries, breaking downstream jq/python consumers.

grep: detect -c/--count mode and passthrough rg output verbatim.
The file:count format was being misinterpreted as file:linenum:content,
producing gibberish like "📄 101 (1): prefix_saturated".

Closes bug-report: 2026-03-19-gh-json-output-rewritten.md
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--rtk branch from 390f04b to 7f881e4 Compare March 19, 2026 14:45
@PLNech PLNech force-pushed the main branch 2 times, most recently from 43f54e2 to 37ac0de Compare March 31, 2026 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant