[warning] failed package validation and/or copy for commit 9c131e5aee61a9f8e808a01303bed5248ce4d87e

[conda-forge-webservices]

Hi @conda-forge/python-chromedriver-binary! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the
staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock
token or your feedstock not having permissions to upload the given package.
Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• First check the conda-forge status page for any infrastructure outages.
• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request that any new packages be added to the allowed outputs for the feedstock
  via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.).
  In this case, you can use our admin-requests repo
  to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax.
  Output packages that match these patterns will be automatically registered for your feedstock.
• Request a feedstock token reset via our admin-requests repo.

If you have any issues or questions, you can find us on Zulip in the
community channel or you can bump us right here.

output validation (is this package allowed for your feedstock?):

• noarch/python-chromedriver-binary-137.0.7118.2.0-pyhbf943cc_0.conda: False

copied (did this package get copied to the production channel?):

• noarch/python-chromedriver-binary-137.0.7118.2.0-pyhbf943cc_0.conda: False

error messages:

• output noarch/python-chromedriver-binary-137.0.7118.2.0-pyhbf943cc_0.conda does not have a valid checksum or correct label on cf-staging

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.

[conda-forge-webservices]

Hi @conda-forge/python-chromedriver-binary! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's packages did not copy from the
staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock
token or your feedstock not having permissions to upload the given package.
Below we have put some information about the failure to help you debug it.

Common ways to fix this problem include:

• First check the conda-forge status page for any infrastructure outages.
• Retry the package build and upload by pushing an empty commit to the feedstock.
• Rerender the feedstock in a PR from a fork of the feedstock and merge.
• Request that any new packages be added to the allowed outputs for the feedstock
  via our admin-requests repo.
• In rare cases, the package name may change regularly in a well defined way (e.g., libllvm18, libllvm19, etc.).
  In this case, you can use our admin-requests repo
  to add a glob pattern that matches the new package name pattern. We use the Python fnmatch module syntax.
  Output packages that match these patterns will be automatically registered for your feedstock.
• Request a feedstock token reset via our admin-requests repo.

If you have any issues or questions, you can find us on Zulip in the
community channel or you can bump us right here.

output validation (is this package allowed for your feedstock?):

• noarch/python-chromedriver-binary-137.0.7118.2.0-pyh5379f07_0.conda: False

copied (did this package get copied to the production channel?):

• noarch/python-chromedriver-binary-137.0.7118.2.0-pyh5379f07_0.conda: False

error messages:

• output noarch/python-chromedriver-binary-137.0.7118.2.0-pyh5379f07_0.conda does not have a valid checksum or correct label on cf-staging

To fix package package output validation errors, follow the instructions above to add new package outputs to your feedstock or to add your feedstock+packages to the allow list for automatic registration.