v1.5.0rc2

[forsyth2]

Checklist

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

[forsyth2]

@conda-forge-admin, please rerender

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

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

For recipe/meta.yaml:

• ℹ️ License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/18576500435. Examine the logs at this URL for more detail.}

[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/18576511626. Examine the logs at this URL for more detail.}

[forsyth2]

@andrewdnolan @xylar This PR is ready for review.

It's a pretty minimal update for zstash, adding just two PRs, neither of which are particularly user-facing:

• Fix tbump E3SM-Project/zstash#390
• Bump to 1.5.0rc2 E3SM-Project/zstash#392

[xylar]

@forsyth2, could you explain to me why this release candidate is needed? It seems like there are no meaningful code changes since rc1.

[xylar]

It's a pretty minimal update for zstash, adding just two PRs, neither of which are particularly user-facing

I see, missed this. I would go further to say that no changes since the last RC have any impact on the package itself and aren't worth the time of making a RC. Let's focus RCs only on code changes that need testing.

[forsyth2]

could you explain to me why this release candidate is needed?

I suppose it's not strictly needed. I just figured I might as well include the latest change if we're making rc2 anyway. If it just creates more work, we can drop it.

[xylar]

Yes, I would put this in the category of needless work, especially for you. Let's drop it.