diff --git a/docs/development.md b/docs/development.md index 9b885447..5b547a2b 100644 --- a/docs/development.md +++ b/docs/development.md @@ -25,4 +25,4 @@ Releases are done manually, for now: 1. Ensure that the build is up to date with `npm run build`. It's also good to ensure you have the correct dependencies installed by running `npm install` before you build. 1. Bump the [package.json](/package.json#L3) and [package-lock.json](/package-lock.json#L3) version numbers and commit them. I like to do this with `npm version {major,minor,patch} --no-git-tag-version`. This will bump the version numbers but let you manually commit and tag, yourself. 1. Update documentation (including updated version numbers). -1. Tag main with the new version number and create a GitHub release. Make sure you also force-create and force-push tags for minor and patch updates. For example, when creating v5.1.0 (a minor bump), you want to create (or update) `v5`, `v5.1`, and `v5.1.0`. +1. Tag main with the new version number and create a GitHub release. Make sure you also force-create and force-push tags for minor and patch updates. For example, when creating v5.2.0 (a minor bump), you want to create (or update) `v5`, `v5.2`, and `v5.2.0`. diff --git a/package-lock.json b/package-lock.json index 040a51b0..9c3470c5 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "github-script", - "version": "5.0.1", + "version": "5.1.0", "lockfileVersion": 2, "requires": true, "packages": { "": { "name": "github-script", - "version": "5.0.1", + "version": "5.1.0", "license": "MIT", "dependencies": { "@actions/core": "^1.5.0", diff --git a/package.json b/package.json index 1811f0d2..ffea2f59 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "github-script", "description": "A GitHub action for executing a simple script", - "version": "5.0.1", + "version": "5.1.0", "author": "GitHub", "license": "MIT", "main": "dist/index.js",