-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: release v6.155.0 #7816
Merged
Merged
build: release v6.155.0 #7816
Conversation
This file contains 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
`AWS_ENDPOINT` defaults to an S3 endpoint hard-coded to ap-southeast-1. This affects deployment scenarios to other AWS regions, unless `AWS_ENDPOINT` is specified to line up with `AWS_REGION`. It can be argued that the default for `AWS_ENDPOINT` should be driven by the specific region that FormSG is deployed to, so accordingly, at runtime, change `loadBucketS3UrlSchema()` so that the default endpoint for S3 buckets reflects the region where FormSG is currently deployed.
build: merge release v6.154.0 to develop
* feat: capture and redirect on sp on well-known endpoint * chore: global replacement
* feat: add onblur to single select component * feat: add single select to email notifications page * feat: add separate notify or step 1 in mrf send outcome email logic * feat: remove email field in step 1 of workflow builder * fix: add ChangeHandler * feat: remove validation in FE to account for deleted email field id * feat: add tc for step 1 field * feat: add chromatic tc for step 1 in settings page * chore: remove unused import * fix: onBlur typing * feat: add default for emailFieldNotificationId
|
kennethchangOPENGOV
approved these changes
Oct 29, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
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.
New
#7794
#7810
#7809
#7808
#7807
Tests
feat: move step1 email field to settings
#7794
TC1: Selecting step 1 email field sends completion email to step 1 email response value:
TC2: Selecting step 1 email field sends approve/reject email to step 1 email response value:
TC3: Deleting the email field causes email to not send to that step 1 party anymore
feat(singpass): singpass jwks config
#7809
Regression
Singpass login should still work