- Updated all crates except webauthn since it has incompatible dependencies
- Updated DataTables JS
- Updated GitHub Actions
- Applied Zizmore fixes
- Removed `fallback-icon.png` and return 404 when a favicon is not
found, same as upstream does.
- Updated `global_domains.json`, which removed a lot of domains. Even
thought this large removal, lets keep it in sync with upstream. Users
can still add custom domains to this list, or just add those domains
to their vault item it self.
Signed-off-by: BlackDex <black.dex@gmail.com>
- Pass the MariaDB client library to mysqlclient-sys through its environment variables, so a cached build no longer recompiles mysqlclient-sys, diesel and diesel_migrations in every MySQL build. The cache prefix changes once, because the old caches would keep rebuilding it.
- Drop the sqlite,mysql,postgresql,enable_mimalloc test: enable_mimalloc is still tested on and off.
- Test and lint unsafe_test_mode in the all-features runs instead of separate SQLite-only ones: it only adds the test seeder.
- Only save caches on main, in the Build and SDK live tests workflows, to save cache space.
* Add a test seeder behind the unsafe_test_mode feature
For the end-to-end tests: with the feature, /test/seeder answers the calls the
SDK's live tests make to a seeder API (POST /seed with SingleUserScene or
TestVectorUserScene, DELETE /seed/<playId>), behind HTTP basic auth from
TEST_SEEDER_USERNAME and TEST_SEEDER_PASSWORD, and 404 without them.
It creates accounts without any checks, so no release build has the feature.
CI builds and tests it with sqlite.
* Run the SDK live tests against the test seeder
tools/sdk-live-tests/run.sh builds the server with unsafe_test_mode and runs
the live tests of the SDK's e2e/wasm suite. For SDK versions whose tests log in
to one given account, each user test vector with a master password is seeded
with its vault on a fresh server; for versions that seed their own accounts,
the tests get the seeder's address. Every vector runs, then a summary.
The workflow runs it by hand, and on changes to the seeder or the runner.
* Run the SDK live tests daily
* Test the published SDK package by default in the SDK live tests