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
- The "New Version Spec" will usually be the full version (e.g. 0.7.1). Repos using `tbump` can also use the "next"
44
+
- The "New Version Spec" will usually be the full version (e.g. 0.7.1). Repos using `tbump` can also use the "next" or "patch"
45
45
option, which will bump the micro version (or the build version in the case of a prerelease). The "minor" option allows projects using "tbump" to bump
46
-
to the next minor version directly.
46
+
to the next minor version directly. Note: The "next" and "patch" options
47
+
are not available when using dev versions, you must use explicit versions
48
+
instead.
47
49
- Use the "since" field to select PRs prior to the latest tag to include in the release
48
50
- Type "true" in the "since the last stable git tag" if you would like to include PRs since the last non-prerelease version tagged on the target repository and branch.
49
51
- The workflow will use the GitHub API to find the relevant pull requests and make an appropriate changelog entry.
0 commit comments