ruamel.yaml v0.18.6

[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 code>@conda-forge-admin,</codeplease 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 code>@<space/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 a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by source code inspection but not in the meta.yaml:

• ruamel

_{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/7811987140, please use this URL for debugging.}

[conda-forge-webservices[bot]]

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.

[davidbrochart]

Closing in favor of #194.

[mbargull]

Closing in favor of #194.

Thanks. Have you seen the bot creating duplicate version update PRs before? The merged branch's name is 0.18.6_h8ef321 whereas this one is 0.18.6_h797791. Kind of looks like is ran for 2 different configurations!? (The re-render commit at least used the same package versions.)

[davidbrochart]

Yes it's strange that there were two identical PRs, maybe a glitch somewhere.

[mbargull]

Looking at the changes in https://github.com/regro/cf-graph-countyfair/ , it might've been a timing issue in that the workflow that would've registered gh-194 in the graph did not get to it in the approx. 2 hours it was open? refs:

• registered new upstream versions: https://github.com/regro/cf-graph-countyfair/commits/615bacf62e7aae0d047f215920cb480c9afa7bf3/versions/7/d/1/6/9/ruamel_yaml.json
• gh-194 was opened and closed in the time frame between commits from https://github.com/regro/cf-graph-countyfair/commits/615bacf62e7aae0d047f215920cb480c9afa7bf3/version_pr_info
• version_pr_info has just been updated only just a few minutes ago: https://github.com/regro/cf-graph-countyfair/commits/03ffce948846d737f75356475f54d41383c75b83/version_pr_info/7/d/1/6/9/ruamel_yaml.json

... but this is just speculation on my part since I'm not deeply familiar with the autotick workflows :shrug:.