Batch migration to set `OauthAccessToken#expires_in`
Compare changes
expires_in: nil
were
created:
OauthAccessToken.new
directly does not set a default
expires_in
. We stopped calling OauthAccessToken.new
directly via !105734 (merged)
expires_in
value of
any refreshed tokens to match the expires_in
value of the
token doing the refreshing. This means that any tokens that happened
to be refreshed while the previous batch migration was running could
have been created with expires_in: nil
. This issue was fixed via !107306 (merged)
oauth_access_token
records in the DB with expires_in: nil
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Numbered steps to set up and validate the change are strongly suggested.
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.