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

refactor: Upgrade pg-promise from 11.5.0 to 11.5.4 #8924

Merged
merged 2 commits into from
Feb 16, 2024

Conversation

parseplatformorg
Copy link
Contributor

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


Snyk has created this PR to upgrade pg-promise from 11.5.0 to 11.5.4.

ℹ️ 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 4 versions ahead of your current version.
  • The recommended version was released 6 months ago, on 2023-08-22.
Release notes
Package name: pg-promise
  • 11.5.4 - 2023-08-22
    • Dependencies updated, including the driver, to v8.11.3
  • 11.5.3 - 2023-08-02
    • Following up on driver fix-update, see issue #888
  • 11.5.2 - 2023-07-28

    This update is to clarify the full range of environments officially supported:

    • PostgreSql v10 - v15
    • NodeJS v14 - v18

    It is worth noting that:

    • It may work with PostgreSql v9, but it is no longer officially supported.
    • It should work with NodeJS v20, but it is not officially supported yet (we support LTS versions of NodeJS only).

    The CI has been updated accordingly. No functional changes.

  • 11.5.1 - 2023-07-23
    • Updated dependencies, including the driver, to v8.11.1
    • Fixed #884 - CI build issue in test
  • 11.5.0 - 2023-05-27
    • Many dependencies updated, including Postgres driver.
    • Minor documentation updates.

    Please note that at the time of publishing this, GitHub CI started showing problems again, unrelated to the project. All tests pass locally fine, disregard Failed Build status for the time being.

from pg-promise GitHub release notes
Commit messages
Package name: pg-promise

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

Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Upgrade pg-promise from 11.5.0 to 11.5.4 refactor: Upgrade pg-promise from 11.5.0 to 11.5.4 Feb 16, 2024
Copy link

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

Copy link

codecov bot commented Feb 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (d0a5af3) 94.32% compared to head (88b3c6c) 94.32%.

Additional details and impacted files
@@              Coverage Diff               @@
##           release-6.x.x    #8924   +/-   ##
==============================================
  Coverage          94.32%   94.32%           
==============================================
  Files                186      186           
  Lines              14827    14827           
==============================================
  Hits               13985    13985           
  Misses               842      842           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mtrezza mtrezza merged commit 223fde0 into release-6.x.x Feb 16, 2024
28 checks passed
@mtrezza mtrezza deleted the snyk-upgrade-bc0df002cbeecc5e016c7fe05e69ff0f branch February 16, 2024 23:41
@parseplatformorg
Copy link
Contributor Author

🎉 This change has been released in version 6.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants