From bec26822bcae6f0ed9d48aabc5887d2759287229 Mon Sep 17 00:00:00 2001 From: Edward McFarlane Date: Wed, 9 Oct 2024 10:51:14 -0400 Subject: [PATCH] Prepare for v1.0.2 --- RELEASE.md | 2 +- package-lock.json | 4 ++-- package.json | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 27e79b5..f5a1c3e 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -8,7 +8,7 @@ We follow the best practices outlined in the [GitHub Actions documentation][gith 2. On a new branch, run the following commands to update the version of the action: ```bash -VERSION=X.Y.Z make updateversion +VERSION=X.Y.Z VERSION_SHORT=X make updateversion ``` 3. Open a PR titled "Prepare for vX.Y.Z". Once it's reviewed and CI passes, merge it. diff --git a/package-lock.json b/package-lock.json index 7cbdffb..741e83d 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "buf-action", - "version": "1.0.1", + "version": "1.0.2", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "buf-action", - "version": "1.0.1", + "version": "1.0.2", "license": "Apache-2.0", "dependencies": { "@actions/core": "^1.10.1", diff --git a/package.json b/package.json index 412ba3d..92897dc 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "buf-action", - "version": "1.0.1", + "version": "1.0.2", "description": "GitHub Action for buf", "main": "src/main.ts", "scripts": {