connect-pg-simple - npm Package Versions

10.0.0 (2024-09-13)

⚠ BREAKING CHANGES

• require node.js >=18

🩹 Fixes

• add name to main function (c98e2ec)
• deps: use latest version of pg (81b5630)
• require node.js >=18 (d51b6ca)

🧹 Chores

• deps: update knip (f78ef50)
• deps: update validate-conventional-commit (84f525a)
• deps: update dependency dotenv to ^16.4.5 (#308) (f97bd51)
• deps: update dependency express to ^4.21.0 (#310) (01c9a55)
• deps: update dependency express-session to ^1.18.0 (#309) (eef0e31)
• deps: update dependency pg-promise to ^11.9.1 (#312) (a553301)
• deps: update dev dependencies (d4488dc)
• deps: update dev dependencies (21e41c4)
• deps: update linting dependencies (817f082)
• deps: update linting dependencies (a4e9e46)
• deps: update type dependencies (97e581f)
• deps: update typescript setup (7c86411)
• deps: use neostandard linting (354f6b3)
• fix @types/superagent type regression (649888c)

9.0.1 (2023-11-01)

Bug Fixes

• 18: Move @types/pg to dev dependencies (ea4a9c1)

9.0.0 (2023-06-07)

• Breaking change: Require Node version >=16.0.0
• Notable: Start automatic pruning lazily. Wait for first use of the session manager before scheduling the pruning. #285
• Change: Log whole error object instead of only message. Thanks @safareli! #225
• ...and internal updates to dev dependencies etc

8.0.0 (2022-11-12)

• Breaking change: Require Node version ^14.18.0 || >=16.0.0
• Notable: Mark most private methods and properties as actually private using the Private class feature (having the name begin with a #) This can be breaking if you relied on those properties or methods
• Internal: Update included version of pg
• Internal: Use node: to import built in modules
• ...and a lot of updates to dev dependencies, GitHub Action workflows etc

7.0.0 (2021-09-06)

• Breaking change: Now requires at least Node.js 12.x
• Internal: Updated some developer dependencies and test targets
• As well as all changes in 7.0.0-0

7.0.0-0 (2021-01-18)

• Possibly breaking change: Align session expiration logic with connect-redis which in turned aligned with connect-mongo. Fixes #54.
• Minor breaking change: The .close() method is now async and returns a Promise that will be resolved when this session store is fully shut down. Fixes #183.
• Minor breaking change: Now requires Node version ^10.17.0 || >=11.14.0
• Feature: New option: disableTouch. Disables updating of TTL in database on touch. Fixes #55.
• Feature: New option: createTableIfMissing. When set, the session table will be automatically created if missing. Fixes #158 and #173. Thanks @aadeshmisra!
• Tweak: Slightly tweaked the pg-promise integration. Fixes #153.
• Tweak: Introduced a new internal _asyncQuery() function in a move to modernize internal code on top of Promise / async / await.

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 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!