You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.rst
+75Lines changed: 75 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -141,6 +141,81 @@ installation and the test file you are trying to run.
141
141
142
142
Note that any tests that require Docker will obviously fail.
143
143
144
+
Creating a Release
145
+
------------------
146
+
147
+
- Before creating a new branch, make sure your local repository is up to date:
148
+
149
+
.. code-block:: bash
150
+
151
+
git pull
152
+
153
+
This ensures you have the latest changes from the default branch (usually ``main`` or ``develop``).
154
+
155
+
- Create a new branch for the release:
156
+
157
+
.. code-block:: bash
158
+
159
+
git checkout -b release/0.10
160
+
161
+
**Important:**
162
+
The release branch must only include the **major** and **minor** version numbers.
163
+
Do not include the patch version.
164
+
For example, use ``release/0.10``, not ``release/0.10.0``.
165
+
166
+
- If creating a **patch release**, do not create a new branch.
167
+
Instead, reuse the existing ``release/0.10`` branch.
168
+
169
+
- Update the version number in ``pyproject.toml``:
170
+
171
+
If the current version is:
172
+
173
+
.. code-block:: toml
174
+
175
+
version = "0.10.0.dev0"
176
+
177
+
bump it to:
178
+
179
+
.. code-block:: toml
180
+
181
+
version = "0.10.0"
182
+
183
+
- **Important:**
184
+
Every time you create a development (``dev``) release, you should first release the corresponding stable version on PyPI before bumping the development version.
185
+
186
+
For example:
187
+
188
+
- If you are at ``0.10.0.dev0``, first release ``0.10.0`` on PyPI.
189
+
- Then, after the release, bump the version to ``0.10.1.dev0``.
190
+
191
+
Otherwise, it may feel confusing to have a ``dev`` version without a corresponding stable release.
192
+
193
+
- Create a commit for the version bump:
194
+
195
+
.. code-block:: bash
196
+
197
+
git commit -am "MAINT: Bump version to v0.10.0"
198
+
199
+
- Then push the branch:
200
+
201
+
.. code-block:: bash
202
+
203
+
git push --set-upstream origin release/0.10
204
+
205
+
- Create a tag for the release:
206
+
207
+
.. code-block:: bash
208
+
209
+
git tag v0.10.0
210
+
git push origin v0.10.0
211
+
212
+
**Important:**
213
+
The release tag must always include the full **major.minor.patch** version number.
214
+
Always include the ``v`` prefix.
215
+
For example, use ``v0.10.0``, not ``v0.10``.
216
+
Creating and pushing the tag automatically triggers the release workflow in GitHub Actions.
217
+
218
+
144
219
Dependencies
145
220
------------
146
221
To use PyDynamicReporting, you must have a locally installed and licensed copy
0 commit comments