Skip to content

Latest commit

 

History

History
57 lines (41 loc) · 1.4 KB

RELEASE.md

File metadata and controls

57 lines (41 loc) · 1.4 KB

RELEASE

For core contributors, when you want to do a release, follow these steps:

Go into your local project.

Be sure to have an origin and upstream. The origin is your fork. The upstream is the official project. You should have something like that:

➜ git remote -v
origin	[email protected]:pascalgrimaud/prettier-java.git (fetch)
origin	[email protected]:pascalgrimaud/prettier-java.git (push)
upstream	[email protected]:jhipster/prettier-java (fetch)
upstream	[email protected]:jhipster/prettier-java (push)

Update main branch and release branch in your fork.

git checkout release
git fetch upstream
git rebase upstream/release

git checkout main
git rebase upstream/main

Be sure your dependencies is up-to-dated:

yarn

In main branch, launch the release, and answer the questions. It will:

  • change the version (patch, minor or major, accordingly to what you choose)
  • tag the version
  • push main branch to upstream
  • push the tag to upstream
yarn run lerna:version

Then, if everything looks OK, merge the main branch to the release branch locally, then push the release branch:

git checkout release
git merge main
git push upstream/release

The Azure Pipelines will build the release branch and publish to NPM. Then, you need to check if the release is correctly published at: