-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore(deps): update all non-major dependencies #46
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/all-minor-patch
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
May 17, 2021 17:34
4b47474
to
97977bf
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 2, 2021 15:10
97977bf
to
4ada85a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
June 23, 2021 14:20
24ee869
to
cefe6d9
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 18, 2021 19:44
cefe6d9
to
93f5415
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 7, 2022 10:38
93f5415
to
174e0d8
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 24, 2022 18:51
174e0d8
to
7b378c2
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
May 16, 2022 00:28
7b378c2
to
5221f8f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 25, 2022 17:53
5221f8f
to
b49a260
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 20, 2022 21:20
b49a260
to
991367d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 16, 2023 22:00
991367d
to
2c4ac50
Compare
renovate
bot
changed the title
fix(deps): update all non-major dependencies
chore(deps): update all non-major dependencies
Mar 16, 2023
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
May 28, 2023 11:53
2c4ac50
to
a2eaf72
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 26, 2023 18:29
a2eaf72
to
6cc0615
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 1, 2023 04:54
6cc0615
to
56c486c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
August 17, 2023 02:09
56c486c
to
7b47b3e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
January 5, 2024 10:04
3343959
to
5363fbb
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
April 2, 2024 22:37
461a0d9
to
db44a0c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 4, 2024 17:24
db44a0c
to
b4daf54
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 17, 2024 15:52
b4daf54
to
6da8a0b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 26, 2024 02:57
6da8a0b
to
83eedb5
Compare
renovate
bot
changed the title
chore(deps): update all non-major dependencies
chore(deps): update akhileshns/heroku-deploy action to v3.13.15
Dec 8, 2024
renovate
bot
changed the title
chore(deps): update akhileshns/heroku-deploy action to v3.13.15
chore(deps): update all non-major dependencies
Dec 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.
This PR contains the following updates:
v3.12.12
->v3.13.15
0.95.4
->0.95.15
8.6.0
->8.13.1
2.7.1
->2.8.0
5.0.2
->5.1.7
3.6.0
->3.6.11
3.6.0
->3.6.11
3.6.0
->3.6.11
3.6.0
->3.6.11
3.6.0
->3.6.11
3.6.0
->3.6.11
3.6.0
->3.6.11
3.6.0
->3.6.11
3.6.0
->3.6.11
3.6.0
->3.6.11
3.6.0
->3.6.11
Release Notes
akhileshns/heroku-deploy (akhileshns/heroku-deploy)
v3.13.15
Compare Source
Updated node version to "node20" (as "node18" is not supported by GitHub Actions)
v3.13.14
Compare Source
Updated node version from 16 to 18 (as 16 is causing problems due to deprecation)
v3.12.14
Compare Source
setOutput
call problems in the future(Thanks to @arg, @clickclickonsal, @romack and @fabn for the suggestion)
v3.12.13
Compare Source
Switched to node 16 due to deprecation of node 12 (Thank you to @brtrick for PR)
knex/knex (knex)
v0.95.15
Compare Source
Bug fixes:
v0.95.14
Compare Source
Bug fixes:
v0.95.13
Compare Source
Bug fixes:
Typings:
v0.95.12
Compare Source
New features:
Bug fixes:
Typings:
v0.95.11
Compare Source
New features:
Bug fixes:
Improvements:
v0.95.10
Compare Source
Improvements:
Typings:
v0.95.9
Compare Source
New features:
Typings:
v0.95.8
Compare Source
New features:
Bug fixes:
Typings:
v0.95.7
Compare Source
New features:
Typings:
v0.95.6
Compare Source
Typings:
v0.95.5
Compare Source
New features:
Bug fixes:
Typings:
brianc/node-postgres (pg)
v8.13.1
Compare Source
v8.13.0
Compare Source
v8.12.0
Compare Source
queryMode
config option to force use of the extended query protocol on queries without any parameters.v8.11.6
Compare Source
v8.11.5
Compare Source
v8.11.4
Compare Source
v8.11.3
Compare Source
v8.11.2
Compare Source
v8.11.1
Compare Source
v8.11.0
Compare Source
v8.10.0
Compare Source
release
event when client is returned to the pool.v8.9.0
Compare Source
v8.8.0
Compare Source
pool.query
.allowExitOnIdle
is enabled).lock_timeout
in client config.pg-pool@3.5.0
pg@8.7.0
pg-cursor@2.7.0
pg@8.6.0
--isolatedModules
.pg-query-stream@4.0.0
pg@8.5.0
pg@8.4.0
DatabaseError
from pg-protocol.sslmode
in the connection string.pg@8.3.0
{ options: string }
field on client/pool config.pg@8.2.0
pg-cursor@2.2.0
pg-query-stream@3.1.0
pg@8.1.0
pg-connection-string
. This includes better support for SSL argument parsing from connection strings and ensures continuity of support.&ssl=no-verify
option to connection string andPGSSLMODE=no-verify
environment variable support for the pure JS driver. This is equivalent of passing{ ssl: { rejectUnauthorized: false } }
to the client/pool constructor. The advantage of having support in connection strings and environment variables is it can be "externally" configured via environment variables and CLI arguments much more easily, and should remove the need to directly edit any application code for the SSL default changes in 8.0. This should make usingpg@8.x
significantly less difficult on environments like Heroku for example.pg-pool@3.2.0
pg
impactpg-pool
as they both use the same connection parameter and connection string parsing code for configuring SSL.pg-pool@3.1.0
pg@8.0.0
note: for detailed release notes please check here
6 lts
from the test matrix.pg>=8.0
may still work on older versions but it is no longer officially supported.rejectUnauthorized
with the SSL connection parameters. Previously we defaulted torejectUnauthorized: false
when it was not specifically included. We now default torejectUnauthorized: true.
Manually specify{ ssl: { rejectUnauthorized: false } }
for old behavior.user
config option if available. Previouslyprocess.env.USER
was used.pg.Pool
andpg.Query
to be an es6 class.pg.native
non enumerable.notice
messages are no longer instances ofError
.pg@7.18.0
rejectUnauthorized
fromfalse
totrue
making things more secure in the general use case.pg-query-stream@3.0.0
stream.close
tostream.destroy
which is the official way to terminate a readable stream. This is a breaking change if you rely on thestream.close
method on pg-query-stream...though should be just a find/replace type operation to upgrade as the semantics remain very similar (not exactly the same, since internals are rewritten, but more in line with how streams are "supposed" to behave).config.batchSize
andconfig.highWaterMark
to both do the same thing: control how many rows are buffered in memory. TheReadableStream
will manage exactly how many rows are requested from the cursor at a time. This should give better out of the box performance and help with efficient async iteration.pg@7.17.0
idle_in_transaction_session_timeout
option.7.16.0
7.15.0
new
.7.14.0
7.13.0
7.12.0
7.11.0
7.10.0
7.9.0
7.8.0
7.7.0
7.6.0
7.5.0
null
orundefined
toclient.query
.7.4.0
7.3.0
7.2.0
7.1.0
Enhancements
7.0.0
Breaking Changes
4.x
.pg.connect
pg.end
andpg.cancel
singleton methods.Client#connect(callback)
now returnsundefined
. It used to return an event emitter.2.x
.2.x
.SELECT 1; SELECT 2;
are now returned as an array of results instead of a single result with 1 array containing rows from both queries.Please see here for a migration guide
Enhancements
Client#connect() => Promise<void>
andClient#end() => Promise<void>
calls. Promises are now returned from all async methods on clients if and only if no callback was supplied to the method.connectionTimeoutMillis
to pg-pool.v6.2.0
replicationStart
messages.v6.1.0
client.end
method. The native client already supported this.v6.0.0
Breaking Changes
pg.pools
. There is still a reference kept to the pools created & tracked bypg.connect
but it has been renamed, is considered private, and should not be used. Accessing this API directly was uncommon and was supposed to be private but was incorrectly documented on the wiki. Therefore, it is a breaking change of an (unintentionally) public interface to remove it by renaming it & making it private. Eventuallypg.connect
itself will be deprecated in favor of instantiating pools directly vianew pg.Pool()
so this property should become completely moot at some point. In the mean time...check out the new features...New features
pg.connect
. The pg-pool constructor is exported from node-postgres atrequire('pg').Pool
. It provides a backwards compatible interface withpg.connect
as well as a promise based interface & additional niceties.You can now create an instance of a pool and don't have to rely on the
pg
singleton for anything:Promise support & other goodness lives now in pg-pool.
Please read the readme at pg-pool for the full api.
This should help with backends incorrectly considering idle clients to be dead and prematurely disconnecting them.
v5.1.0
client.query
implement the promise interface. This is the first step towards promisifying more of the node-postgres api.Example:
v5.0.0
Breaking Changes
require('pg').native
now returns null if the native bindings cannot be found; previously, this threw an exception.New Features
undefined
as a query parameterdefaults.connectionString
returnToHead
being passed to generic poolv4.5.0
v4.4.0
stderr
if a named query exceeds 63 characters which is the max length supported by postgres.v4.3.0
pg-types
semver. Allow it to float againstpg-types@1.x
.v4.2.0
v4.1.0
v4.0.0
npm install pg-native
try/catch
block.v3.6.0
v3.5.0
v3.4.0
v3.2.0
v3.1.0
end
frompg
object when a pool is drainedv3.0.0
Breaking changes
After some discussion it was decided node-postgres was non-compliant in how it was handling DATE results. They were being converted to UTC, but the PostgreSQL documentation specifies they should be returned in the client timezone. This is a breaking change, and if you use the
date
type you might want to examine your code and make sure nothing is impacted.pg@v2.0 included changes to not convert large integers into their JavaScript number representation because of possibility for numeric precision loss. The same types in arrays were not taken into account. This fix applies the same type of type-coercion rules to arrays of those types, so there will be no more possible numeric loss on an array of very large int8s for example. This is a breaking change because now a return type from a query of
int8[]
will contain string representationsof the integers. Use your favorite JavaScript bignum module to represent them without precision loss, or punch over the type converter to return the old style arrays again.
Single
date
parameters were properly sent to the PostgreSQL server properly in local time, but an input array of dates was being changed into utc dates. This is a violation of what PostgreSQL expects. Small breaking change, but none-the-less something you should check out if you are inserting an array of dates.end
event if it ends due to an errorThis is a small change to bring the semantics of query more in line with other EventEmitters. The tests all passed after this change, but I suppose it could still be a breaking change in certain use cases. If you are doing clever things with the
end
anderror
events of a query object you might want to check to make sure its still behaving normally, though it is most likely not an issue.New features
prepareValue
The long & short of it is now any object you supply in the list of query values will be inspected for a
.toPostgres
method. If the method is present it will be called and its result used as the raw text value sent to PostgreSQL for that value. This allows the same type of custom type coercion on query parameters as was previously afforded to query result values.If domains are active node-postgres will honor them and do everything it can to ensure all callbacks are properly fired in the active domain. If you have tried to use domains with node-postgres (or many other modules which pool long lived event emitters) you may have run into an issue where the active domain changes before and after a callback. This has been a longstanding footgun within node-postgres and I am happy to get it fixed.
Avoids a scenario where your pool could fill up with disconnected & unusable clients.
To provide better documentation and a clearer explanation of how to override the query result parsing system we broke the type converters into their own module. There is still work around removing the 'global-ness' of the type converters so each query or connection can return types differently, but this is a good first step and allow a lot more obvious way to return int8 results as JavaScript numbers, for example
v2.11.0
v2.10.0
v2.9.0
v2.8.0
v2.7.0
v2.6.0
v2.5.0
pg.defaults.parseInt8 = true
v2.4.0
v2.3.0
Due to the low usage & required compiled dependency this will be pushed into a 3rd party add-on
v2.2.0
v2.1.0
v2.0.0
For more information see https://github.com/brianc/node-postgres/pull/353
If you are unhappy with these changes you can always override the built in type parsing fairly easily.
v1.3.0
v1.2.0
v1.1.0
JSON
data type for PostgreSQL Server @ v9.2.0 or greaterv1.0.0
pg.connect
now requires 3 argumentsString
v0.15.0
end
when disconnected from back-end serverv0.14.0
v8.7.3
Compare Source
v8.7.1
Compare Source
v8.7.0
Compare Source
frontend-collective/react-sortable-tree (react-sortable-tree)
v2.8.0
Compare Source
Features
Bug Fixes
TryGhost/node-sqlite3 (sqlite3)
v5.1.7
Compare Source
What's Changed
@mapbox/node-pre-gyp
withprebuild
+prebuild-install
(TryGhost/node-sqlite3@605c7f9) by @daniellockyerRowToJS
performance by removingNapi::String::New
instantiation by @daniellockyerNew Contributors
Full Changelog: TryGhost/node-sqlite3@v5.1.6...v5.1.7
v5.1.6
Compare Source
What's Changed
log2
by @daniellockyerNew Contributors
Full Changelog: TryGhost/node-sqlite3@v5.1.5...v5.1.6
v5.1.5
[Com
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.