Version Packages #3352
Merged
Version Packages #3352
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
changeset-release/main
branch
9 times, most recently
from
7bba39b to
a341216
Compare
zchenwei
reviewed
Jan 27, 2023
github-actions
bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
70a9444 to
c82e1fa
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
c82e1fa to
999f9d3
Compare
Smoke TestsReact Native
|
🥴 |
wlee221
approved these changes
Feb 1, 2023
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@aws-amplify/[email protected]
Patch Changes
#3333
4ba0fb5c1Thanks @calebpollman! - fix(authenticator): migrate totpSecretCode generation to state machine#3327
13d0882a8Thanks @wlee221! - fix(rwa): improve default behavior handling for custom formFields.Previously, adding custom formFields for fields that are not in
signUpAttributesconfiguration wouldn't get any default values, which could lead to broken UI.This commit improves default handling by applying defaults to all known auth field (birthdate, first_name, etc) to custom formField options.
Updated dependencies [
4ba0fb5c1,412538be9,9ce2d01b0,13d0882a8]:@aws-amplify/[email protected]
Patch Changes
#3349
8ae8e0b8cThanks @ErikCH! - fix: Swapped save and cancel buttons.#3333
4ba0fb5c1Thanks @calebpollman! - fix(authenticator): migrate totpSecretCode generation to state machine#3344
b85547545Thanks @ErikCH! - fix: Updated error text for max file count to be more explicit.#3287
412538be9Thanks @zchenwei! - build: updates to support Node ESMConfirmed that both ESM build cannot be loaded by Node.js #3155 and Can't build with Astro #3206 are fixed without having to apply any workaround
Also, test out the changes with the following frameworks/tools:
--polyfill-nodeto fix JS incompatibility in dev mode, but is a known issue#3350
db4ea4f1dThanks @ErikCH! - fix: Swap the upload button with the clear all button.#3327
13d0882a8Thanks @wlee221! - fix(rwa): improve default behavior handling for custom formFields.Previously, adding custom formFields for fields that are not in
signUpAttributesconfiguration wouldn't get any default values, which could lead to broken UI.This commit improves default handling by applying defaults to all known auth field (birthdate, first_name, etc) to custom formField options.
Updated dependencies [
4ba0fb5c1,412538be9,9ce2d01b0,13d0882a8]:@aws-amplify/[email protected]
Patch Changes
#3333
4ba0fb5c1Thanks @calebpollman! - fix(authenticator): migrate totpSecretCode generation to state machine#3287
412538be9Thanks @zchenwei! - build: updates to support Node ESMConfirmed that both ESM build cannot be loaded by Node.js #3155 and Can't build with Astro #3206 are fixed without having to apply any workaround
Also, test out the changes with the following frameworks/tools:
--polyfill-nodeto fix JS incompatibility in dev mode, but is a known issue#3291
9ce2d01b0Thanks @ioanabrooks! - chore(ui,ui-react-core): Add type guard utilsUpdated dependencies [
4ba0fb5c1,412538be9,9ce2d01b0,13d0882a8]:@aws-amplify/[email protected]
Patch Changes
#3333
4ba0fb5c1Thanks @calebpollman! - fix(authenticator): migrate totpSecretCode generation to state machineUpdated dependencies [
4ba0fb5c1,412538be9,9ce2d01b0,13d0882a8]:@aws-amplify/[email protected]
Patch Changes
#3333
4ba0fb5c1Thanks @calebpollman! - fix(authenticator): migrate totpSecretCode generation to state machine#3287
412538be9Thanks @zchenwei! - build: updates to support Node ESMConfirmed that both ESM build cannot be loaded by Node.js #3155 and Can't build with Astro #3206 are fixed without having to apply any workaround
Also, test out the changes with the following frameworks/tools:
--polyfill-nodeto fix JS incompatibility in dev mode, but is a known issue#3291
9ce2d01b0Thanks @ioanabrooks! - chore(ui,ui-react-core): Add type guard utils#3327
13d0882a8Thanks @wlee221! - fix(rwa): improve default behavior handling for custom formFields.Previously, adding custom formFields for fields that are not in
signUpAttributesconfiguration wouldn't get any default values, which could lead to broken UI.This commit improves default handling by applying defaults to all known auth field (birthdate, first_name, etc) to custom formField options.
@aws-amplify/[email protected]
Patch Changes
#3333
4ba0fb5c1Thanks @calebpollman! - fix(authenticator): migrate totpSecretCode generation to state machine#3327
13d0882a8Thanks @wlee221! - fix(rwa): improve default behavior handling for custom formFields.Previously, adding custom formFields for fields that are not in
signUpAttributesconfiguration wouldn't get any default values, which could lead to broken UI.This commit improves default handling by applying defaults to all known auth field (birthdate, first_name, etc) to custom formField options.
Updated dependencies [
4ba0fb5c1,412538be9,9ce2d01b0,13d0882a8]: