Skip to content

Latest commit

 

History

History
39 lines (20 loc) · 1.35 KB

RELEASE.markdown

File metadata and controls

39 lines (20 loc) · 1.35 KB
Raw

How to Release

Create a stable release

  1. Create a BLADE jira ticket for the new release

  2. Create a new branch based on ticket

  3. Run gradlew prepareRelease

  4. Commit the changes

  5. Generate changelog./gradlew -b changelogs-sdk.gradle buildChangelogs

  6. Commit the changelog

  7. Create PR on liferay/liferay-blade-cli repo from this branch

  8. If the PR passes all the tests, merge the PR to master.

  9. Generate a new tag based on the new version git tag 4.1.2

  10. Push the tags to upstream git push --tags upstream

By merging this PR to master, and since all of the versions of the components are set to stable versions, this will cause the GitHub workflow to release the binaries to nexus which will cause the existing blade CLIs to report a new stable release/version is available and anyone who runs blade update will get the new version. See Create a snapshot release right after releasing a stable version.

Create a snapshot release

  1. Create a new branch based for updating to new snapshot release

  2. Run gradlew prepareSnapshot

  3. Commit the changes using the release ticket

  4. Create a PR

  5. If it passes CI, merge the PR

By merging this PR to master with all the version numbers for components that end in -SNAPSHOT this will cause the GitHub workflow to release the binaries for a new snapshot release.