Skip to content

RFC: Default to cargo-auditable - #79

Draft
xhochy wants to merge 2 commits into
conda-forge:mainfrom
xhochy:cargo-auditable
Draft

RFC: Default to cargo-auditable#79
xhochy wants to merge 2 commits into
conda-forge:mainfrom
xhochy:cargo-auditable

Conversation

@xhochy

@xhochy xhochy commented Jun 23, 2025

Copy link
Copy Markdown
Member

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@conda-forge-admin

conda-forge-admin commented Jun 23, 2025

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 (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15831216583. Examine the logs at this URL for more detail.

@xhochy
xhochy force-pushed the cargo-auditable branch 3 times, most recently from c54c552 to 9ff365a Compare June 23, 2025 17:39
@xhochy
xhochy force-pushed the cargo-auditable branch from 9ff365a to 638de79 Compare June 23, 2025 17:39
@conda-forge-admin

Copy link
Copy Markdown
Contributor

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

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15832223087. Examine the logs at this URL for more detail.

@xhochy
xhochy force-pushed the cargo-auditable branch from 4744a8f to 1a824c5 Compare June 23, 2025 18:54
@conda-forge-admin

conda-forge-admin commented Jun 23, 2025

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 (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/15833197160. Examine the logs at this URL for more detail.

@xhochy
xhochy force-pushed the cargo-auditable branch 2 times, most recently from 8e01733 to 9dce0bc Compare June 23, 2025 19:15
@pavelzw

pavelzw commented Jul 10, 2026

Copy link
Copy Markdown
Member

xref conda-forge/cfep#63

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