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 connect-pg-simple from 3.1.2 to 6.1.0 in /art #5

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 Apr 21, 2020

Bumps connect-pg-simple from 3.1.2 to 6.1.0.

Release notes

Sourced from connect-pg-simple's releases.

v6.1.0

  • 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 pruneSessionRandomizedInterval enables deactivation + customization of the new random prune interval feature.
  • Change: Default prune interval is now 5 minutes, rather than 1 minute. 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.
  • Performance: The database schema definition now specifies an index on the expire column. 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.

voxpelli/node-connect-pg-simple@v6.0.1...v6.1.0

v6.0.1

  • Very minor security fix: schemaName and tableName wasn't escaped. If any of the two contained a string with a double quote in it, then that would enable an SQL injection. This was previously a feature of tableName, before the introduction of a separate schemaName, as that allowed a schema to be defined as part of tableName. Defining schema name through tableName is still supported after this fix, but is now deprecated.
  • Fix: Errors wasn't propagated properly. Fixed in #150. Thanks @bobnil!

voxpelli/node-connect-pg-simple@v6.0.0...v6.0.1

v6.0.0

  • Breaking change: Now requires at least Node.js 10.x, this as Node.js 8.x only have a short time left in its LTS
  • Breaking change: This project now uses INSERT ... ON CONFLICT, more popularly known as UPSERT. This is only supported on PostgreSQL version 9.5 and above.
  • Update pg-promise dev dependency to 9.x
  • Listen on pool errors. Fixes #29
  • Lots of dev dependency updates

voxpelli/node-connect-pg-simple@v5.0.0...v6.0.0

Changelog

Sourced from connect-pg-simple's changelog.

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 pruneSessionRandomizedInterval enables deactivation + customization of the new random prune interval feature.
  • Change: Default prune interval is now 5 minutes, rather than 1 minute. 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.
  • Performance: The database schema definition now specifies an index on the expire column. 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.

6.0.1 (2019-08-21)

  • Very minor security fix: schemaName and tableName wasn't escaped. If any of the two contained a string with a double quote in it, then that would enable an SQL injection. This was previously a feature of tableName, before the introduction of a separate schemaName, as that allowed a schema to be defined as part of tableName. Defining schema name through tableName is still supported after this fix, but is now deprecated.
  • Fix: Errors wasn't propagated properly. Fixed in #150. Thanks @bobnil!

6.0.0 (2019-07-28)

5.0.0 (2018-06-06)

  • Breaking change: Now requires at least Node.js 8.x (this as Node.js 6.x only have a short time left in its LTS and I rather don't bump the major version more often than I have to)
  • Breaking change: Now expects pg 7.x to be used
  • Fix: Connection string is now handled by pg instead of by this module. Should improve support for things like ssl.

4.2.1 (2017-08-20)

  • Fix: The pruning timer will no longer keep Node alive, it's been given the unref() treatment

4.2.0 (2017-05-20)

  • Feature: New option pgPromise enables the library to re-use an existing connection from pg-promise. This is a mutually-exclusive alternative to specifying pool, conObject, or conString (only one of these can be provided).

4.1.0 (2017-05-19)

  • Feature: New option conObject enables connection details to be set through an object
  • Improvement: Hardening of conString parsing + some added tests of it

4.0.0 (2017-05-19)

  • Breaking change + improved support: When the pg module is provided to this module, then a pool from the new 6.x version of that module is now required rather than providing the module itself
Commits
  • c2eb0ec 6.1.0
  • d4e2345 Update CHANGELOG
  • a23f307 Increase default prune interval to 5 minutes
  • e554d28 Feature: Make prune interval randomized by default
  • 91e3a55 Update dependency pg-promise to v10
  • 5398353 Update table.sql (#156)
  • ab8f8b1 Update linting + swap semistandard for own conf
  • d03fbf8 Update dev dependency express-session
  • 569c0a0 Update general dev dependencies
  • 8bb0d7b Typo fix
  • 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.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Apr 21, 2020
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.

None yet

0 participants