Skip to content

Latest commit

 

History

History
28 lines (23 loc) · 1.56 KB

RELEASE.md

File metadata and controls

28 lines (23 loc) · 1.56 KB

Release v2

All changes have to be made on «master» branch.

  1. Update the package version by running npm version patch|minor. This command returns a new package version. Let assume it's 2.3.4
  2. Push changes to github and merge them to the «master» branch
  3. Go to https://github.com/2gis/mapgl-gltf/releases/new
  4. Click the «Choose tag» button and create a new tag according to the version in package.json, for example v2.3.4
  5. Make sure the release target is the «master» branch
  6. Paste the release tag into the «Release title» field, for example v2.3.4
  7. Add a release description
  8. Click the «Publish release» button
  9. Go to https://github.com/2gis/mapgl-gltf/actions and wait for completing the release workflow

Release v1

All changes have to be made on «plugin-v1» branch.

  1. Update the package version by running npm version patch|minor. This command returns a new package version. Let assume it's 1.2.3
  2. Push changes to github and merge them to the «plugin-v1» branch
  3. Go to https://github.com/2gis/mapgl-gltf/releases/new
  4. Click the «Choose tag» button and create a new tag according to the version in package.json, for example v1.2.3
  5. Make sure the release target is the «plugin-v1» branch
  6. Paste the release tag into the «Release title» field, for example v1.2.3
  7. Add a release description
  8. Unset the «Set as the latest release» checkbox because version 1 release can't be the latest
  9. Click the «Publish release» button
  10. Go to https://github.com/2gis/mapgl-gltf/actions and wait for completing the release workflow