[Snyk] Upgrade express-http-proxy from 1.6.0 to 1.6.3

[andersonsevla]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade express-http-proxy from 1.6.0 to 1.6.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 3 versions ahead of your current version.
• The recommended version was released 3 years ago, on 2021-10-26.

Release notes

Package name: express-http-proxy

• 1.6.3 - 2021-10-26
  

  Allow author to delete headers in userResHeaderDecorator.

• 1.6.2 - 2020-07-21
  

  Update node.js versions used in ci build.

• 1.6.1 - 2020-07-20
  

  Small bug fixes and documentation enhancements.

• 1.6.0 - 2019-09-25

from express-http-proxy GitHub release notes

Commit messages

Package name: express-http-proxy

• e2474ea 1.6.3
• f6881dc Bump y18n from 4.0.0 to 4.0.1
• 7c25ccc Bump lodash from 4.17.19 to 4.17.21
• 0363c66 Bump glob-parent from 5.1.1 to 5.1.2
• 2aec188 [#453] Author should be able to delete headers in userResHeaderDecorator.
• 1692a00 Remove outdated Gemnaisum badge from README header.
• 3de3f76 1.6.2
• 1a595f0 Update README for patch version.
• 7d75db7 Update node.js versions used in ci.
• 42cc849 1.6.1
• a0d5e72 Update release notes for 1.6.1.
• 5527c1b Update dependencies.
• 9e28f9b [adhoc] fixes trivial misspelling.
• f53e7ee Create node.js.yml
• 1983acc Add important note about 'body-parser'
• 7358c01 [#422] Correct misspelling.

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[backstage-rdstation]

Olá! Obrigado por enviar o pull request para atualizar o pacote express-http-proxy. No entanto, a descrição do pull request não explica claramente o motivo da atualização. Seria importante incluir informações sobre o contexto histórico da mudança, a justificativa ou o racional por trás dela. Além disso, seria útil adicionar um passo a passo ou instruções de teste para facilitar a revisão e teste do pull request. Escrever uma descrição mais detalhada e informativa pode ajudar a equipe a entender melhor as mudanças propostas. Se precisar de ajuda para melhorar a descrição, estou à disposição para auxiliar. Obrigado!

Esse comentário foi gerado por inteligência artificial