NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1501 by repository stars
Latest stable
v1.28.0
Last release 13 days ago
09 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Most releases are documented
notes for 38 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
209 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
The oauth2, oauth1 and Apple callbacks now read the handshake token only from the JWT cookie set by the login step. They used TokenService.Get , which
The oauth2, oauth1 and Apple callbacks now read the handshake token only from the JWT cookie set by the login step. They used TokenService.Get, which takes the JWT query parameter and the X-JWT header before the cookie, so a callback request could carry a handshake that the browser's own login never set and complete a login started elsewhere, leaving the browser signed in to an account it did not choose. Session tokens in the query or header work as before everywhere else (#329).
Two more callback fixes in the same change. The oauth1 callback panicked when the cookie held a session token and GET was in XSRFIgnoreMethods; it now answers 403 like the oauth2 and Apple callbacks. The callback also enforces the 30-minute expiry the login handlers put on the handshake, which the cookie path never checked. A handshake without an expiry is still accepted.
Two behaviour changes. A callback that sends the handshake in ?token= or X-JWT without the cookie now fails. No known integration does this: remark42 and the example finish OAuth through a browser popup that carries the cookie. A user who leaves the provider's consent page open for more than 30 minutes now has to start the login again.
Every oauth2 login through the shared oauth2 handler, which serves the built-in oauth2 providers except Apple and every AddCustomProvider registration, now uses PKCE with the S256 method. Servers without PKCE support ignore it, so there is nothing to configure, and a callback for a handshake issued before the upgrade sends no verifier (#327 by @paskal).
New TelegramHandler.ChatIDAttribute stores the user's raw Telegram chat ID as a string attribute under the given key on a fresh login, so an app can message the user through its bot. Empty keeps the current behaviour, and the user id stays the hashed value (c8b8b0b by @paskal).
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
The direct provider no longer gives a 40-character hex username another user's id. It built the user id with token.HashID , which returns a 40-charact
The direct provider no longer gives a 40-character hex username another user's id. It built the user id with token.HashID, which returns a 40-character hex value unchanged, so a username equal to the SHA1 of another username got that user's id: 522b276a356bdf39013dfabea2cd43e141ecc9e8 logged in with the same id as alice. An application that keys records or permissions on User.ID treated the two logins as one account. Exploiting it needs a username policy that accepts 40-character hex names and a known victim username. The default id is now the plain SHA1 of the username. Reported privately by Rathnadeepan (@HotWater-015), fixed in #324.
One behaviour change. With the default id mapping, usernames of exactly 40 hex characters get new ids, so records keyed on the old ids need a migration. Every other username keeps its id. A custom UserIDFunc works as before: its result still goes through HashID, so it must return an id the application controls, never the raw username.
Logout now clears a JWT cookie whose name starts with __Http- or __Host-Http-. Reset expired the cookie without HttpOnly, and Chromium rejects a Set-Cookie for such a name without it, so the session cookie survived sign-out. The removal header now carries HttpOnly for every deployment (#320).
New Opts.PartitionedCookies marks the auth cookies Partitioned, so an application embedded in a page on another site keeps its session when the browser blocks third-party cookies, and the JWT cookie stays HttpOnly. It requires SecureCookies, and a cross-site frame also needs SameSiteCookie: http.SameSiteNoneMode. It helps only the logins that set the cookie inside the frame: direct, telegram and email code. An OAuth callback runs in a popup with its own top-level site, so with the option on, an OAuth session no longer reaches the frame (#318 by @paskal).
Also in this release: a README section on getting the user email from Google (#323) and a README typo fix (#321 by @hamidzr).
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Verify login now accepts only a signed handshake token that carries this provider's name. Before, LoginHandler accepted any token with a user::address
Verify login now accepts only a signed handshake token that carries this provider's name. Before, LoginHandler accepted any token with a user::address handshake signed with the service secret. That included handshake tokens an application issues for its own purposes, which are not login confirmations, and confirmations issued by another verify provider. A session token, which has no handshake, caused a nil dereference. All of these now get a 403.
One behaviour change. An application that mints its own handshake tokens and sends them to the verify login endpoint has to set the provider name on them. Tokens from the provider's own confirmation request already carry it.
The login error paths no longer log the token. Six error branches of LoginHandler passed the raw request to the error response, which logs the URL with ?token= in it. An expired session token sent as ?token= was logged in full, and it stays usable as a cookie because the auth middleware refreshes expired tokens. A handler built without a confirmation store logged a confirmation link that could still be redeemed.
Also in this release: the provider tests fail with the address when a test server port is taken, where before they failed later on a client timeout that did not name the cause.
Full detail on the token check in #319.
Nothing published for this version
Nothing published for this version
Nothing published for this version
The Telegram provider no longer hard-codes https://api.telegram.org . NewTelegramAPIWithBaseURL takes the base, and every request goes through it, ava
The Telegram provider no longer hard-codes https://api.telegram.org. NewTelegramAPIWithBaseURL takes the base, and every request goes through it, avatar downloads included. An empty base falls back to the public API.
Moving a token-bearing URL off a constant is what the rest of the change is for: the bot token travels in the request path, and the answers now come from a host the library does not control. The base is validated, error text is scrubbed of the token in raw and encoded forms, a success response has to match Telegram's own username shape, and redirects are refused by default because Go copies the previous URL into Referer.
One behaviour change. A caller that relied on the default redirect policy now gets an error on a redirect. A caller-supplied CheckRedirect remains in force.
Also in this release: the Apple public-key test no longer binds a shared port, and the Telegram tests no longer race or depend on order.
Full detail in #316.
Nothing published for this version
Nothing published for this version
Nothing published for this version
EmailParams gains HELOHost , which sets the hostname the sender announces in the SMTP greeting. Left empty it stays localhost , so existing configurat
EmailParams gains HELOHost, which sets the hostname the sender announces in the SMTP greeting. Left empty it stays localhost, so existing configurations are unchanged. A relay enforcing reject_non_fqdn_helo_hostname or reject_unknown_helo_hostname refuses the default greeting, and the verification message never leaves.
Verification email delivery is now bound to the request context. TimeOut covered the connection setup only, so a server that accepted the connection and then stalled held the login request for as long as it liked. The send now ends when the request does. Sender implementations that do not offer SendContext keep working through the existing Send.
Also updates dependencies across the root, v2 and example modules, and sets explicit GITHUB_TOKEN permissions in the workflows.
Nothing published for this version
Avatar storage on GridFS destroyed data. Every Put created a new revision under the same filename, so old avatars accumulated, Remove deleted only the
Avatar storage on GridFS destroyed data. Every Put created a new revision under the same filename, so old avatars accumulated, Remove deleted only the newest one and left the avatar readable, and ID could return a stale revision. Cleanup now removes only revisions older than the upload that just completed, so two concurrent uploads for the same user cannot delete each other's file.
Apple public keys are now cached rather than fetched on every login, refreshed when a token names an unknown key so rotation still works, and reused for up to 12 hours if the key service is unreachable. A non-2xx response or an empty key set is rejected instead of being cached as valid.
The post-auth redirect uses 303 instead of 307. Apple's form_post callback arrives as a POST, and a method-preserving redirect replayed it onto the target page, which a static file server answers with 405. This changes the status for the oauth1, oauth2 and verify providers as well.
Two documented parameters now work: session is honoured by the direct and verify providers, and aud is accepted alongside site on the verify confirmation request. Apple no longer forces a persistent cookie when a session-only login was requested. For the direct and verify providers any non-zero sess value now means session-only, where previously only sess=1 did.
The avatar route returns 404 when no avatar store is configured, instead of dereferencing a nil proxy.
Dependencies: go-pkgz/email v0.8.0 and go-pkgz/rest v1.24.0. CI moves to go 1.26 and golangci-lint v2.12.
The GitHub provider can now derive the local user id from the immutable numeric account id instead of the mutable login. This is opt-in and off by def
The GitHub provider can now derive the local user id from the immutable numeric account id instead of the mutable login. This is opt-in and off by default, since enabling it changes the id of every existing GitHub user. Separately, the OAuth1 and OAuth2 callbacks no longer skip the user info HTTP status check, which previously let an error response map every failed login onto one shared user id.
Full Changelog: v1.25.5...v1.25.6
Nothing published for this version
Nothing published for this version
Changes since v1.25.4 #293 redact sensitive auth logging #292 package-wide comment sweep #291 fix misleading and stale docstrings around the security
Full Changelog: v1.25.4...v1.25.5
Nothing published for this version
Nothing published for this version
Security : fixes stored XSS in avatar.Proxy by rejecting non-image avatar content before storage and before serving. Also adds CSP/nosniff headers, We
Security: fixes stored XSS in avatar.Proxy by rejecting non-image avatar content before storage and before serving. Also adds CSP/nosniff headers, WebP-safe validation, ETag parsing fixes, and decompression-bomb checks. Credit to @paskal.
Full Changelog: v1.25.3...v1.25.4
Security: large hardening wave covering log/credential leaks, OAuth/Apple validation, and email-confirmation replay protection. Credit to @paskal.
Security: large hardening wave covering log/credential leaks, OAuth/Apple validation, and email-confirmation replay protection. Credit to @paskal.
Full Changelog: https://github.com/go-pkgz/auth/compare/v1.25.2...v1.25.3
Nothing published for this version
Nothing published for this version
Nothing published for this version
Security: Patreon provider user ID collision fix, see GHSA-f6qq-3m3h-4g42. Credit to @Nadav0077.
Security: Patreon provider user ID collision fix, see GHSA-f6qq-3m3h-4g42. Credit to @Nadav0077.
Full Changelog: https://github.com/go-pkgz/auth/compare/v1.25.1...v1.25.2
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Bump github.com/golang-jwt/jwt/v5 from 5.2.1 to 5.2.2 in /v2 by @dependabot in https://github.com/go-pkgz/auth/pull/235
Full Changelog: https://github.com/go-pkgz/auth/compare/v1.25.0...v1.25.1
Nothing published for this version
feature: Discord OAuth2 Provider by @mgkbadola in https://github.com/go-pkgz/auth/pull/223
Full Changelog: https://github.com/go-pkgz/auth/compare/v1.24.2...v1.25.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Detect and set proper Content-Type for avatars by @paskal in https://github.com/go-pkgz/auth/pull/219
Full Changelog: https://github.com/go-pkgz/auth/compare/v1.24.1...v1.24.2
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fix TestTelegramConfirmedRequest by @cyb3r4nt in https://github.com/go-pkgz/auth/pull/215
Full Changelog: https://github.com/go-pkgz/auth/compare/v1.24.0...v1.24.1
Nothing published for this version
Nothing published for this version
One column per quarter.