Skip to content

Deprecate v0 recipe format - #34414

Merged
wolfv merged 3 commits into
conda-forge:mainfrom
wolfv:deprecate-v0
Aug 6, 2026
Merged

Deprecate v0 recipe format#34414
wolfv merged 3 commits into
conda-forge:mainfrom
wolfv:deprecate-v0

Conversation

@wolfv

@wolfv wolfv commented Aug 4, 2026

Copy link
Copy Markdown
Member

Checklist

  • Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
  • License file is packaged (see here for an example).
  • Source is from official source.
  • Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
  • If static libraries are linked in, the license of the static library is packaged.
  • Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
  • Build number is 0.
  • A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
  • GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
  • When in trouble, please check our knowledge base documentation before pinging a team.

@conda-forge-admin

conda-forge-admin commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/example-v0-deprecated/meta.yaml) and found it was in an excellent condition.

@wolfv wolfv changed the title Deprecate v0 Deprecate v0 recipe formay Aug 4, 2026
@wolfv wolfv changed the title Deprecate v0 recipe formay Deprecate v0 recipe format Aug 4, 2026
Comment thread pixi.toml
Comment on lines +73 to 74
description = "DEPRECATED: generate v0 only for exceptional recipes unsupported by v1"
cmd = "cd recipes && grayskull cran --strict-conda-forge"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to review the grayskull cran --strict-conda-forge output first. Submissions I've seen recently aren't at parity with our (standard) v0 recipes.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you let me know what to improve? Ideally give me a few examples and I will happily take a look!

@carterbox

Copy link
Copy Markdown
Member

@conda-forge/staged-recipes, please review

@conda-forge-webservices

Copy link
Copy Markdown

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: {conda-forge/staged-recipes, conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby, conda-forge/help-rust}. Thanks!

- [Currently available conda-forge packages](https://conda-forge.org/feedstock-outputs/)
- [The conda-forge docs](https://conda-forge.org/docs/maintainer/adding_pkgs.html#the-staging-process)
- [Grayskull](https://github.com/conda-incubator/grayskull) - to automatically generate a recipe for packages on PyPI
- [Grayskull](https://github.com/conda-incubator/grayskull) - to automatically generate a v1 recipe for packages on PyPI (pass `--use-v1-format`)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grayskull should change their default to v1 at this point, ideally.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already made the pr

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread .github/pull_request_template.md

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could rename the directory name to example-v0-deprecated or something like that.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wolfv
wolfv merged commit 9927cb7 into conda-forge:main Aug 6, 2026
9 checks passed
@matthewfeickert

Copy link
Copy Markdown
Member

The recipes/example-v0-deprecated/meta.yaml got cleaned up and removed by conda-forge-admin in b0fa2bf. Given that this file was renamed explicitly I don't think this was the intended outcome. Should it be brought back?

@wolfv

wolfv commented Aug 7, 2026

Copy link
Copy Markdown
Member Author

Fixed!

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants