build: release v6.127.0 #7412
Closed
build: release v6.127.0 #7412
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 [@types/jwk-to-pem](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/jwk-to-pem) from 2.0.1 to 2.0.3. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/jwk-to-pem) --- updated-dependencies: - dependency-name: "@types/jwk-to-pem" dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
build: merge release v6.126.0 to develop
Bumps [nodemailer](https://github.com/nodemailer/nodemailer) and [@types/nodemailer](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/nodemailer). These dependencies needed to be updated together. Updates `nodemailer` from 6.9.12 to 6.9.13 - [Release notes](https://github.com/nodemailer/nodemailer/releases) - [Changelog](https://github.com/nodemailer/nodemailer/blob/master/CHANGELOG.md) - [Commits](nodemailer/nodemailer@v6.9.12...v6.9.13) Updates `@types/nodemailer` from 6.4.7 to 6.4.15 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/nodemailer) --- updated-dependencies: - dependency-name: nodemailer dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: "@types/nodemailer" dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [winston](https://github.com/winstonjs/winston) from 3.8.2 to 3.13.0. - [Release notes](https://github.com/winstonjs/winston/releases) - [Changelog](https://github.com/winstonjs/winston/blob/master/CHANGELOG.md) - [Commits](winstonjs/winston@v3.8.2...v3.13.0) --- updated-dependencies: - dependency-name: winston dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…7405) * fix: add joi validation on POST body for payment onboarding * chore: tighten validation Co-authored-by: Tejas G. <code@gtejas.com> --------- Co-authored-by: Tejas G. <code@gtejas.com>
chore: update date to 28 jun
* feat: add basic email notifications page * feat: update storage form types * feat: update validation rules and add helper fns * rename email notifications page name * refactor tab rendering logic * fix(admin-form): update Joi validation wrt emails and publicKey fields Fixes #2264 by disallowing publicKey field for email mode forms and disallowing emails field if not Email or Encrypt mode. * feat(model): add emails field to encrypt forms * fix(frontend): fix issue when getValues returns undefined * refactor: make dataCollationData optional and add common types * feat(encrypt-submission): update encrypt submissions to send email notifs * fix: replace deprecated opaque type with tagged * refactor: move email notifications and show payments tab by default * fix: update mutations to fix failing validation at form wizard * fix: remove unused type predicates * feat(frontend): exclude email notifications from payment forms * fix: move tabConfig to top level and separate label from path * refactor: remove redundant useMemo and add EmailNotificationsHeader * fix: update encrypt form validation to have string[] only * fix(admin-form): enforce emails to be empty when duplicating to encrypt * fix(test:backend): add and modify tests for emails field in encrypt form * fix(test): ensure processDuplicateOverrideProps returns empty emails for encrypt * fix(test): update ENCRYPT_FORM_DEFAULTS to have emails field * fix: add exhaustive switch for enums * fix: move boolean calc out and fix inline message in payments page for test env * fix: update form encrypt schema * fix: add PaymentsNotAllowed component * fix: update comment for /settings controller and remove emails from duplicate dto * fix(admin-form): validate that payment forms don't have emails and vice versa * fix: add helper to extract emails from form types * fix: cleanup * fix: update use-template mutations * fix: update payment form and emails to be mutually exclusive * fix: check payments_field.enabled instead of making stripe call * fix: check both PaymentChannel and enabled field for payment forms * feat: move email notifications into a new tab * feat: reduce opacity at component level and add stories for email notifs * fix: add common payment fields to fix chromatic tests * fix: update wrong link and remove padding * fix: fix lodash merge array bug for chromatic test * fix: lodash merge should only overwrite if override arr is empty * fix: fix chromatic reviews * fix: fix tag input UI * fix: ensure non-zero admin emails length before sending * fix: move invalid payment config check to svc instead of controller * fix: fix incorrect error thrown and add jest test case for invalid payment update * fix: remove unused import and move jest test * test: update e2e test for email notification in encrypt form * fix: fix failing backend jest tests * fix: check for null + undefined and fix style * fix: improve rendering of tabs to avoid inserting via idx * fix: render null if not email or encrypt form * fix: increase encrypt-submission timeout for checking for emails * fix(test): fix e2e tests for new email notifications tab
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
Dependencies
Dev-Dependencies
Tests