Bump to 1.6.0

[forsyth2]

Bump to 1.6.0

[forsyth2]

Providing a reference for future production releases. Here are the steps completed for this release:

Production release of zstash v1.6.0

References:

• Somewhat outdated docs on how to make a release: https://docs.e3sm.org/zstash/_build/html/main/dev_guide/release.html
• Notes from the production release of v1.5.0: Bump to 1.5.0 #403 (comment)
• Notes from the last RC (v1.6.0rc3): Bump to 1.6.0rc3 #443 (comment)

Step 1: setup/testing

We can skip the testing step, since that has been thoroughly covered here: #439 (comment)

Step 2: Bump versions

Step 2a: Confluence

Confirm version numbers are correct on https://e3sm.atlassian.net/wiki/spaces/DOC/pages/129732419/Packages+in+the+E3SM+Unified+conda+environment:

• E3SM Unified 1.12.0: zstash v1.5.0
• E3SM Unified 1.13.0: zstash v1.6.0

Step 2b: zstash repo

Bumping the Version

# On Perlmutter
cd ~/ez/zstash
git status # Confirm there's no uncommitted changes
git fetch upstream main
git checkout -b v1.6.0 upstream/main
git log --oneline | head -n 9
# 2469f4a Bump to 1.6.0rc3 (#443)
# b985d89 Merge pull request #442 from E3SM-Project/fixes-of-unified-rc5
# 6848913 Add Improv support
# b04f6ca Fix hsi calls in follow_symlinks.sh
# a0b8df3 Fix hsi calls in test_update_non_empty_hpss.bash
# b260147 Bump to 1.6.0rc2
# 4e1dad2 Isolate hsi calls (#440)
# ed6a77e Bump to 1.6.0rc1 (#438)
# 601eb4b Add Bebop support (#437)

# Good, matches https://github.com/E3SM-Project/zstash/commits/main/

# Set up conda so we can use tbump:
nersc_conda # Activate conda
conda env list # Just pick any zstash dev env, so we have tbump available
conda activate zstash-profile-unifiedrc5-20260414

tbump 1.6.0 --no-tag
git log --oneline | head -n 2
# 8e41931 Bump to 1.6.0
# 2469f4a Bump to 1.6.0rc3 (#443)
git push upstream v1.6.0
# Create, add "Update version" label" to: https://github.com/E3SM-Project/zstash/pull/444

# Compare https://github.com/E3SM-Project/zstash/pull/444/changes with rc3's diff:
# https://github.com/E3SM-Project/zstash/pull/443/changes
# Looks good

# Wait for CI checks to pass, merge, delete branch: https://github.com/E3SM-Project/zstash/pull/444

Releasing on GitHub: production releases

1. Draft a new release here.
   • Click "Draft a new release".
2. Set Tag version to v1.6.0, including the “v”. @Target should be main.
   • Tag > Create new tag > v.1.6.0
3. Set Release title to v1.6.0, including the “v”.
4. Use Describe this release to summarize the changelog.
   • "Summary of changes": The high-level summary
   • "Full list of changes": The categorized log of commits
5. Make sure "Set as the latest release" is checked.
6. Click Publish release.
   • Tag created here.
   • Unlike the RCs, v1.6.0 now appears on both Tags and Releases.
7. CI/CD release workflow is automatically triggered.
   • https://github.com/E3SM-Project/zstash/actions/runs/25877612203 is just for the docs. Clicking "Publish release" is responsible for triggering the bot PR on conda-forge.

Step 2c: zstash-feedstock repo

Releasing on conda-forge: production releasess

TODO: wait for the bot PR

1. Wait for a bot PR to come up automatically on conda-forge after the GitHub release. This can happen anywhere from 1 hour to 1 day later. (Alternative: open an issue with the bot command: @conda-forge-admin, please update version and the PR will opened.)
   • Check https://github.com/conda-forge/zstash-feedstock/pulls
   • See ENH: update package version to 1.5.0 conda-forge/zstash-feedstock#23
2. Complete any requirements to merge the PR.
3. Check the https://anaconda.org/conda-forge/zstash/files/manage page to view the newly updated package. Check it has the main label.

[forsyth2]

Relevant conda-forge PR: conda-forge/zstash-feedstock#28