Skip to content

Add cargo-edit package #29542

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

Merged
merged 3 commits into from
Apr 2, 2025
Merged

Add cargo-edit package #29542

merged 3 commits into from
Apr 2, 2025

Conversation

Hofer-Julian
Copy link
Contributor

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.

Copy link
Contributor

Hi! This is the staged-recipes linter and I found some lint.

It looks like some changes were made outside the recipes/ directory. To ensure everything runs smoothly, please make sure that recipes are only added to the recipes/ directory and no other files are changed.

If these changes are intentional (and you aren't submitting a recipe), please add a maintenance label to the PR.

File-specific lints and/or hints:

  • recipes/example-v1/recipe.yaml:

    • lints:
      • Do not edit or delete example recipes in recipes/example/ or recipe/example-v1/.
  • recipes/example-v1/README.md:

    • lints:
      • Please put your recipe in its own directory in the recipes/ directory as recipe/<name of feedstock>/<your recipe file>.yaml.
  • recipes/example/meta.yaml:

    • lints:
      • Do not edit or delete example recipes in recipes/example/ or recipe/example-v1/.

@conda-forge-admin
Copy link
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/cargo-edit/recipe.yaml) and found it was in an excellent condition.

Copy link
Contributor

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

@wolfv
Copy link
Member

wolfv commented Mar 27, 2025

Looks good! Happy to merge once the URL is fixed :)

@Hofer-Julian
Copy link
Contributor Author

This is now ready to be merged from my side @wolfv :)

@wolfv wolfv merged commit 75061c9 into conda-forge:main Apr 2, 2025
7 checks passed
@Hofer-Julian Hofer-Julian deleted the add-cargo-edit branch April 2, 2025 08:55
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.

3 participants