Skip to content

Commit

Permalink
Update making_release_from_repo.md
Browse files Browse the repository at this point in the history
  • Loading branch information
fcollonval committed Apr 19, 2024
1 parent a6deb2c commit 42649ed
Showing 1 changed file with 2 additions and 7 deletions.
9 changes: 2 additions & 7 deletions docs/source/get_started/making_release_from_repo.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,13 +20,8 @@ already uses Jupyter Releaser using workflows on its own repository.

![Prep Release Workflow Dialog](../images/prep_release_repo.png)

- The "New Version Spec" will usually be the full version (e.g. 0.7.1). Repos using `tbump` can also use:

- "next" or "patch" option, which will bump the micro version (or the build version in the case of a prerelease).
Note: The "next" and "patch" options are not available when using dev versions, you must use explicit versions
instead.
- "minor" option, which will bump to the next minor version directly.
- "release" option, which will start making prereleases (a0, a1...)
- The "New Version Spec" will usually be the full version (e.g. 0.7.1).
Repos using `hatch` can also use [segments](https://hatch.pypa.io/latest/version/#supported-segments) such as _patch_, _minor_, _alpha_,... .

- Use the "since" field to select PRs prior to the latest tag to include in the release

Expand Down

0 comments on commit 42649ed

Please sign in to comment.