Bump to 3.2.0rc2

[forsyth2]

Bump to 3.2.0rc2

[forsyth2]

Release process notes:

• rc1: Bump to 3.2.0rc1 #813
• Releases: https://github.com/E3SM-Project/zppy/releases

Step 1: testing

The fixes of rc8 were tested in that PR. More complete testing will be done by testing this RC, rc2 in E3SM Unified 1.13.0rc9.

Step 2: Bump versions

Step 2a: Confluence

Already updated https://e3sm.atlassian.net/wiki/spaces/DOC/pages/129732419/Packages+in+the+E3SM+Unified+conda+environment, in #813

Step 2b: zppy repo

cd ~/ez/zppy
git status # Check for uncommitted changes
git fetch upstream main
git checkout -b v3.2.0rc2 upstream/main
nersc_conda # Activate conda env
conda activate zppy-fixes-of-rc8-20260505 # Just activate some zppy dev env so we have tbump
tbump 3.2.0rc2 --no-tag
# Creates commit, but doesn't push it (because branch isn't named `main`)
git diff HEAD^ HEAD | cat
# Yes, these match up with changes in https://github.com/E3SM-Project/zppy/pull/813
git push upstream v3.2.0rc2
# Create, and "Update version" label" to, and merge https://github.com/E3SM-Project/zppy/pull/816, delete branch on GitHub

git checkout main
git fetch upstream
git reset --hard upstream/main
git tag -a v3.2.0rc2 -m "v3.2.0rc2"
# Delete the branch from the tbump step. Otherwise, the push command won't work.
git branch -D v3.2.0rc2
git push upstream v3.2.0rc2

v3.2.0rc2 now appears on Tags but not on Releases. Good, this is expected.

Step 2c: zppy-feedstock repo

cd ~/zppy-feedstock
curl -sL https://github.com/E3SM-Project/zppy/archive/v3.2.0rc2.tar.gz | openssl sha256
# SHA2-256(stdin)= 62e97ab6512bc7407f5810c6c595f320758e03a9ad01ca6ee24f7065fef07248
git status # Check for uncommitted changes
git fetch upstream dev
git checkout -b v3.2.0rc2 upstream/dev
emacs recipe/recipe.yaml
# Update the version and sha256 (and the build number if needed):
# version: 3.2.0rc2
# sha256: ... # The sha256 from the previous step
# number: 0 # build >>> number should always be 0

# Check https://github.com/E3SM-Project/zppy/compare/v3.2.0rc1...v3.2.0rc2
# If there are changes in dependencies there (e.g., in a `dev.yml`),
# You'll want to include them in this feedstock PR too.

# No relevant changes to add.

git add -A
git commit -m "v3.2.0rc2"
git push forsyth2 v3.2.0rc2

Created conda-forge/zppy-feedstock#37