Skip to content

fix(vordr): commit Cargo.lock for reproducible builds (re-apply, closes #14)#22

Merged
hyperpolymath merged 1 commit into
mainfrom
refix/vordr-cargo-lockfile
May 3, 2026
Merged

fix(vordr): commit Cargo.lock for reproducible builds (re-apply, closes #14)#22
hyperpolymath merged 1 commit into
mainfrom
refix/vordr-cargo-lockfile

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

Re-applies fix originally squash-merged as #19 and reverted as part of the rescript-ecosystem cleanup. Same content. Closes #14.

Containerfile expects Cargo.lock alongside Cargo.toml; .gitignore was previously hiding it. Force-added so binary-crate builds are reproducible.

Closes #14.

The Containerfile expects Cargo.lock alongside Cargo.toml; it wasn't
committed because the repo's .gitignore broadly excludes Cargo.lock
(library-crate convention). For BINARY crates (vordr is a CLI binary)
the lockfile should be tracked so deployments are reproducible.

Force-added via `git add -f` to bypass the .gitignore rule. A cleaner
follow-up would be to add a .gitignore exception:
  !container-stack/vordr/src/rust/Cargo.lock
or move vordr-specific .gitignore rules into a per-crate .gitignore.
@hyperpolymath hyperpolymath merged commit 8fc3981 into main May 3, 2026
6 checks passed
@hyperpolymath hyperpolymath deleted the refix/vordr-cargo-lockfile branch May 3, 2026 10:33
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 3, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[container-stack/vordr] Cargo.lock not committed; Containerfile COPY fails

1 participant