chore(deps): bump asobi to include rotating refresh tokens (#145)#66
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the pinned
asobidependency from92518c7(#138) to052b5c9(#145), picking up the rotating refresh-token auth change.Why
The client SDK smoke tests run against
ghcr.io/widgrensit/asobi_lua:latest(viasdk_demo_backend). The current image predates asobi #145, so it still returnssession_tokenand lacks/auth/refreshand/auth/logout. That breaks the auth smoke flow for every SDK now migrated to the access/refresh token pair.Merging this republishes
asobi_lua:latestwith the new auth surface, unblocking the SDK sync PRs (asobi-dart/js/unity/godot/defold/unrealfeat/sync-api).Change
rebar.lock:asobiref →052b5c98e061a392b1ef6eecc8ec373fa01223f2.Local build skipped (this environment is OTP 29; asobi→kura builds on OTP 28) — validated by CI.