msgpack-python v1.0.8

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by source code inspection shows no discrepancy with the stated requirements in the meta.yaml.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/8120493336, please use this URL for debugging.}

[conda-forge-webservices]

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) and found it was in an excellent condition.

[ocefpaf]

@conda-forge-admin, please rerender

[github-actions]

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

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/msgpack-python-feedstock/actions/runs/8158134499.

[mattip]

Over in the ray feedstock, I needed to delete this line and rerender to get past the CI failure:

msgpack-python-feedstock/conda-forge.yml

Line 13 in 2b66698

conda_build_tool: mambabuild

Perhaps that construct should be flagged? @h-vetinari
A search in the conda-forge org showed only this usage and the one removed in conda-forge/ray-packages-feedstock#152

[h-vetinari]

Perhaps that construct should be flagged? @h-vetinari

It's "just" that currently boa is incompatible with newer conda-build, so the requirements cannot be resolved. In principle, the line works correctly, so it's borderline IMO whether flagging it is the right approach.

[mattip]

OK, just thought I would point out the problem. It seems not too many recipes are pinning to mambabuild anyway. Thanks for fixing here.

[wolfv]

@h-vetinari should we merge this one? :)

[jakirkham]

@conda-forge-admin , please re-render

[conda-forge-webservices]

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) and found it was in an excellent condition.

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

For recipe:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

[conda-forge-webservices]

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) and found it was in an excellent condition.

[jakirkham]

@conda-forge-admin , please re-render

[jakirkham]

@conda-forge-admin , please re-render

[github-actions]

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

I tried to rerender for you but ran into some issues. Please check the output logs of the latest webservices GitHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or you can try rerendeing locally.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/msgpack-python-feedstock/actions/runs/9070073871.

[jakirkham]

@conda-forge-admin , please re-render

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing, but could not be merged (error=API error in PUT to merge -- 'Resource not accessible by integration').

[jakirkham]

Thus the PR was passing, but could not be merged (error=API error in PUT to merge -- 'Resource not accessible by integration').

@jaimergp @beckermr could this be related to recent automerge changes?

[jakirkham]

In case it is helpful, here is the traceback from the GHA job:

Traceback (most recent call last):
  File "/cf-autotick-bot-action/conda_forge_automerge_action/automerge.py", line 482, in _automerge_pr
    merge_status = pr.merge(
                   ^^^^^^^^^
  File "/opt/conda/lib/python3.11/site-packages/github/PullRequest.py", line 845, in merge
    headers, data = self._requester.requestJsonAndCheck("PUT", f"{self.url}/merge", input=post_parameters)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/lib/python3.11/site-packages/github/Requester.py", line 548, in requestJsonAndCheck
    return self.__check(*self.requestJson(verb, url, parameters, headers, input, self.__customConnection(url)))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/lib/python3.11/site-packages/github/Requester.py", line 609, in __check
    raise self.createException(status, responseHeaders, data)
github.GithubException.GithubException: 403 {"message": "Resource not accessible by integration", "documentation_url": "https://docs.github.com/rest/pulls/pulls#merge-a-pull-request"}
INFO:conda_forge_automerge_action.automerge:DID NOT MERGE PR 37 on conda-forge/msgpack-python-feedstock: PR could not be merged: API error in PUT to merge -- 'Resource not accessible by integration'

[beckermr]

This looks like a github api error. Other automerge have gone through recently, so I doubt there is anything we need to do. Just merge it by hand?

[jakirkham]

Am noticing some automerge jobs are run by ghost and some conda-forge-webservices [bot]. Is this expected/relevant?

[beckermr]

No idea.