fix(rust): bump config-disassembler to 0.10.3 - #70
Merged
Merged
Conversation
Bumps the underlying config-disassembler Rust crate 0.10.2 -> 0.10.3, pulling in mcarvin8/config-disassembler#123: reassembled XML now renders single-child "compact" wrapper elements with no internal whitespace (e.g. Salesforce Flow's `<connector><targetReference>X</targetReference></connector>`) on one line instead of always block-formatting them, closing a byte-retention gap on round trip for metadata types that use this idiom heavily. Backward compatible -- directories disassembled by older crate versions have no such formatting on disk and continue to reassemble block-formatted exactly as before. No API changes on the Node side -- pure dependency bump. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01R4hK4DbmkU523ubHnubjcC
4 tasks done
mcarvin8
added a commit
to mcarvin8/sf-decomposer
that referenced
this pull request
Sep 8, 2026
* fix(deps): bump config-disassembler to 3.4.2 Bumps config-disassembler 3.4.1 -> 3.4.2 (root package.json and docker/package.json, kept in sync per the Dockerfile's own comment). Pulls in mcarvin8/config-disassembler-node#70, which bumps the underlying Rust crate to 0.10.3 (mcarvin8/config-disassembler#123): reassembled XML now renders single-child "compact" wrapper elements with no internal whitespace (e.g. Salesforce Flow's `<connector><targetReference>X</targetReference></connector>`) on one line instead of always block-formatting them, closing the byte- retention gap the perf suite measured on Mega_Flow.flow-meta.xml (103.52% -> 100.00%). Backward compatible with directories already disassembled by older crate versions. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01R4hK4DbmkU523ubHnubjcC * chore(megalinter): apply linters fixes [skip ci] * fix(deps): add missing config-disassembler-linux-arm64-musl to lock file npm's registry propagation lagged briefly after the 3.4.2 publish (same issue as the 3.4.1 bump) -- npm install ran here before that platform binary indexed, so package-lock.json never got its entry. CI's `npm ci` then correctly refused to install as out-of-sync. Re-ran `npm install` now that the registry has caught up; the lock file gains exactly the missing config-disassembler-linux-arm64-musl entry (no unrelated version churn). Verified `npm ci` succeeds and the full suite still passes (617/617). Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01R4hK4DbmkU523ubHnubjcC --------- Co-authored-by: Claude Sonnet 5 <[email protected]>
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
config-disassemblerRust crate 0.10.2 → 0.10.3, pulling in fix(xml): preserve compact single-child element formatting on round-trip config-disassembler#123: reassembled XML now renders single-child "compact" wrapper elements with no internal whitespace (e.g. Salesforce Flow's<connector><targetReference>X</targetReference></connector>) on one line instead of always block-formatting them, closing a byte-retention gap on round trip for metadata types that use this idiom heavily.Test plan
cargo build/npm run build:debugagainst 0.10.3npm test— 94/94 vitest tests passnpm run build(release) +npm test— 94/94 pass🤖 Generated with Claude Code
https://claude.ai/code/session_01R4hK4DbmkU523ubHnubjcC