Skip to content

Commit 091609c

Browse files
authored
[ENH] Automatically set version release as the latest release on Github (#2908)
## Description of changes Automatically set a released version as the latest on Github ## Test plan We will make a new release and see. ## Documentation Changes Update the release process documentation
1 parent 99365d5 commit 091609c

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

.github/workflows/release-chromadb.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -239,7 +239,8 @@ jobs:
239239
artifacts: "dist/chromadb-${{needs.get-version.outputs.version}}.tar.gz"
240240
allowUpdates: true
241241
removeArtifacts: true
242-
prerelease: true
242+
prerelease: ${{ needs.check-tag.outputs.tag_matches != 'true' }}
243+
makeLatest: ${{ needs.check-tag.outputs.tag_matches == 'true' }}
243244

244245
release-docs:
245246
name: Deploy docs to Vercel

RELEASE_PROCESS.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,4 +17,4 @@ git tag A.B.C <SHA>
1717
```
1818
git push origin A.B.C
1919
```
20-
6. On the right panel on Github, click on "Releases", and the new release should appear first. Edit it, and mark it as "latest".
20+
6. On the right panel on Github, click on "Releases", and the new release should appear first. Make sure it is marked as "latest".

0 commit comments

Comments
 (0)