Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

private cloudsmith registry no longer recognised #510

Closed
jayvdb opened this issue Apr 7, 2023 · 0 comments · Fixed by #511
Closed

private cloudsmith registry no longer recognised #510

jayvdb opened this issue Apr 7, 2023 · 0 comments · Fixed by #511
Labels
bug Something isn't working

Comments

@jayvdb
Copy link

jayvdb commented Apr 7, 2023

Describe the bug
We have a private registry allowed in our deny.toml like below, and as of v0.13.8 this is no longer being recognised.

allow-registry = [
  "https://dl.cloudsmith.io/basic/franklin-ai/rosalind/cargo/index.git",
]

Our builds are now failing with

error[source-not-allowed]: detected 'registry' source not explicitly allowed
   ┌─ /__w/rosalind/rosalind/Cargo.lock:53:22
   │
53 │ <package name> <package version> registry+https://dl.cloudsmith.io/basic/franklin-ai/rosalind/cargo/index.git
   │                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ source
   │

To Reproduce
Steps to reproduce the behavior:

  1. Create a private cloudsmith repository, c.f. https://cloudsmith.com/blog/worlds-first-private-cargo-registry-with-cloudsmith-rust/
  2. Use a crate published in the private cloudsmith repository
  3. Add the private cloudsmith repository to deny.toml `allow-registry
  4. Run cargo-deny

Expected behavior
The same behaviour as v0.13.7, given that .8 is a patch release.
Or a error indicating that our previous deny.toml entry needs to be changed in some new way to be compatible with v0.13.8

Screenshots
See log above

Device:

  • All

Additional context

@jayvdb jayvdb added the bug Something isn't working label Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant