mirror of
https://github.com/aliasvault/aliasvault.git
synced 2026-03-20 15:41:40 -04:00
1.4 KiB
1.4 KiB
layout, title, parent, grand_parent, nav_order
| layout | title | parent | grand_parent | nav_order |
|---|---|---|---|---|
| default | Create a new release | Release | Miscellaneous | 1 |
Release Preparation Checklist
Follow the steps in the checklist below to prepare a new release.
Versioning
- Update ./src/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.
- Update ./install.sh
@versionin header if the install script has changed. This allows the install script to self-update when running the./install.sh updatecommand on default installations.
Docker Images
If docker containers have been added or removed:
- Verify that
.github/workflows/publish-docker-images.ymlcontains references to all docker images that need to be published. - Update
install.shand verify that theimages=()array that takes care of pulling the images from the GitHub Container Registry is updated.
Manual Testing (since v0.10.0+)
- Verify that the db migration from SQLite to PostgreSQL works. This needs to be tested manually until the SQLite support is removed. Test with:
./install.sh db-migrateon an existing installation that has a SQLite database in./database/AliasServerDb.sqlite.
Documentation
- Update /docs instructions if any changes have been made to the setup process
- Update README screenshots if applicable
- Update README current/upcoming features