Skip to content

Upgrade dependencies and bump authzed/api to v1.45.4#35

Open
tonnenpinguin wants to merge 4 commits intogoodhamgupta:mainfrom
tonnenpinguin:chore/upgrade
Open

Upgrade dependencies and bump authzed/api to v1.45.4#35
tonnenpinguin wants to merge 4 commits intogoodhamgupta:mainfrom
tonnenpinguin:chore/upgrade

Conversation

@tonnenpinguin
Copy link
Contributor

@tonnenpinguin tonnenpinguin commented Mar 25, 2026

I regenerated the api client based on authzed/api v1.45.4
Google RPC types are no longer taken from Buf; they come from the googleapis Hex package (pulled in via grpc). I updated the Makefile accordingly.

Important: Users need to add GRPC.Client.Supervisor to their supervision tree (e.g. {GRPC.Client.Supervisor, []} in the app’s children). The gRPC client needs this supervisor to open connections.

Aside from that, typical app code can stay the same if you already pass a single target string to the client.

Authzed.Api.V1.Client

Client.new/3 now takes a single endpoint string (e.g. "host:port"), matching GRPC.Stub.connect/2 (including typed forms like ipv4:… / ipv6:… where appropriate).
Client.new/4 (host + port) remains for backward compatibility but is @deprecated. It no longer calls the deprecated GRPC.Stub.connect/3 path (which can surface as warnings or break warnings_as_errors). Instead it builds a target string and delegates to new/3, so deprecation is our compile-time @deprecated, not the library’s runtime warning.

- Bump version to 1.7.0
- Update grpc and protobuf dependencies to versions 0.11.0 and 0.16.0 respectively
- Remove deprecated Google RPC modules from the codebase
- Add GRPC.Client.Supervisor to the supervision tree in the documentation
- Clean up docker-compose-test.yml by removing the version line
cp -r authzed/api/* lib/api/
@echo "Copying files to google/rpc folder..."
@mkdir -p lib/google
cp -r google/rpc lib/google/
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like with this change we need to update the CI stage(which generates protobuf files and diffs them against the previous version) to make it green.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the quick feedback!
I updated the github action files and since we've already been seeing node deprecation warnings I figured I'd just bump everything to the latest version :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants