Repository navigation
Release v16.4.0 - #1480
Merged
Merged
Release v16.4.0#1480
Conversation
lizkenyon
approved these changes
Nov 5, 2026
Suleimanlatrsh
force-pushed
the
v16.4.0
branch
from
November 5, 2026 19:51
c4202be to
9132503
Compare
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.
What
Bumps
shopify_apito 16.4.0 and moves the Unreleased CHANGELOG entries under it.Why
Add JWT client assertion support to client credentials merged on Oct 29 but hasn't been released yet. This release also includes Treat invalid_identity_session token exchange errors as invalid JWT.
What I checked
rake test:libraryandrake test:rest_wrapperspass locally (Ruby 3.4.8)rubocopis cleanversion.rb,Gemfile.lockandCHANGELOG.mdchange, same as the v16.3.1 releasesrb tcdidn't run locally (the Sorbet binary is x86 only), CI runs itNotes for reviewers
After merge I'll tag
v16.4.0on the merge commit and deploy the rubygems stack in Shipit.