-
### Describe your use case
As part of the effort to write snapshot tests for `cargo-semver-checks` edge cases (see #846), we need to use a Cargo registry for some edge cases, for example when the bas…
-
This will require semantic-release-nuget's configuration object to be changed.
Currently, semantic-release-nuget only allows pushing to one custom server with `NUGET_TOKEN`. This prevents users fro…
-
### Problem Statement
The cleanup policies currently do not support image data context entries:
```yaml
context:
- name: imageData
imageRegistry:
reference: "ghcr.io/kyverno/kyverno"
…
-
### Problem
When the alternative registry index is specified via environment variable (e.g., `CARGO_REGISTRIES_MY_REGISTRY_INDEX`), then retrieving the token from `.cargo/credentials{,.toml}` does no…
-
### Problem
In sandboxed/hermetic environments such as Bazel, `$HOME` is not available. This causes builds to fail following #2727. In our case, we're just using public registries so appearently be…
-
Add a builtin publish-job for uploading to crates.io, in the same vein as the homebrew one.
Use this as a template: https://github.com/axodotdev/cargo-dist/blob/main/.github/workflows/publish-relea…
-
### Feature request description
Assume that the following can be found at $HOME/.config/containers/registries.conf, on macOS:
```
unqualified-search-registries = ['docker.io']
[[registry]]
…
-
Now that Cargo alternative registries have been stabilized, they are configured as:
```toml
[registries]
my-registry = { index = "https://my-intranet:8080/git/index" }
```
Currently, Cargo uses t…
-
### TL;DR
We could create a central registry (or multiple registries) probably in the form of a YAML file, of all the templates that are known to exist.
### Detailed design
```markdown
Desired feat…
-
### Is your feature request related to a problem? Please describe.
When running zot on small scale edge locations or IOT environments with a shared internet line, there might be the relevance to li…