[warning] failed package validation and/or copy for commit 7dd8f77c64f57f4f0ad118df3f8f0ef18cfdbe16

Hi @conda-forge/jfrog-cli! 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](https://conda-forge.org/status/) 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](https://github.com/conda-forge/admin-requests?tab=readme-ov-file#add-a-package-output-to-a-feedstock).
- 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](https://github.com/conda-forge/admin-requests?tab=readme-ov-file#add-a-package-output-to-a-feedstock)
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](https://github.com/conda-forge/admin-requests?tab=readme-ov-file#reset-your-feedstock-token).

If you have any issues or questions, you can find us on Zulip in the
community [channel](https://conda-forge.zulipchat.com/#narrow/channel/457337-general) or you can bump us right here.

copied (did this package get copied to the production channel?):
- **win-64/jfrog-cli-2.95.0-h11686cb_0.conda**: False

error messages:
- output win-64/jfrog-cli-2.95.0-h11686cb_0.conda does not have a valid checksum or correct label on cf-staging

Start with the conda-forge status page and the reported win-64 artifact error, then check whether the staging package has a valid checksum and label. The issue is resolved when jfrog-cli-2.95.0-h11686cb_0.conda copies from cf-staging to production; the listed retry, rerender, or admin-request paths describe possible next steps.

Written by the indexing model from the issue text.