Skip to content

Update pin for aws_c_common#7103

Closed
regro-cf-autotick-bot wants to merge 1 commit intoconda-forge:mainfrom
regro-cf-autotick-bot:new_pin-aws_c_common-0.11.1-0-_h987a59
Closed

Update pin for aws_c_common#7103
regro-cf-autotick-bot wants to merge 1 commit intoconda-forge:mainfrom
regro-cf-autotick-bot:new_pin-aws_c_common-0.11.1-0-_h987a59

Conversation

@regro-cf-autotick-bot
Copy link
Contributor

This PR has been triggered in an effort to update the pin for aws_c_common. The current pinned version is 0.10.6, the latest available version is 0.11.1 and the max pin pattern is x.x.x. This migration will impact 1 feedstocks.

Checklist:

  • The new version is a stable supported pin.
  • I checked that the ABI changed from 0.10.6 to 0.11.1.

**Please note that if you close this PR we presume that the new pin has been rejected.

@conda-forge-admin please ping aws-c-common

This PR was generated by https://github.com/regro/cf-scripts/actions/runs/13661473924 - please use this URL for debugging.

@regro-cf-autotick-bot regro-cf-autotick-bot requested a review from a team as a code owner March 4, 2025 19:46
@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/aws-c-common and so here I am doing that.

@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 (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:

  • ℹ️ top-level output has some malformed specs:
  • In section test: python >= 3.8 Requirements spec fields should always be space-separated to avoid known issues in conda-build. For example, instead of name =version=build, use name version build`.

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

@xhochy xhochy closed this Mar 5, 2025
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