Repository navigation
chore: sync Cargo.lock with workspace version + lock CI to the lockfile - #46
Merged
Merged
Conversation
Cargo.lock still recorded 0.1.0 while the workspace Cargo.toml moved to 0.1.1 in the v0.1.1 release; any cargo invocation on a fresh clone dirtied the tree. Sync the lockfile and add --locked to CI check/clippy/test/build so this class of drift fails CI instead of accumulating. Fixes #44
This was referenced Oct 15, 2026
ajianaz
added a commit
that referenced
this pull request
Oct 15, 2026
Fixed: - Streaming path (vectorize_to) now applies SVG optimization when optimize=true; it was silently skipped (#43) - PixelExact streaming metadata: svg_byte_size off-by-one and path_count double-counting translucent paths (#47) Changed: - CI, release workflow and Dockerfile build with --locked; Cargo.lock synced with the workspace version (#46, #50) - Parity test vectorize()/vectorize_to() hardened: 58 cases, config matrix, ground-truth counter assertions (#47, #49) Co-authored-by: ajianaz <ajianaz@users.noreply.github.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
5 tasks done
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.
Description
Fixes #44:
Cargo.lockatdeveloprecordedcovecto/covecto-api/covecto-cliat 0.1.0 while the workspaceCargo.tomlis 0.1.1 (since the v0.1.1 release, PR #35) — the lock update was never committed with the release. Any cargo command on a fresh clone rewrites the lock and dirties the tree.Type
chore— Maintenance, CI, etc.Changes
Cargo.lockto the workspace version (0.1.0 → 0.1.1, 3 lines)--lockedto CIcheck,clippy,test, andbuildso lockfile drift fails CI instead of accumulating silentlycargo fmtintentionally stays un-locked (it does not resolve dependencies)Testing
cargo check --workspace --all-targets --locked— passes locally (1m56s)git statusclean aftercargo metadataon a fresh worktree--lockedon all four jobsRelated Issues
Closes #44
Checklist
develop