Skip to content
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

Bump express and lisk-sdk #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Dec 10, 2022

Bumps express to 4.17.3 and updates ancestor dependency lisk-sdk. These dependencies need to be updated together.

Updates express from 4.16.4 to 4.17.3

Release notes

Sourced from express's releases.

4.17.3

4.17.2

4.17.1

  • Revert "Improve error message for null/undefined to res.status"

4.17.0

  • Add express.raw to parse bodies into Buffer
  • Add express.text to parse bodies into string

... (truncated)

Changelog

Sourced from express's changelog.

4.17.3 / 2022-02-16

4.17.2 / 2021-12-16

4.17.1 / 2019-05-25

... (truncated)

Commits

Updates lisk-sdk from 2.3.6 to 5.2.2

Release notes

Sourced from lisk-sdk's releases.

Version 5.2.2

Change Log

v5.2.2 (2022-05-02)

Full Changelog

This release upgrades NodeJS to the latest LTS version, and fixes security bugs found on the blockchain syncing mechanism.

Released packages

Patch releases

  • [email protected]
  • @​liskhq/lisk-api-client@​5.1.6
  • @​liskhq/lisk-bft@​0.3.4
  • @​liskhq/lisk-chain@​0.3.4
  • @​liskhq/lisk-client@​5.2.2
  • @​liskhq/lisk-codec@​0.2.2
  • @​liskhq/lisk-cryptography@​3.2.1
  • @​liskhq/lisk-db@​0.2.1
  • [email protected]
  • @​liskhq/lisk-genesis@​0.2.4
  • @​liskhq/lisk-p2p@​0.7.3
  • @​liskhq/lisk-passphrase@​3.1.1
  • @​liskhq/lisk-transaction-pool@​0.5.3
  • @​liskhq/lisk-transactions@​5.2.2
  • @​liskhq/lisk-tree@​0.2.2
  • @​liskhq/lisk-utils@​0.2.1
  • @​liskhq/lisk-validator@​0.6.2
  • [email protected]
  • @​liskhq/lisk-framework-dashboard-plugin@​0.1.7
  • @​liskhq/lisk-framework-faucet-plugin@​0.1.7
  • @​liskhq/lisk-framework-forger-plugin@​0.2.7
  • @​liskhq/lisk-framework-http-api-plugin@​0.2.7
  • @​liskhq/lisk-framework-monitor-plugin@​0.2.7
  • @​liskhq/lisk-framework-report-misbehavior-plugin@​0.2.7

Improvements

  • Update Node.js version and dependencies #7062
  • Update package description and license #7083

Bugs

  • Issues with block synchronization mechanism on validator change #7151

Closed issues:

... (truncated)

Commits
  • 1ce8dd7 Merge branch 'hotfix/5.2.2'
  • bde8ddc ⬆️ Bump version 5.2.2
  • a56ab69 ⬆️ Bump version 5.2.2
  • 9769259 Merge pull request #155 from LiskHQ/7083-update_package
  • df21bd9 ♻️ Update yarn.lock
  • 6db616a ⬆️ Bump dependencies
  • 3ad5ca7 📚 Update package description and readme version
  • fd44028 ⬆️ Bump version
  • f5616a1 Merge pull request #154 from LiskHQ/153-sync-issue-after-restart
  • 85cf6ec 💅 Fix format
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by ishantiw, a new releaser for lisk-sdk since your current version.


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.

Bumps [express](https://github.com/expressjs/express) to 4.17.3 and updates ancestor dependency [lisk-sdk](https://github.com/LiskHQ/lisk-sdk). These dependencies need to be updated together.


Updates `express` from 4.16.4 to 4.17.3
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](expressjs/express@4.16.4...4.17.3)

Updates `lisk-sdk` from 2.3.6 to 5.2.2
- [Release notes](https://github.com/LiskHQ/lisk-sdk/releases)
- [Commits](LiskArchive/lisk-sdk@v2.3.6...v5.2.2)

---
updated-dependencies:
- dependency-name: express
  dependency-type: indirect
- dependency-name: lisk-sdk
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants