Release 3.1.0 - Return key ID from CreateKey request #156
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
briskt
requested review from
Praveenraj-K,
ethancanne,
hobbitronics and
jason-jackson
and removed request for
a team
forevermatt
reviewed
Nov 3, 2025
|
hobbitronics
approved these changes
Nov 4, 2025
hobbitronics
left a comment
hobbitronics
left a comment
There was a problem hiding this comment.
Looks good to me and issue seems to be resolved.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
IDP-1726 serverless-mfa-api-go does not include key ID in response
Added
Fixed
Changed
x-mfa-apikeyandx-mfa-apisecretfor both/api-keyendpoints. This may be a breaking change if these endpoints are in an automated workflow. Since these are generally not used for production and are rarely-used endpoints, no major version bump is necessary.