- Updated web-vault to v2022.05.0
- Made several changes to the build scripts for ease of building/patching etc...
You can now run `make checkout` to pull/update the repo to the wanted version
There is also a `make patch-web-vault` to patch the repo
A `make generate-patch` to create a patch file from the current changes
And many more changes
- Added support for v2.26.1
- Hide some more input fields we do not use
- Fixed building with npm (The audit fix breaks the build)
- Fixed the vaultwarden version json filename.
- Add a bwrs-version.json based upon the latest tag of the
bw_web_builds (Assuming a build is started/created after a new tag is created).
- Updated node version to latest LTS, v13 is EOL, v14 is LTS until 2023-04-30 ( https://nodejs.org/en/about/releases/ )
Running `git submodule update --recursive --init` should be totally fine
for us and it gives us more auditability because then the submodule
commit hash is pinned by the main git repo tag.
* `set -o pipefail -o errexit` exit early on error. This is very useful
to not overlook errors that might not fully break the build but tamper
with the end result.
* Fix `mkdir OUTPUT_FOLDER` fail
* Rework git checkout stuff to only run needed commands.
