@bastani/atomic-storage-postgres 0.9.90-alpha.1 → 0.9.90
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +12 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,18 @@
|
|
|
2
2
|
|
|
3
3
|
## [Unreleased]
|
|
4
4
|
|
|
5
|
+
## [0.9.90] - 2026-11-19
|
|
6
|
+
|
|
7
|
+
### Added
|
|
8
|
+
|
|
9
|
+
- Connections through an HTTP proxy: where the only way out is a proxy that opens `CONNECT` tunnels, such as a sandbox's, every connection to PostgreSQL (the pool's, the wake-ups connection and cancel requests, and their reconnects) tunnels through the proxy `HTTPS_PROXY` names, then `ALL_PROXY` or `HTTP_PROXY`, unless `NO_PROXY` exempts the database host, as for Atomic's other HTTPS clients; a database on this machine is reached directly. The new `proxy` option, an `http://` or `https://` URL or `"none"`, overrides the environment, and SDK callers can pass `socket`, a function that opens each connection, for a custom transport. TLS still runs end to end with the server: with the default `verify-full` (or `require` without `sslrootcert`) it checks the certificate against the database's host name, so the proxy sees only encrypted traffic, cancel requests included. `verify-ca` does not check the host name, so it keeps the proxy out only with an `sslrootcert` CA that signs your database servers alone; `prefer`, `allow` and `disable` let a proxy read the traffic. A proxy that refuses the tunnel fails the open with `StorageUnavailableError` naming the proxy, without its credentials, and the `host:port` it refused, and the warning an open prints while it retries a proxy that cannot be reached names the proxy rather than the database server. If you already set `HTTPS_PROXY` (or Atomic's `httpProxy` setting) and reach a remote database directly, its connections now go through that proxy: add the database host to `NO_PROXY`, or set the `proxy` option to `"none"`, to keep them direct ([#5473](https://github.com/bastani-inc/atomic/issues/5473))
|
|
10
|
+
|
|
11
|
+
### Fixed
|
|
12
|
+
|
|
13
|
+
- A URL that names no host, used with `PGHOST`, now gets the same default `sslmode=verify-full` as a URL naming that host when `PGHOST` is not this machine, instead of connecting without TLS. A URL that names this machine in another spelling, such as `127.1`, `localhost.` or `[::ffff:127.0.0.1]`, no longer gets a default `sslmode=verify-full`, which a local server without TLS refused: it is treated as this machine, like `localhost` and `127.0.0.1` ([#5473](https://github.com/bastani-inc/atomic/issues/5473))
|
|
14
|
+
- Wake-ups no longer turn off for the rest of the process when the check of the listening connection had to open a new pool connection that took longer than 2 seconds, as through a slow proxy or while a cloud identity issues its first token. The check now waits for its notification only once it was sent ([#5473](https://github.com/bastani-inc/atomic/issues/5473))
|
|
15
|
+
- Proxy tunnels no longer fail when the proxy sends an informational reply such as `103 Early Hints` before the final `200`. The 16 KiB header limit and 8-second timeout cover all replies together, not the database traffic that follows. A proxy whose connection ends right after a CR byte of its answer is reported as closed, which the open retries, instead of as an answer that is not HTTP, which it never retries. A CR inside a header field that no LF follows is read as a space, so the answer's final status decides. A CR in a status line is still refused, and a CR where `HTTP/` should start an answer is now refused at once instead of after the 8-second deadline ([#5565](https://github.com/bastani-inc/atomic/issues/5565), [#5670](https://github.com/bastani-inc/atomic/issues/5670))
|
|
16
|
+
|
|
5
17
|
## [0.9.90-alpha.1] - 2026-11-19
|
|
6
18
|
|
|
7
19
|
### Added
|
package/package.json
CHANGED