Skip to content

Point repository references at impossibleG/impossible-embeddings - #2

Merged
autoantohaki merged 5 commits into
mainfrom
fix/repository-url
Oct 21, 2026
Merged

autoantohaki merged 5 commits into
mainfrom
fix/repository-url

Conversation

@autoantohaki

Copy link
Copy Markdown
Member

Before: Cargo.toml, the container OCI labels, the SBOM documentNamespace, SECURITY.md and the release guide all name impossibleG/impossible-embedding. That repository does not exist (the GitHub API returns 404), so the documented gh attestation verify ... --repo impossibleG/impossible-embedding check cannot pass against real release assets, and the image's source and documentation labels lead to a 404.

After: every reference names impossibleG/impossible-embeddings, the repository that actually builds and attests the releases.

How: a text-only change in five files: Cargo.toml, Dockerfile, SECURITY.md, docs/releasing.md and scripts/generate-sbom.ps1. Product and binary names (impossible-embedding) are unchanged.

The Unix-only model store used ? on rustix calls whose Errno had no
conversion into the crate error, so cargo check failed on Linux and CI
on main has been red since. Add the conversion, and take the credential
open error by reference so the Unix branch of map_open_error passes
clippy without an underscore-prefixed binding.
Cargo metadata, the container OCI labels, the SBOM namespace, the
security policy and the release verification command all named
impossibleG/impossible-embedding, which does not exist. The documented
gh attestation verify --repo command would fail against real release
assets, and the image source label pointed to a 404.
cargo deny now fails on RUSTSEC-2026-0346, -0347, -0348, -0349 (rustls),
-0382 (rustls-webpki) and -0381/-0383 (webpki-roots, webpki-root-certs).
These crates back the TLS client used for model downloads. Bump them to
the patched releases and regenerate the third-party notices.
@autoantohaki
autoantohaki merged commit 8eaa4d2 into main Oct 21, 2026
6 checks passed
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.

1 participant