@rc312/effect-snowflake 0.1.0 → 0.2.0

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @rc312/effect-snowflake
 
+## 0.2.0
+
+### Minor Changes
+
+- Upgrade Effect support to 4.1.2 and require Node.js 22.19 or newer to match Effect's runtime requirements.
+
+  Effect 4.1 promotes typed failures to defects when combined with cleanup defects. Snowflake transaction failures retain both the original error and the cleanup error in the combined Cause.
+
 ## 0.1.0
 
 ### Minor Changes

package/README.md

@@ -8,7 +8,7 @@ An Effect 4 client for Snowflake through Apache Arrow ADBC. Queries return Arrow
 bun add @rc312/effect-snowflake effect apache-arrow@^21.1.0
 ```
 
-Use Node.js 22.12 or newer. This is a server-only package with a native dependency. The package includes the JavaScript ADBC driver manager; install the Snowflake shared-library driver separately:
+Use Node.js 22.19 or newer. This is a server-only package with a native dependency. The package includes the JavaScript ADBC driver manager; install the Snowflake shared-library driver separately:
 
 ```sh
 npm install -g @columnar-tech/dbc
@@ -128,7 +128,7 @@ const insert = db.transaction((tx) =>
 
 Transactions reserve the connection, disable autocommit, and serialize work on the supplied session. Use `tx` inside the callback and await its work. Returning from the callback closes its child scope and expires the session before commit. Typed failures, defects, and interruption trigger rollback. Failed commits also attempt rollback. Successful completion or rollback restores autocommit.
 
-Failed reader/statement cleanup, rollback, or autocommit restoration invalidates the client; no further operation is accepted. Recovering a cleanup defect within the callback still prevents commit: the transaction fails with operation `transaction.invalidated` and attempts rollback. Autocommit is never re-enabled after a failed rollback, because doing so could commit pending changes. Cleanup failures are preserved as defects alongside the original failure. Acquire a new client after invalidation.
+Failed reader/statement cleanup, rollback, or autocommit restoration invalidates the client; no further operation is accepted. Recovering a cleanup defect within the callback still prevents commit: the transaction fails with operation `transaction.invalidated` and attempts rollback. Autocommit is never re-enabled after a failed rollback, because doing so could commit pending changes. Cleanup failures are preserved as defects alongside the original failure. In Effect 4.1, a cleanup defect also promotes the original typed failure to a defect in the combined Cause. Acquire a new client after invalidation.
 
 Only the callback is interruptible. Once commit starts, the adapter finishes commit and autocommit restoration before releasing the connection. Interruption during a successful commit does not trigger a subsequent rollback; the caller may still observe interruption after the commit completes.
 
@@ -173,5 +173,3 @@ bun run lint
 ```
 
 Unit tests use real Arrow IPC and controlled native resources for precision, acquisition and reader failures, serialized work, combined cleanup causes, transaction interruption, scope retirement, and tracing redaction. The examples and E2E sources are included in typechecking. Coverage reports are written under the package's ignored `coverage/` directory; the live suite runs separately from ordinary unit tests.
-
-The lifecycle ownership helpers were adapted from the provided `effect-extensions-copy/src/waddler/snowflake.ts` reference implementation.

package/examples/README.md

@@ -15,7 +15,7 @@ cp packages/effect-snowflake/examples/.env.example packages/effect-snowflake/.en
 
 Edit `packages/effect-snowflake/.env` for a development account, warehouse, database, and schema. The template uses JWT authentication and a private-key file path. For inline keys, remove `SNOWFLAKE_PRIVATE_KEY_PATH` and set `SNOWFLAKE_PRIVATE_KEY` to a PKCS#8 PEM. `SNOWFLAKE_PRIVATE_KEY_PASS` supplies an encrypted inline key's passphrase. For password authentication, set `SNOWFLAKE_AUTHENTICATOR=auth_snowflake` and `SNOWFLAKE_PASSWORD`; for OAuth use `auth_oauth` and `SNOWFLAKE_TOKEN`.
 
-The examples need Node.js 22.12+ and Bun for workspace build scripts. The Node entrypoints load the package-local `.env` using `--env-file-if-exists`; exported environment variables take precedence. Real `.env` files are ignored by Git. Do not commit credentials. Secrets are loaded through `Config.Redacted`, and the configuration check never prints their values.
+The examples need Node.js 22.19+ and Bun for workspace build scripts. The Node entrypoints load the package-local `.env` using `--env-file-if-exists`; exported environment variables take precedence. Real `.env` files are ignored by Git. Do not commit credentials. Secrets are loaded through `Config.Redacted`, and the configuration check never prints their values.
 
 If manifest discovery is unavailable, set `SNOWFLAKE_ADBC_DRIVER` to the absolute path of an installed driver library or manifest. The shared configuration sets native login and network timeouts to 30 seconds and request retries to 60 seconds. These bound individual native operations; they are not an overall scenario deadline.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rc312/effect-snowflake",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Scoped Effect 4 Snowflake client with Apache Arrow ADBC queries, streams, and transactions.",
   "license": "MIT",
   "repository": {
@@ -46,16 +46,16 @@
     "@apache-arrow/adbc-driver-manager": "~0.24.0"
   },
   "devDependencies": {
-    "@effect/vitest": "^4.0.5",
+    "@effect/vitest": "^4.1.2",
     "@types/node": "^26.6.5",
     "@vitest/coverage-v8": "5.0.4",
     "vitest": "^5.0.4"
   },
   "peerDependencies": {
     "apache-arrow": "^21.1.0",
-    "effect": "^4.0.5"
+    "effect": "^4.1.2"
   },
   "engines": {
-    "node": ">=22.12.0"
+    "node": ">=22.19.0"
   }
 }