Repository navigation
chore(master): release 0.9.3 - #62
Merged
pszymkowiak merged 1 commit intoFeb 6, 2026
Merged
Conversation
Contributor
Author
|
🤖 Created releases: 🌻 |
ahundt
pushed a commit
to ahundt/rtk
that referenced
this pull request
Feb 23, 2026
…ster--components--rtk chore(master): release 0.9.3
KuSh
pushed a commit
that referenced
this pull request
Aug 30, 2026
…ment Review round on PR #62 found two hand-edited JSON parse sites the sweep missed — read_composer_bin_dir (core/utils.rs) and parse_global_json_mtp_mode (dotnet_cmd.rs, where BOMs are most common) — plus a test comment claiming the toml crate rejects BOMs when it in fact tolerates them (which is the very reason TOML sites are untouched). Also adds the BOM+invalid-JSON edge test the spec asked for: stripping must not mask genuinely broken JSON. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
KuSh
pushed a commit
that referenced
this pull request
Aug 30, 2026
…sites Follow-up to upstream #3203 (fork PR #62), which added strip_leading_bom() for config reads. KuSh's review flagged three more parse sites that hard-fail on BOM-prefixed files, scoped out of #3203 into this follow-up: - deps.rs summarize_package_json_str: a package.json saved by Notepad or PowerShell 5.1 Out-File killed `rtk deps` with a bare "expected value at line 1 column 1" (no file path). Now BOM-tolerant, with .context() naming the file on both read and parse failures. - json_cmd.rs filter_json_compact / filter_json_string: `rtk json` (both compact and --keys-only) errored on BOM-prefixed files -- the most likely command to be pointed at human-saved JSON. Unit tests per site: BOM input parses identically to plain input; invalid package.json errors now carry the path. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
🤖 I have created a release beep boop
0.9.3 (2026-02-06)
Bug Fixes
This PR was generated with Release Please. See documentation.