Skip to content

Add osx-arm64 builds for fastframes#8321

Merged
hmaarrfk merged 1 commit intoconda-forge:mainfrom
p-queue:fastframes-osx-arm64
Mar 10, 2026
Merged

Add osx-arm64 builds for fastframes#8321
hmaarrfk merged 1 commit intoconda-forge:mainfrom
p-queue:fastframes-osx-arm64

Conversation

@p-queue
Copy link
Contributor

@p-queue p-queue commented Mar 9, 2026

@p-queue p-queue requested a review from a team as a code owner March 9, 2026 23:39
@conda-forge-admin
Copy link
Contributor

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

  • ❌ The MACOSX_DEPLOYMENT_TARGET key in /tmp/tmp1fmc8f7z/cf_feedstock_ops_dir/recipe/conda_build_config.yaml needs to be removed or replaced by c_stdlib_version, appropriately restricted to osx

For recipe/meta.yaml:

  • ℹ️ 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/22879910288. Examine the logs at this URL for more detail.

@p-queue
Copy link
Contributor Author

p-queue commented Mar 10, 2026

I am a bit confused by the error here as fastframes-feedstock is not using recipe/conda_build_config.yaml for anything. From what I can see here it seems like things should be handled correctly?

Edit: I guess this is probably just from the recipe/conda_build_config.yaml from conda-forge-pinning-feedstock itself.

@hmaarrfk hmaarrfk merged commit a814703 into conda-forge:main Mar 10, 2026
2 of 3 checks passed
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.

Missing builds for osx-arm64

3 participants