All the scripts used by this repo were more focused on Linux based systems.
They did not work on macOS or other BSD based systems because of flags
or commands which are not available.
This PR resolves those items by adjusting the failed commands so they
work on both Linux and macOS/BSD systems.
Fixes#112
- Updated web-vault to v2023.1.1
- Added a small patch to allow scrolling the organizations menu when
there are a lot of organizations.
Fixes https://github.com/dani-garcia/vaultwarden/issues/3148
I also created a PR at bitwarden/clients, pending approval.
This PR updates the web-vault to v2022.11.1
It also replaces the main logo and top left icon to indicate it is
Vaultwarden.
And the footer text has been change to `Vaultwarden (unofficial Bitwarden® server)`
This hopefully helps causing less confusion.
This version has a new feature which isn't supported yet by vaultwarden.
It shouln't be that hard to add this functionality i think.
You can now revoke and restore user access to an org.
- Updated to the latest released web-vault.
- Made some small changes to the checkout script to catch tags like
`2022.6.2` and `v2022.6.2` and convert them to `web-v2022.6.2` instead.
Updated the web-vault to the latest released version.
This version is also using the new repo `bitwarden/clients` instead of the old `bitwarden/web`.
All files have been changed where needed.
- 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
The patch is almost identical just some offsets are different.
This version does solve the multiple `/sync` requests which will benefit
the loading time and load on the server!
- 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.
There needs to be a small change on the vaultwarden server for this to
be fully supported as far as i could tell.
So maybe not yet ready for merge/tagging.
- 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/ )
