From 242d165554600eb8de1d8dff4284c2928c69d40c Mon Sep 17 00:00:00 2001 From: hammadb Date: Tue, 5 Sep 2023 17:21:09 -0700 Subject: [PATCH] [RELEASE] Release js 1.5.8 --- clients/js/DEVELOP.md | 3 ++- clients/js/package.json | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/clients/js/DEVELOP.md b/clients/js/DEVELOP.md index 8236cc36a92..030f3ef455c 100644 --- a/clients/js/DEVELOP.md +++ b/clients/js/DEVELOP.md @@ -23,7 +23,8 @@ This readme is helpful for local dev. #### Automatically ##### Increase the version number -1. Create a new PR for the release that upgrades the version in code. Name it `js_release/A.B.C` for production releases and `js_release_alpha/A.B.C` for alpha releases. In the package.json update the version number to the new version +1. Create a new PR for the release that upgrades the version in code. Name it `js_release/A.B.C` for production releases and `js_release_alpha/A.B.C` for alpha releases. In the package.json update the version number to the new version. For production releases this is just the version number, for alpha +releases this is the version number with '-alphaX' appended to it. For example, if the current version is 1.0.0, the alpha release would be 1.0.0-alpha1 for the first alpha release, 1.0.0-alpha2 for the second alpha release, etc. 2. Add the "release" label to this PR 3. Once the PR is merged, tag your commit SHA with the release version diff --git a/clients/js/package.json b/clients/js/package.json index 3e49e65b651..53dbaf0e9c6 100644 --- a/clients/js/package.json +++ b/clients/js/package.json @@ -1,6 +1,6 @@ { "name": "chromadb", - "version": "1.5.7", + "version": "1.5.8", "description": "A JavaScript interface for chroma", "keywords": [], "author": "",