Skip to content

Commit

Permalink
Merge pull request OpenGeoscience#1092 from OpenGeoscience/beta
Browse files Browse the repository at this point in the history
fix: Add semantic release.
  • Loading branch information
manthey authored Jun 9, 2021
2 parents 3dc5c77 + 94b38eb commit 63eac77
Show file tree
Hide file tree
Showing 4 changed files with 13,598 additions and 8,399 deletions.
12 changes: 7 additions & 5 deletions .github/workflows/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -103,20 +103,22 @@ jobs:
dist/built/geo.lean.js
dist/built/geo.lean.min.js
deploy-npm:
if: ${{ startswith(github.ref, 'refs/tags/') }}
# if: ${{ startswith(github.ref, 'refs/tags/') }}
needs: build
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
with:
node-version: 15.x
- run: npm ci
- name: Import artifacts
uses: actions/download-artifact@v2
with:
name: dist
path: dist
- uses: JS-DevTools/npm-publish@v1
with:
token: ${{ secrets.NPM_TOKEN }}
dry-run: true
- name: Release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
run: npx semantic-release
10 changes: 3 additions & 7 deletions docs/developers.rst
Original file line number Diff line number Diff line change
Expand Up @@ -104,12 +104,8 @@ screen output is used, the browser must be running on the same machine as the
Release Process
---------------

To make a new GeoJS release:
GeoJS is now using semantic-release. Prefix the first line of commit messages with an appropriate prefix, such as ``fix``, ``perf``, ``feat``, ``docs``, ``ci``, ``refactor``, ``style``, ``test``, ``build``, or ``BREAKING CHANGE``. See `<https://github.com/semantic-release/semantic-release/blob/master/CONTRIBUTING.md#type>`_ for details.

- Update the version number in package.json.
- Update the CHANGELOG.md file with changes since the last release
- Commit to GitHub and merge to master
- Tag the commit on GitHub with a tag of the form vX.Y.Z (e.g., v0.17.0).
- After the release appears on GitHub, update the release notes with the changes since the last release.
When the PR is merged to master, a new release will be made if appropriate.

Tagging a commit on the master branch will trigger a build on CI, at the end of which the new version will be published to npm and the build artifacts will be pushed to the tagged version on GitHub.
After the release appears on GitHub, update the ``CHANGELOG.md`` file to reflect these changes.
Loading

0 comments on commit 63eac77

Please sign in to comment.