Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump to 3.0.0rc1 #660

Merged
merged 1 commit into from
Jan 17, 2025
Merged

Bump to 3.0.0rc1 #660

merged 1 commit into from
Jan 17, 2025

Conversation

forsyth2
Copy link
Collaborator

@forsyth2 forsyth2 commented Jan 17, 2025

Bump to 3.0.0rc1

Small Change

  • To merge, I will use "Squash and merge". That is, this change should be a single commit.

@forsyth2 forsyth2 added the Update version Code specifically to update the version label Jan 17, 2025
@forsyth2 forsyth2 self-assigned this Jan 17, 2025
@forsyth2 forsyth2 merged commit f19232d into main Jan 17, 2025
4 checks passed
@forsyth2 forsyth2 deleted the v3.0.0rc1 branch January 17, 2025 01:22
@forsyth2
Copy link
Collaborator Author

Following https://docs.e3sm.org/zppy/_build/html/main/dev_guide/release.html:

git status # Make sure no changes will be carried over
git fetch upstream main
git checkout -b v3.0.0rc1 upstream/main
tbump 3.0.0rc1 --no-tag
git push upstream v3.0.0rc1
# Create and merge https://github.com/E3SM-Project/zppy/pull/660

git fetch upstream
git checkout -b  main upstream/main
git tag -a v3.0.0rc1 -m "v3.0.0rc1"
# Delete the branch from the tbump step. Otherwise, the push command won't work.
git branch -D v3.0.0rc1
git push upstream v3.0.0rc1
# v3.0.0rc1 now appears on https://github.com/E3SM-Project/zppy/tags

cd ~/zppy-feedstock/
curl -sL https://github.com/E3SM-Project/zppy/archive/v3.0.0rc1.tar.gz | openssl sha256
# SHA2-256(stdin)= 7f59f3c7a17a81fc4dffef368d1e26b21a5f70c976d0700196368e69ca8dd0e7
git fetch upstream dev
git checkout -b v3.0.0rc1 upstream/dev
# In `recipe/meta.yaml`, update the version and sha256 (and the build number if needed):
{% set version = "3.0.0rc1" %} # Set to your version
sha256: ... # The sha256 from the previous step
number: 0 # build > number should always be 0
git add -A
git commit -m "v3.0.0rc1"
git push forsyth2 v3.0.0rc1
# Create https://github.com/conda-forge/zppy-feedstock/pull/18
# TODO: once that merges, look at https://anaconda.org/conda-forge/zppy

@xylar
Copy link
Contributor

xylar commented Jan 17, 2025

@forsyth2, I have a question here. Shouldn't zppy-interfaces have been added as a dependency of zppy here?

@forsyth2
Copy link
Collaborator Author

Shouldn't zppy-interfaces have been added as a dependency of zppy here?

Ah, this is a good question, but the answer is no. Similar to how main is just another branch as far as git is concerned, zppy-interfaces is just another workflow package as far as zppy is concerned. Notice zppy doesn't have dependencies on NCO, e3sm_to_cmip, e3sm_diags, mpas_analysis, or ilamb either. Rather, those packages just need to exist in whatever environment is specified by environment_commands. They don't need to exist in the environment zppy itself is run from.

@xylar
Copy link
Contributor

xylar commented Jan 17, 2025

Ah, right, sorry. Thanks for reminding me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Update version Code specifically to update the version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants