SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions.

SpiceDB

I just noticed `version":"v1.20.0","error":"GET https://api.github.com/repos/authzed/spicedb/releases/latest: 403 API rate limit exceeded for ...` in my container logs while running our spicedb containerbased testsuite ...a "few" times (trying to make it more robust, removing flakiness etc, so running tests hundreds of times) - hope that doesn't mind you folks? I think it's the integrated latest-version check that does this.

i'll add the --skip-release-check=true for the tests, though

I don't think that's a problem - rate limits should be associated with the client. If you authenticate, you should get higher rate limits

npnp, for the tests its fine to just avoid the check at all 🙂

yep, not upgraded yet. will do shortly 🙂