From d36cdfbdb7c865f3b91eb085f71bac066f696c4f Mon Sep 17 00:00:00 2001 From: Kyle Hounslow Date: Mon, 27 Jul 2026 12:16:47 -0700 Subject: [PATCH] chore(release): bump CLI to 0.3.0 and document the tag-request step Minor release. The delta since v0.2.0 includes VPC support for the AWS installer (#337), a new feature adding --vpc-id / --subnet-ids / --security-group-ids and a VPC-private deployment path, plus the security-group data-path check and e2e harness (#344). Per the RFC #27 bumping rules, a new non-breaking feature is a MINOR bump, so v0.2.0 -> v0.3.0 rather than a patch. Also fix RELEASING.md step 2: maintainers cannot push tags to this repo (.github#531), so the release tag is requested via a [GitHub Request] issue on opensearch-project/.github. Documents the format and links .github#577 as an example. Signed-off-by: Kyle Hounslow --- RELEASING.md | 9 ++------- aws/cli-installer/package-lock.json | 4 ++-- aws/cli-installer/package.json | 2 +- 3 files changed, 5 insertions(+), 10 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 28997516..937e25a9 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -18,13 +18,8 @@ The CLI (`aws/cli-installer`, published to npm as `@opensearch-project/observabi ## Cutting a release -1. Open a PR that sets `aws/cli-installer/package.json` to the target version (e.g. `0.2.0-beta.1`). Sign commits for DCO (`git commit -s`). Get a maintainer review and merge to `main`. -2. Tag the merged commit and push it: - ``` - git tag v0.2.0-beta.1 - git push upstream v0.2.0-beta.1 - ``` - The tag is the release trigger. Merging alone publishes nothing. +1. Open a PR that sets `aws/cli-installer/package.json` to the target version (e.g. `0.3.0`). Sign commits for DCO (`git commit -s`). Get a maintainer review and merge to `main`. +2. Request the release tag by filing a `[GitHub Request]` issue on [opensearch-project/.github](https://github.com/opensearch-project/.github/issues). Maintainers cannot push tags to this repo directly ([.github#531](https://github.com/opensearch-project/.github/issues/531)), so the admins create the tag on your behalf. Give the merged commit SHA and the tag name (`v0.3.0`). See [.github#577](https://github.com/opensearch-project/.github/issues/577) for the exact format. The tag is the release trigger; merging alone publishes nothing. 3. The `release-to-npm` job pauses on the `release-approval` environment. A required reviewer, who cannot be the release author, opens the workflow run and approves the deployment. 4. On approval, the workflow validates the version, runs tests, publishes the CLI to the correct npm dist-tag, and drafts the GitHub release. Fill in the release notes with the component-version matrix from `.env`. diff --git a/aws/cli-installer/package-lock.json b/aws/cli-installer/package-lock.json index 85f934ec..9725480c 100644 --- a/aws/cli-installer/package-lock.json +++ b/aws/cli-installer/package-lock.json @@ -1,12 +1,12 @@ { "name": "@opensearch-project/observability-stack", - "version": "0.2.1", + "version": "0.3.0", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@opensearch-project/observability-stack", - "version": "0.2.1", + "version": "0.3.0", "license": "Apache-2.0", "dependencies": { "@aws-crypto/sha256-js": "^5.2.0", diff --git a/aws/cli-installer/package.json b/aws/cli-installer/package.json index de475146..25f15f1a 100644 --- a/aws/cli-installer/package.json +++ b/aws/cli-installer/package.json @@ -1,6 +1,6 @@ { "name": "@opensearch-project/observability-stack", - "version": "0.2.1", + "version": "0.3.0", "description": "CLI for the Observability Stack", "type": "module", "bin": "./bin/cli-installer.mjs",