...
| Tip | ||||
|---|---|---|---|---|
You have not pushed your commits to a branch on Github yet (See push changes to github). If you are NOT working on a past version release, i.e. you are releasing the latest version of the software. Now is a good time to push your main branch onto the repository. This should always be a fast-forward push and should never require a "force push"
Now browsing Github you should see two commits with "[maven-release-plugin]" in the label. See examples in Verify local updates On some repositories (like fcrepo/fcrepo) you are not able to push directly on to main, in this case you should push your release branch up to origin
Then open a pull request from the release branch to main, it will have the 2 release related commits. This pull request should NOT be squash merged. -- If you are working on a past version, see Push Release Branch to Maintenance |
...
| Anchor | ||||
|---|---|---|---|---|
|
...
- Changing from SNAPSHOT version to release version. Something like [maven-release-plugin] prepare release $REPO-$CURR
- Changing from release version to next development version. Something like [maven-release-plugin] prepare for next development iteration
If this appears correct, you can push your release branch on to the maintenance branch.
...