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

Disable Version Sources on a Per-Feedstock Basis #2820

Closed
ytausch opened this issue Jun 27, 2024 · 1 comment
Closed

Disable Version Sources on a Per-Feedstock Basis #2820

ytausch opened this issue Jun 27, 2024 · 1 comment

Comments

@ytausch
Copy link
Contributor

ytausch commented Jun 27, 2024

We should add a configuration option for conda-forge.yml that allows disabling some version sources for a particular feedstock.

Why do we need this?

  1. Feedstocks oftentimes rely on the hash stability of GitHub-generated tarballs, however, they have proven to not being stable despite GitHub promising to announce any changes to tarball stability within a six-months notice. (Or has there been a announcement I am not aware of?)
  2. This is why we want to use custom stable source archives provided by the repository maintainers.
  3. However, there are instances like LLVM where the repository maintainers upload their custom source archives only some time after the release has been created on GitHub.
  4. The bot then detects the new version from the GitHub RSS feed, but any update attempts fail because the source archive is not available yet. This has been observed here.

Our preferred solution is an option to disable the RSS version source (or any other source, of course) for instances like this.

@ytausch
Copy link
Contributor Author

ytausch commented Jun 27, 2024

Oops, this seems to exist already: bot.version_updates.sources

@ytausch ytausch closed this as completed Jun 27, 2024
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

No branches or pull requests

1 participant