Skip to content

chore(examples): update Go/Python SDK deps to new releases#15

Open
lakhansamani wants to merge 2 commits into
mainfrom
chore/sdk-proto-dep-bump
Open

chore(examples): update Go/Python SDK deps to new releases#15
lakhansamani wants to merge 2 commits into
mainfrom
chore/sdk-proto-dep-bump

Conversation

@lakhansamani

Copy link
Copy Markdown
Contributor

Summary

Update every example that depends on authorizer-go or authorizer-py to the newly released SDKs, which now consume the dedicated authorizer-proto-go / authorizer-proto packages as real versioned dependencies (instead of vendoring generated stubs). Go examples also move to the /v2 module path.

Changes

  • Go examples (with-go, with-microservices-go, with-spiffe/workload, with-k8s-tokenreview/app): import path github.com/authorizerdev/authorizer-go -> .../authorizer-go/v2; require v2.2.0-rc.4. Dropped the local replace => ../authorizer-go directives — the tagged release now carries the client_credentials / client_assertion APIs those examples needed. go mod tidy pulls authorizer-proto-go v0.1.0 transitively.
  • Python examples (with-python, with-rag-fga, with-agents-python): bump authorizer-py to 0.3.0rc3 (matching each file's existing pin style). authorizer-proto is pulled transitively.
    • with-rag-fga/seed.py: PaginatedRequest was removed in 0.3.0rc3; switched to ListUsersRequest (same pagination=PaginationRequest(...) shape, which is what admin.users() now takes).
    • with-agents-python: replaced the editable-local install (pip install -e ../../../authorizer-python, a path that doesn't exist for anyone cloning this repo) with a requirements.txt pinning the released SDK — the token-exchange API it needs now ships in 0.3.0rc3.
  • Refreshed now-stale README/Dockerfile notes that described the removed replace directives and old versions.

Testing

  • Go: go mod tidy + go build ./... + go vet ./... clean for all 4 modules.
  • Python: fresh-venv pip install -r requirements.txt for each example resolves with no errors and lands authorizer_proto in site-packages; every imported symbol resolves against 0.3.0rc3 and all .py files compile.
  • No live-server runtime verification (examples require a running Authorizer instance); build/install + import-resolution is the bar.

Please review — not self-merging.

- Go examples: import path -> authorizer-go/v2, pin v2.2.0-rc.4;
  drop local `replace` directives now that the tag ships the
  client_credentials/client_assertion APIs (pulls authorizer-proto-go).
- Python examples: bump authorizer-py to 0.3.0rc3 (pulls authorizer-proto).
- with-rag-fga: PaginatedRequest was removed in 0.3.0rc3; use ListUsersRequest.
- with-agents-python: switch editable-local install to released authorizer-py.
- Refresh stale README/Dockerfile notes about the removed replaces.
Bump every example depending on authorizer-js or authorizer-react to
the released RCs, matching each file's existing caret pin style.

- authorizer-js ^3.2.1 -> ^3.3.0-rc.4: with-nextjs, with-nextjs-13,
  with-react-native-expo, with-express-js (direct); with-vanilla-js
  and with-vanilla-js-custom-ui via the unpkg UMD CDN URL.
- authorizer-react ^2.0.7 -> ^2.2.0-rc.3: with-nextjs, with-nextjs-13,
  with-react, with-gatsbyjs. Transitive authorizer-js dedupes up to
  3.3.0-rc.4 in each lockfile.
- No code changes needed: no example calls the flattened admin
  pagination API, sets is_multi_factor_auth_enabled on signup, or
  composes AuthorizerVerifyOtp directly, so none of the RC breaking
  changes apply.
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.

1 participant