Repository navigation
chore: lock release and Docker builds to Cargo.lock - #50
Merged
Merged
Conversation
Ref #48 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Oct 15, 2026
Merged
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
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
Ref #48 (lockfile half): adds
--lockedto every dependency-resolving cargo invocation in the release pipeline and Docker builds, matching what CI already does since #46 — a release or image build can no longer resolve different dependencies than CI tested.Type
chore— Maintenance, CI, etc.Changes
.github/workflows/release.yml:cargo build --release --locked --target … -p covecto -p covecto-apiDockerfile:--lockedon the dependency pre-build step and the finalcargo build --release --locked --bin covecto(the Dockerfile already copiesCargo.toml+Cargo.lockbefore sources, so the lockfile is present and layer caching is unchanged;.dockerignoredoes not exclude it)Dockerfile.binaries: no change needed — it only copies pre-built binaries, no cargo stepcargo publishlines in release.yml (would need--allow-dirtyinteraction review; can be a follow-up)Testing
cargo build --release --locked -p covecto-core— clean locally (6m18s)Related Issues
Ref #48
Checklist
develop