Skip to content

Conversation

@forsyth2
Copy link
Collaborator

Summary

Objectives:

  • Bump to 0.2.0rc2

Small Change

  • To merge, I will use "Squash and merge". That is, this change should be a single commit.
  • Logic: I have visually inspected the entire pull request myself.
  • Pre-commit checks: All the pre-commits checks have passed.

@forsyth2 forsyth2 self-assigned this Oct 16, 2025
@forsyth2 forsyth2 added priority: high High priority task (for next release) Update version Code specifically to update the version labels Oct 16, 2025
@forsyth2 forsyth2 marked this pull request as ready for review October 16, 2025 23:07
@forsyth2 forsyth2 merged commit 5a88374 into main Oct 16, 2025
5 checks passed
@forsyth2 forsyth2 deleted the v0.2.0rc2 branch October 16, 2025 23:07
@forsyth2
Copy link
Collaborator Author

Release process notes:

Step 1: testing

cd ~/ez/zppy-interfaces
git status
# branch: test_unified_1.12.0rc1_chrysalis
# nothing to commit
git fetch upstream main
git checkout main
git reset --hard upstream/main
git log
# Last commit: Further pcmdi_diags updates (#41)
# Good, matches https://github.com/E3SM-Project/zppy-interfaces/commits/main
rm -rf build
conda clean --all --y
conda env create -f conda/dev.yml -n zi-main-20251016
conda activate zi-main-20251016
python -m pip install .
pytest tests/unit/global_time_series/test_*.py
# 10 passed in 29.55s
pytest tests/unit/pcmdi_diags/test_*.py
# 7 passed, 1 warning in 20.27s

See discussion on warnings at PCMDI/pcmdi_metrics#1330 (comment).

Step 2: Bump versions

Step 2a: Confluence

Update https://e3sm.atlassian.net/wiki/spaces/DOC/pages/129732419/Packages+in+the+E3SM+Unified+conda+environment:

  • E3SM Unified 1.11.0: zppy-interfaces v0.1.1
  • E3SM Unified 1.11.1: zstash v0.1.2
  • E3SM Unified 1.12.0: zstash v0.2.0 (We updated this when we made rc1)

Step 2b: zppy-interfaces repo

cd ~/ez/zppy-interfaces
git status
# Check for uncommitted changes
git fetch upstream main
git checkout -b v0.2.0rc2 upstream/main
tbump 0.2.0rc2 --no-tag
# Error: Invalid config: 'Key "tbump" does not exist.'
# 
# We'll need to update manually
git grep -n "0\.2\.0rc1"
# zppy_interfaces/version.py:1:__version__ = "0.2.0rc1"
#
# Yes, this matches up with changes in https://github.com/E3SM-Project/zppy-interfaces/pull/24
# Make corresponding changes here
git add -A
pre-commit run --all-files
git commit -m "Bump to 0.2.0rc2"
git push upstream v0.2.0rc2
# Follow example of https://github.com/E3SM-Project/zppy-interfaces/pull/39
# Create, add "Update version" label" to, and merge https://github.com/E3SM-Project/zppy-interfaces/pull/43
git checkout main
git fetch upstream
git reset --hard upstream/main
git tag -a v0.2.0rc2 -m "v0.2.0rc2"
# Delete the branch from the tbump step. Otherwise, the push command won't work.
git branch -D v0.2.0rc2
git push upstream v0.2.0rc2

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

Step 2c: zppy-interfaces-feedstock repo

cd ~/zppy-interfaces-feedstock
curl -sL https://github.com/E3SM-Project/zppy-interfaces/archive/v0.2.0rc2.tar.gz | openssl sha256
# SHA2-256(stdin)= ace4d6571bd3bd65e38b304cc1ae014ae2fb351f038e6abd8becc3a8941dea2d
git status
# Check for uncommitted changes
git fetch upstream dev
git checkout -b v0.2.0rc2 upstream/dev
emacs recipe/meta.yaml
# In `recipe/meta.yaml`, update the version and sha256 (and the build number if needed):
# {% set version = "0.2.0rc2" %}
# sha256: ... # The sha256 from the previous step
# number: 0 # build >>> number should always be 0
#
# Also appear to need to edit a number of dependency versions...
git add -A
git commit -m "v0.2.0rc2"
git push forsyth2 v0.2.0rc2
# Follow example of https://github.com/conda-forge/zppy-interfaces-feedstock/pull/3

Created conda-forge/zppy-interfaces-feedstock#5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority: high High priority task (for next release) Update version Code specifically to update the version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants