@@ -5,7 +5,6 @@ In this guide, we'll cover:
55
66* Preparing The Code For Release
77* Creating A Release On GitHub
8- * Updating The sha256
98* Releasing The Software On Anaconda
109* Creating a New Version of the Documentation
1110
@@ -106,48 +105,6 @@ Remember to write a description.
106105
1071063. Click "Publish release".
108107
109- Updating The sha256
110- --------------------
111-
112- 1. Download "Source code (.tar.gz)" from the `GitHub releases page <https://github.com/E3SM-Project/zstash/releases >`_.
113-
114- 2. Run ``shasum -a 256 `` on this file. For example:
115-
116- ::
117-
118- shasum -a 256 zstash-0.4.1.tar.gz
119-
120- 3. On your machine, pull the latest version of the code.
121- This will have the ``conda/meta.yaml `` we edited in the first section.
122-
123- ::
124-
125- git checkout master
126- git pull <upstream-origin> master
127-
128- Or:
129- ::
130-
131- git fetch <upstream-origin> master
132- git checkout -b <branch-name> <upstream-origin>/master
133-
134- 4. Change ``sha256 `` in ``conda/meta.yaml `` to the result of step 2.
135-
136- 5. Commit and push your changes.
137-
138- ::
139-
140- git commit -am 'Edit sha256 for v0.4.1'
141- git push <upstream-origin> master
142-
143- Or:
144-
145- ::
146-
147- git commit -am 'Edit sha256 for v0.4.1'
148- git push <fork-origin> <branch-name>
149- # Create pull request for the master branch
150-
151108Releasing The Software On Anaconda
152109----------------------------------
153110
@@ -158,6 +115,9 @@ This triggers the CI/CD workflow that handles Anaconda releases.
158115
1591163. Check the https://anaconda.org/e3sm/zstash page to view the newly updated package.
160117
118+ * Release candidates are assigned the ``e3sm_dev `` label
119+ * Production releases are assigned the ``main `` label
120+
1611214. Notify the maintainers of the unified E3SM environment about the new release on the
162122`E3SM Confluence site <https://acme-climate.atlassian.net/wiki/spaces/WORKFLOW/pages/129732419/E3SM+Unified+Anaconda+Environment >`_.
163123Be sure to only update the ``zstash `` version number in the correct version(s) of
0 commit comments