Add a release workflow

.github/workflows/release.yaml

@@ -0,0 +1,56 @@
+# Makes an automated release
+#
+# To trigger this workflow, ensure the CHANGELOG is up to date, then push the commit 
+# to be released to a `release/*` branch.
+#
+# e.g.
+#     git checkout -b release/v1.0.0
+#     git push
+#
+name: Release
+
+on:
+  push:
+    branches: [release/*]
+
+jobs:
+  create-release:
+    name: Create GitHub Release and tag
+    runs-on: ubuntu-latest
+    environment: Release
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v2
+      - uses: cucumber-actions/[email protected]
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+
+  publish-rubygem:
+    name: Publish Ruby Gem
+    needs: create-release
+    runs-on: ubuntu-latest
+    environment: Release
+      - uses: actions/checkout@v2
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: 3.0.2
+          bundler-cache: true
+      - uses: cucumber-actions/[email protected]
+        with:
+          rubygems_api_key: ${{ secrets.RUBYGEMS_API_KEY }}
+          working_directory: 'ruby'
+
+  publish-npm:
+    name: Publish NPM package
+    needs: create-release
+    runs-on: ubuntu-latest
+    environment: Release
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '16'
+      - uses: cucumber-actions/[email protected]
+        with:
+          npm-token: ${{ secrets.NPM_TOKEN }}
+          working-directory: 'javascript'

CONTRIBUTING.md

@@ -0,0 +1,35 @@
+Everyone contributing to this repo is expected to abide by the [Cucumber Community Code of Conduct](https://cucumber.io/conduct).
+
+## Making a release
+
+There are two parts to making a release. First, prepare the release, then make the release.
+
+### Preparing a release
+
+Anyone with commit rights to `main` can prepare a release.
+
+To make these steps easier, can use the [`changelog`](https://github.com/rcmachado/changelog) tool.
+
+First, make sure your changes are detailed in the `Unreleased` section of the [CHANGELOG](./CHANGELOG.md) file.
+
+Then, use [semver](https://semver.org/) to pick a version for the next release.
+
+    read $next_release
+
+Modify the changelog:
+
+    changelog release $next_release -o CHANGELOG.md
+
+Commit and push
+
+     git add .
+     git commit -m "Release $next_release"
+
+### Making a release
+
+Only people with rights to push to the `release/*` branches can make releases.
+
+    git checkout -b release/v$next_release
+    git push
+
+This will trigger the [`release` workflow](https://github.com/cucumber/cucumber-expressions/actions/workflows/release.yaml).