yads / nodemailer-express-handlebars

A plugin for nodemailer that uses express-handlebars view engine to generate emails
87 stars 30 forks source link

Bump express-handlebars from 4.0.0 to 5.3.1 #52

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps express-handlebars from 4.0.0 to 5.3.1.

Release notes

Sourced from express-handlebars's releases.

v5.3.1

5.3.1 (2021-05-04)

Bug Fixes

  • add note about security (78c47a2)

v5.3.0

5.3.0 (2021-03-30)

Features

v5.2.1

5.2.1 (2021-02-16)

Bug Fixes

  • deps: update dependency handlebars to ^4.7.7 (1930523)

v5.2.0

5.2.0 (2020-10-23)

Features

  • allow views to be an array (a9f4aaa)

v5.1.0

5.1.0 (2020-07-16)

Features

v5.0.0

5.0.0 (2020-07-06)

Bug Fixes

... (truncated)

Changelog

Sourced from express-handlebars's changelog.

5.3.1 (2021-05-04)

Bug Fixes

  • add note about security (78c47a2)

5.3.0 (2021-03-30)

Features

5.2.1 (2021-02-16)

Bug Fixes

  • deps: update dependency handlebars to ^4.7.7 (1930523)

5.2.0 (2020-10-23)

Features

  • allow views to be an array (a9f4aaa)

5.1.0 (2020-07-16)

Features

5.0.0 (2020-07-06)

Bug Fixes

BREAKING CHANGES

  • Drop support for node versions below v10

4.0.6 (2020-07-06)

... (truncated)

Commits
  • 63e8010 chore(release): 5.3.1 [skip ci]
  • 78c47a2 fix: add note about security
  • 2cde11e chore: update package-lock.json
  • 9a6cf60 chore(deps): update devdependency eslint to ^7.25.0
  • fbc5681 Merge pull request #157 from express-handlebars/renovate/node-10.x
  • 1e2b967 chore(deps): update devdependency eslint-plugin-promise to ^5.1.0
  • 4bcc294 chore(deps): update devdependency eslint to ^7.24.0
  • 6ffb7ee chore(deps): update devdependency eslint-plugin-promise to v5
  • 8b9f920 chore(deps): update devdependency @​semantic-release/npm to ^7.1.1
  • b291a6b chore(deps): update node.js to >=v10.24.1
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/yads/nodemailer-express-handlebars/network/alerts).
imnotteixeira commented 2 years ago

Hey @yads, could we get this merged, please? It's causing some downstream audit problem in dependent packages as can be seen in #53 and #38, for example. It is also affecting @BrunoRosendo and me in a project of ours. Since we are not using npm>8, we can't override transitive versions yet, so the fix must come from your side.

Thank you

imnotteixeira commented 2 years ago

Thank you @yads, does it auto-publish to npm? Can you update it there if not?