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
Release notes will generate a list of issues that have been fixed between tags as well as all PRs that have been merged. If there is a pre-release build or any tag between the last release and the current release it will only show the differences from those tags. See example below.
Example
Consider you have already released v1.0.0 and are working on v1.1.0. The repository only has a tagged commit for v1.0.0. When you create a beta or release candidate build you may use the tag v1.1.0-RC0. This will kick off its own release notes process. When it is time to make the final v1.1.0 release it will only have the issues listed that were completed after v1.1.0-RC0 when it should have all issues between tag v1.0.0 and v1.1.0.
The text was updated successfully, but these errors were encountered:
Description
Release notes will generate a list of issues that have been fixed between tags as well as all PRs that have been merged. If there is a pre-release build or any tag between the last release and the current release it will only show the differences from those tags. See example below.
Example
Consider you have already released
v1.0.0
and are working onv1.1.0
. The repository only has a tagged commit forv1.0.0
. When you create a beta or release candidate build you may use the tagv1.1.0-RC0
. This will kick off its own release notes process. When it is time to make the finalv1.1.0
release it will only have the issues listed that were completed afterv1.1.0-RC0
when it should have all issues between tagv1.0.0
andv1.1.0
.The text was updated successfully, but these errors were encountered: