This repository was archived by the owner on Sep 20, 2021. It is now read-only.
[Snyk] Upgrade connect-pg-simple from 6.1.0 to 6.2.1#231
Open
snyk-bot wants to merge 1 commit into
Open
Conversation
Snyk has created this PR to upgrade connect-pg-simple from 6.1.0 to 6.2.1. See this package in npm: https://www.npmjs.com/package/connect-pg-simple See this project in Snyk: https://app.snyk.io/org/cds-snc/project/88c1d267-b9fd-4968-80e6-67a901d47fd1?utm_source=github&utm_medium=upgrade-pr
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Snyk has created this PR to upgrade connect-pg-simple from 6.1.0 to 6.2.1.
ℹ️ 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.
Release notes
Package name: connect-pg-simple
-
6.2.1 - 2020-08-19
- Fix: Regression, query errors wasn't properly forwarded. Fixes #180 and #179. Thanks @ alxndrsn! (5c324ac)
- Test: Added test for above regression (fd36978)
- Change: Improved types + error return values (f73ea0d 68a2242)
- Change: Updated SECURITY.md to delegate security reports to Tidelift, and thus ensure quicker responses (7683d40 59c7fbc)
-
6.2.0 - 2020-08-06
- Important fix: Bump pg to 8.2.1 to support node 14+
- Change: Change default prine interval to 15 mins
- Test: Add Node 14 to GitHub CI
- Test: Added more types and type linting
-
6.1.0 - 2019-12-29
- Feature: Prune intervals are now by default randomized between 50% and 150% of the set prune value, making the average prune interval be the same as before, but makes database load more even by making it unlikely for eg. many instances to all prune at once.
- Feature: New option
- Change: Default prune interval is now
- Performance: The database schema definition now specifies an index on the
from connect-pg-simple GitHub release notesv6.2.0...v6.2.1
v6.1.0...v6.2.0
pruneSessionRandomizedIntervalenables deactivation + customization of the new random prune interval feature.5minutes, rather than1minute. No need to clean extremely often. Will probably make even longer eventually, but a more drastic change could be kind of a breaking change. Please comment in #162 with feedback on future default.expirecolumn. You have to add this yourself if you have already set up this module. The change is purely for enhancing performance and can be skipped if no performance issues have been experiences. It is recommended to apply it though.v6.0.1...v6.1.0
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