From 8a730f42ccf19a8f0e9215090786dac07bd664c0 Mon Sep 17 00:00:00 2001 From: xermicus Date: Wed, 28 May 2025 08:15:41 +0200 Subject: [PATCH] update NPM package version (#336) Signed-off-by: Cyrill Leutwiler --- RELEASE.md | 6 +++++- js/resolc/package.json | 2 +- package-lock.json | 2 +- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 95972bd..439f544 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -4,7 +4,11 @@ Prior to the first stable release we neither have formal release processes nor d To create a new pre-release: -1. Create a release PR which updates the versions in the workspace `Cargo.toml` and updates the `CHANGELOG.md` accordingly. +1. Create a release PR which, if necessary: + - Updates the versions in the workspace `Cargo.toml` + - Updates the version in each crate `Cargo.toml` + - Updates the version of the NPM package in `js/resolc/package.json` + - Updates the `CHANGELOG.md` to reflect all observable changes 2. If the CI passes, merge the release PR. 3. Push a `vX.Y.Z` tag that has the same version as in `Cargo.toml` 4. The release workflow will attempt to build and publish a new pre-release if the latest tag does match the cargo package version. diff --git a/js/resolc/package.json b/js/resolc/package.json index 7e4b7b3..b142a8d 100644 --- a/js/resolc/package.json +++ b/js/resolc/package.json @@ -1,7 +1,7 @@ { "name": "@parity/resolc", "license": "Apache-2.0", - "version": "0.1.0-dev.16", + "version": "0.1.0", "author": "Parity (https://parity.io)", "module": "index.ts", "types": "./dist/index.d.ts", diff --git a/package-lock.json b/package-lock.json index 9c88c29..7d18f59 100644 --- a/package-lock.json +++ b/package-lock.json @@ -44,7 +44,7 @@ }, "js/resolc": { "name": "@parity/resolc", - "version": "0.1.0-dev.16", + "version": "0.1.0", "license": "Apache-2.0", "dependencies": { "@types/node": "^22.9.0",