Patch amrex-26.04 to fix incorrect release number in CHANGES.md

[WeiqunZhang]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)

Patch amrex-26.04 to fix incorrect release number in CHANGES.md

[WeiqunZhang]

What to do with build number in this situation?

[conda-forge-admin]

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

[WeiqunZhang]

I guess should bump up the build number.

[WeiqunZhang]

@conda-forge-admin, please rerender

[conda-forge-admin]

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/conda-forge-webservices/actions/runs/24008639366. Examine the logs at this URL for more detail.}

[ax3l]

What to do with build number in this situation?

Since conda-forge usually does not purge published artifacts (needs admin involvement), the build number will prioritize the new artifacts we publish now, solving the issue (and avoiding breaking reproducible envs someone might have on disk, e.g., for minor other issues).

[ax3l]

Thank you, looks great!