-
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.81.0 #6777
Merged
Merged
build: release v6.81.0 #6777
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
Bumps [zod](https://github.com/colinhacks/zod) from 3.21.4 to 3.22.3. - [Release notes](https://github.com/colinhacks/zod/releases) - [Changelog](https://github.com/colinhacks/zod/blob/master/CHANGELOG.md) - [Commits](colinhacks/zod@v3.21.4...v3.22.3) --- updated-dependencies: - dependency-name: zod dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [zod](https://github.com/colinhacks/zod) from 3.22.2 to 3.22.3. - [Release notes](https://github.com/colinhacks/zod/releases) - [Changelog](https://github.com/colinhacks/zod/blob/master/CHANGELOG.md) - [Commits](colinhacks/zod@v3.22.2...v3.22.3) --- updated-dependencies: - dependency-name: zod dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
build: merge release v6.80.0 into develop
* feat: add .well-known fetch * chore: detect specific directory * refactor: use combined regex
* feat: move submission versions to shared * refactor: make version for clear mutates optional * feat: FE get presigned post data * feat: share AttachmentPresignedPostDataMapType * feat: fe upload files to quarantine bucket * feat: throw error if attachment upload failed * feat: storage submission with virus scans * fix: virus scan conditional * refactor: check feature value right before using * fix: csp headers for virus scanner * fix: csp headers again (typo) * fix: local virus scans if >1 attachment submitted * style: improve virus scan failed error msg * docs: add comments to PublicFormProvider * fix: rm version in SubmitStorageFormClearArgs * docs: createClearSubmissionWithVirusScanningFormData * docs: submitStorageModeClearFormWithVirusScanning * fix: repeated attachment responses on local dev * fix: use virusScannerQuarantineS3BucketUrl defined - chore: rm unused URL for clean bucket - fix: broken tests due to CSP change * fix: broken tests due to schema without clean url * feat: default true for encryption boundary shift FE flag * chore: rm dangling comment from testing * style: virus scan error msg * fix: crash for submissions without attachments * style: syncVirusScanning -> devModeSyncVirusScanning * perf: on local dev - exit for...of once err * fix: status code for malicious file should be 400 * feat: filename in virus scan failed error * fix: encrypt-submission.service tests * refactor: break in attachment res in for...of * chore: rm TODO * fix: playwright tests blocked by feature flag * fix: get-s3-presigned-post-data crash when [] * fix: use fetch fallback only mutateasync fails * docs: explain what onError for mutateAsync does
3 tasks
tshuli
approved these changes
Oct 5, 2023
overriding BE tests to merge as they passed in the PR before release |
fyi @tshuli overwrote the tests w observed behaviour! |
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
#6767
#6774
#6775
#6773
Dependencies
#6768
#6769
Dev-Dependencies
Tests
feat(virus-scanner): frontend orchestration
#6767
@KenLSM
Preperation
eicar.com.txt
.featureflags
collection, set theencryption-boundary-shift-virus-scanner
flag as{ enabled: true }
.Test that virus scanner works
Test that BE feature flag works
@tshuli
featureflags
collection, set theencryption-boundary-shift-virus-scanner
flag as{ enabled: false }
.featureflags
collection, restore theencryption-boundary-shift-virus-scanner
flag as{ enabled: true }
.Test that the FE feature flag works
@tshuli
Test that FE falls back to submission without virus scan if virus scanning fails
@tshuli
VIRUS_SCANNER_LAMBDA_FUNCTION_NAME
) to an invalid function name and redeploy the app.function
virus-scanner-production-virus-scanner
virus-scanner-staging-virus-scanner
virus-scanner-uat-virus-scanner
Test that
/submission/storage
will be used if growthbook can't be instantiatedGROWTHBOOK_CLIENT_KEY
) to an invalid one.sdk-...
/submissions/storage
endpoint rather than/submissions/encrypt
.GROWTHBOOK_CLIENT_KEY
) to the appropriate one.Regression tests
Deploy Notes
featureflags
collection, set theencryption-boundary-shift-virus-scanner
flag as{ enabled: true }
.New GrowthBook flags:
Make sure that the
encryption-boundary-shift-virus-scanner
flag is disabled for prod before deployment. Rollout to 1% after deployment.encryption-boundary-shift-virus-scanner
: FE flag for virus scanner feature.New AWS configs:
Make sure that the prod quarantine S3 bucket has the right CORS policy as described below.
Quarantine bucket CORS policy:
feat: add well-known domain
#6774
@LinHuiqing
Regression
Existing well-known routes are not affected
Existing static and public routes are not affected
Deploy Notes
New aasa file in
.well-known
:apple-developer-merchantid-domain-association
file into s3 static bucket