zapstore-mirror/net.aliasvault.app
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bump install.sh version to use self-documenting ISO8601 date

Browse Source
This commit is contained in:
Leendert de Borst
2026-01-28 16:52:32 +01:00
parent 3eb7aca4da
commit b687bc08ba
3 changed files with 19 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/misc/dev/release/manual-versioning.md
+1 -1
View File
@@ -14,7 +14,7 @@ Alternatively, you can do it manually by following these steps:
- [ ] 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.
- Only required if new 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 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.
- [ ] Update ./install.sh `@version` number in header ONLY if the install script content has changed since the last release. Increment the number by 1. This allows the install script to self-update when running the `./install.sh update` command on default installations. Note: This is a simple build number (not semver) that is independent of the release version - only increment it when install.sh actually changes.
## 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.