mirror/aliasvault
1
0
Fork 0
mirror of https://github.com/aliasvault/aliasvault.git synced 2026-05-24 00:05:44 -04:00
Code Issues Packages Projects Releases Wiki Activity

Add bump-version.sh script (#846)

Browse Source
This commit is contained in:
Leendert de Borst
2025-05-30 10:22:26 +02:00
parent a8e075d932
commit 2803dcf02c
3 changed files with 274 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/misc/release/create-new-release.md
View File

@@ -13,7 +13,7 @@ Follow the steps in the checklist below to prepare a new release.
- [ ] Update ./apps/server/Shared/AliasVault.Shared.Core/AppInfo.cs and update major/minor/patch to the new version. This version will be shown in the client and admin app footer. This version should be equal to the git release tag.
- [ ] Update ./apps/server/Shared/AliasVault.Shared.Core/AppInfo.cs with the minimum supported client versions.
- In case API output breaks earlier client versions and/or this version of the client/API will upgrade the client vault model to a new major version.
- [ ] Update ./install.sh `@version` in header if the install script has changed. This allows the install script to self-update when running the `./install.sh update` command on default installations.
- [ ] Update ./install.sh `@version` in header ONLY if the install script content has changed since the last release. This allows the install script to self-update when running the `./install.sh update` command on default installations.
## Versioning browser extensions
- [ ] Update `./apps/browser-extension/wxt.config.ts` with the new version for the extension. This will be shown in the browser extension web stores. This version should be equal to the git release tag.