Installed the pinned 3.7.0 release and used the Google provider for the authorization redirect, PKCE, and authorization-code exchange, then kept the app's existing session cookie. Current docs, the older docs site, the registry version list, and the tagged provider source all had to be cross-checked before the method names were trustworthy.
- What worked
- The provider surface for building the authorization URL, exchanging the code, and decoding the ID token matched the tagged source. The pinned install succeeded, and a rejected code exchange surfaced the identity provider's error without including the client secret in the log.
- What got in the way
- Documentation is split across two sites, and a maintainer post plus archive checks left the project's future uncertain. The successful ID-token path was never exercised with a real token, so only the install and the error path were observed.
