@voltro/plugin-duckdb 0.87.0 → 0.88.0

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.
Files changed (5) hide show
  1. package/CHANGELOG.md +169 -6
  2. package/THIRD-PARTY-NOTICES.md +647 -51
  3. package/dist/index.js +1 -2
  4. package/dist/sink.js +1 -2
  5. package/package.json +4 -4
package/CHANGELOG.md CHANGED
@@ -41,6 +41,166 @@ _Changes staged for the next release accumulate here (rolled up from
41
41
 
42
42
  ---
43
43
 
44
+ ## [0.88.0] — 2026-11-02
45
+
46
+ ### ⚠ BREAKING
47
+
48
+ - **Direct computed-cache key callers handle unencodable subjects** — `@voltro/runtime`, `@voltro/voltro`
49
+
50
+ `computedCacheKey()` can return `bypass: 'subject-not-encodable'` for claims that cannot safely identify a cache entry. Direct consumers with exhaustive bypass switches must handle this case by running without caching. `voltro update` identifies the direct imports to review. Queries using the native `cache:` declaration and `invoke()` tests need no manual key or code change.
51
+ - **The framework runs on effect 4.1.0** — `@voltro/cli`, `@voltro/devtools`, `@voltro/runtime`, `@voltro/database`, `@voltro/voltro`, `@voltro/sql-sqlite`, `@voltro/sql-mysql`, `@voltro/sql-mssql`, `@voltro/sql-postgres`
52
+
53
+ Every `@voltro/*` package now pins `effect` and its `@effect/*` companions to 4.1.0. Apps pin the same version and run `voltro add patches`: it writes the 4.1.0 patch files, retires the `patchedDependencies` entries an earlier CLI shipped for 4.0.1 (pnpm refuses an install over an unused patch) and moves the lockstep overrides. Two former patch fixes ship upstream in 4.1.0 (SQL Server request cancellation, the SQL Server message-storage MERGE). On SQL Server the shared transaction key now applies to every client in the process, not only the first one built.
54
+
55
+ `chunkRowsForInsert` from `@voltro/database` returns non-empty chunks (`NonEmptyReadonlyArray`), the shape effect 4.1's `sql.insert` requires; an empty input yields no chunk instead of one empty chunk.
56
+
57
+ SQL statement spans are named after their database, following the OpenTelemetry database conventions: the database name, else the server address, else the system name (`postgresql`, `mysql`, `microsoft.sql_server`, `sqlite`). Before, every statement span was `sql.execute`. Trace queries and dashboards that match that name should match the `db.query.text` attribute instead; the devtools trace panel and durable-trace sampling already do.
58
+
59
+ **`voltro update` carries you across this** — codemod `0.88.0/01_effect-4-1`. If you pin versions by hand and never run it, print the notes without changing anything: `voltro update --codemods-only --from <your current version> --dry-run` (this one ships in 0.88.0).
60
+ - **Runtime patch pins preserve third-party Effect majors** — `@voltro/cli`
61
+
62
+ `voltro add patches` scopes Effect pins to their current major instead of replacing unrelated libraries' Effect 3 dependencies. It migrates exact pins previously shipped by the framework, preserves unrelated policies, and refuses conflicting custom policies before writing files. In pnpm workspaces it names competing nonempty root `resolutions` or `pnpm.overrides` and explains their explicit reconciliation. Peer repair refuses cross-major global policy changes. Bun workspaces require Bun >=1.4.4 and a supported `packageManager` pin or `engines.bun` floor; upgrade the actual tool and older declarations before retrying, because Bun 1.2.0 ignored the scoped companion pin. `voltro update` carries the review as `0.88.0/06_effect-override-scope`.
63
+ - **Keep test runners out of production KV and workflow dependency closures** — `@voltro/kv`, `@voltro/workflow`
64
+
65
+ The test-only HotStore and workflow conformance suites now require their caller to supply runner operations. Pass `{ describe, it, expect }` as the third argument to `hotStoreConformance`, and `{ describe, test, expect, beforeAll, afterEach }` as the second argument to `runClusterEngineSuite` and `runJournalEncryptionSuite`. The exported structural runner interfaces have no dependency on Vitest. Both production packages remove their optional Vitest peer; an application's development runner can no longer enter a production deployment through those peer links. Keep Vitest in the test application's own devDependencies. Runtime KV/workflow calls and `runHotStoreSqlParity` are unchanged. `voltro update` identifies direct suite imports for review.
66
+ - **REST test handlers publish events under the request tenant** — `@voltro/testing`, `@voltro/cli`
67
+
68
+ When crossing 0.87.0, custom `makeTestApp({ restRoutes })` handlers receive a request-scoped `ctx.app` instead of the root fixture context. Event assertions must subscribe to that request tenant: the default anonymous request uses `acme` or `x-tenant`; an explicit `anonymous: 'no-tenant'` uses `''`, distinct from the event bus subscriber's default `null`. Pass the app's anonymous policy, select the subscriber tenant explicitly and assert delivered payloads even when HTTP success and `notified` already pass. Direct `invoke` retains its supplied context identity, and projected `publicApi` handlers already use request-scoped invocation. Plugin HTTP routes are not mounted by this request harness. `voltro update` locates raw request harness calls and prints the review steps.
69
+
70
+ ### Added
71
+
72
+ - **voltro add patches --ai accepts ai 7.0.156** — `@voltro/cli`, `@voltro/ai`
73
+
74
+ `voltro add patches --ai 7.0.156` wires the AI SDK declaration correction for `@ai-sdk/provider-utils` 5.0.70, regenerated with the original build from the release commit; JavaScript stays byte-identical to the published package. 7.0.105 and 7.0.132 remain selectable. `@voltro/ai` is built and tested against ai 7.0.156.
75
+ - **The retained invoice observations table is exported from the billing package** — `@voltro/plugin-billing`
76
+
77
+ `billingRetainedInvoiceObservationsTable` is exported from `@voltro/plugin-billing` beside the other billing tables, so an app can reference it.
78
+ - **plugin-billing accepts stripe 23** — `@voltro/plugin-billing`
79
+
80
+ The `stripe` peer range is `^22.6.1 || ^23.0.1`. stripe 23 pins Stripe API version `2026-09-30.endive`; the plugin still sends no `apiVersion` of its own, so the SDK's pinned version applies.
81
+
82
+ ### Changed
83
+
84
+ - **A booting server holds requests until the app is ready instead of answering 503** — `@voltro/runtime`, `@voltro/voltro`
85
+
86
+ `voltro serve`, `voltro start` and `voltro dev` used to answer every request that arrived before the boot finished with a plain-text `503 starting`. On a platform that scales to zero, that request is the visitor who woke the instance, and a browser does not act on `Retry-After` for a navigation. Requests and WebSocket upgrades that arrive while the app boots now wait and are handed to the app in arrival order once it is ready. The wait is bounded by `VOLTRO_BOOT_HOLD_MS` (default `30000`, at most five minutes, `0` restores the immediate `503`) and by 512 waiting requests. A request the wait cannot cover still gets `503` with `Retry-After: 1`, and a browser navigation gets a minimal page that reloads itself. `/internal/startup` reports waiting requests as `held`, and `bindBootListener` accepts `holdMs` and `maxHeld`. Probes are unchanged, so nothing changes under Kubernetes.
87
+ - **DocsLayout navigation nests collapsible groups with page counts** — `@voltro/ui-shadcn`
88
+
89
+ `DocsLayout` renders its sidebar as one tree: headerless groups are flat start links, other groups and sub-groups are collapsible rows with page counts, `DocsNavSubGroup` accepts nested `subgroups` and `trailingEntries`, the current page's link carries `aria-current="page"` (forwarded through `ShellLinkProps`), and the rail scrolls the active link into view after navigation.
90
+ - **Native Redis connections use ioredis 6 and keep the RESP2 protocol** — `@voltro/kv`, `@voltro/runtime`, `@voltro/cli`
91
+
92
+ The native Redis transport moved to ioredis 6, which defaults to RESP3. Registry connections set `protocol: 2`, so command replies, Pub/Sub and Lua results keep their shapes.
93
+ - **Connection drivers install only with the server runtime** — `@voltro/kv`, `@voltro/runtime`
94
+
95
+ `ioredis`, `@upstash/redis` and `@nats-io/transport-node` are optional peers of `@voltro/kv` and dependencies of `@voltro/runtime`. API apps keep all three without a step; web apps and SDKs that reach `@voltro/kv` only through types no longer download server drivers. Code that opens a connection without `@voltro/runtime` adds its driver, and a missing driver now fails naming the package.
96
+ - **The mobile template targets Expo SDK 58** — `@voltro/cli`
97
+
98
+ New mobile apps scaffold on Expo SDK 58 with React Native 0.88.1 and React 19.3.0, using the versions SDK 58 bundles for its native modules.
99
+ - **plugin-sentry runs on Sentry 11 and exports server spans over OTLP** — `@voltro/plugin-sentry`
100
+
101
+ Sentry 11 removed `SentrySpanProcessor`. The plugin now exports the framework's spans to the OTLP endpoint Sentry derives from the DSN and links errors and logs to the active span with `openTelemetryIntegration()`; the Sentry SDK records no spans of its own. `tracesSampleRate` keeps its meaning and is applied per trace id at the export. Server traces need the optional `@opentelemetry/sdk-trace-base` and `@opentelemetry/exporter-trace-otlp-http` packages (they replace `@sentry/opentelemetry`); without them the plugin warns and reports errors and breadcrumbs only. `init.tracesSampleRate` and `init.enableOpenTelemetrySetup` are ignored, and `init.skipOpenTelemetrySetup` no longer exists in Sentry 11.
102
+
103
+ ### Fixed
104
+
105
+ - **Deferred workflow starts retain their original caller receipt** — `@voltro/workflow`, `@voltro/cli`
106
+
107
+ A controlled workflow start now returns its existing queued receipt when another replica exhausts submission retries, or shared capacity moves, before its acceptance callback dispatches. It no longer reports an ordinary start failure while the committed submission remains unresolved. Execution identity, caller input, capacity ownership and retry limits stay unchanged; definite rejection and invalid ownership still fail explicitly.
108
+
109
+ - **Aggregate counters are non-negative safe integers on every dialect** — `@voltro/database`
110
+
111
+ A `count()` / `countDistinct()` / ranking counter now decodes to a number only when it is a non-negative safe integer; a fractional, negative, non-numeric or larger value is refused instead of passed through or rounded. SQLite and Turso decode counters too when the queried table has decimal columns, where they used to stay strings.
112
+ - **Cache clear honors connection namespace prefixes** — `@voltro/kv`, `@voltro/cache`
113
+
114
+ Clearing a cache through a named, namespaced Redis connection now binds logical cache keys to that connection's physical namespace. Redis-family engines and the local transport preserve neighboring caches and invalidation fences, while refusing foreign prefixes and forged key sets. The existing atomic cache command format remains unchanged.
115
+ - **Cache commands use the selected app's configuration and connections** — `@voltro/cli`
116
+
117
+ `voltro cache status`, `flush` and `invalidate` resolve `app.config.ts`, environment overrides and named Redis connections exactly like Dev and Serve, including an optional target app directory. Invalid configuration fails instead of silently reporting memory, in-process transports refuse CLI mutation, and diagnostics omit endpoint URLs and credentials.
118
+ - **Generated cache examples boot and upgrade reviews name affected lines** — `@voltro/cli`
119
+
120
+ The seeded core API example now uses an object cache declaration. Forced guide refresh discovers both flat and project-grouped app layouts, replacing stale nested examples without executing configs or crossing an app boundary. The shared cache/KV migration review lists authored code locations, including asserted backend literals, and a new review reaches applications that already crossed the original migration. It also identifies stale core guides for refresh; protected hand-maintained guides stay under their owner's control.
121
+ - **Subject query caches follow current authority** — `@voltro/runtime`, `@voltro/testing`
122
+
123
+ Subject-scoped computed queries key the complete subject claims and raw and resolved permission sets. Removing an admin grant, changing roles or switching tenant or credential type cannot reuse a result admitted under earlier authority. Authentication refreshes before lookup, and a change while a read is pending refuses retention and delivery. Connection-local state is never covered by subject scope; handlers that read it do not retain their results. The same decisions apply to `invoke` tests, memory caches and Redis caches.
124
+ - **Preserve connection declaration errors across module boundaries** — `@voltro/kv`
125
+
126
+ Redis, NATS, Storage, Analytics and SQL registries retain typed configuration diagnostics across module and VM boundaries instead of mislabeling them as dynamic credential failures. Errors returned by credential resolvers remain redacted.
127
+ - **Bind demo API tenants consistently in browser and server renders** — `@voltro/cli`
128
+
129
+ The fullstack, admin, SSR API and public status templates now send their explicit demo tenant to header-based anonymous APIs. SSR API and status pages use the same binding for server-side RPC reads, so a fresh scaffold renders successfully and its browser subscriptions select the same data. API refusals for missing tenants and access checks remain enforced. These demo bindings select rows and do not authenticate users; private production data requires verified authentication. Fresh-consumer diagnostics retain uppercase error log lines.
130
+ - **Two voltro dev processes starting together mint one set of secrets, not two** — `@voltro/cli`
131
+
132
+ `voltro dev` mints missing project secrets into `.env.local`. Two processes on one project starting at the same time (two local replicas, a dev server beside a test boot) each minted their own values; with field encryption the database recorded one key and refused the second process at boot. Minting now runs under a lock and adopts a value another process wrote meanwhile; a lock left by a crashed mint is taken over.
133
+ - **Event warnings follow workspace package exports** — `@voltro/cli`
134
+
135
+ Development event wiring warnings now recognise sibling `useEvent` consumers imported through package exports, TypeScript path aliases, named and namespace re-exports, and static local aliases. Each subscription is matched to its descriptor so an unused import or another API's same-named module does not hide a missing consumer. Workspace discovery supports declared pnpm, npm, Yarn and Bun members and excludes nested projects and build output.
136
+ - **Index audit preserves partial row coverage and uniqueness** — `@voltro/database`
137
+
138
+ The index audit recommends dropping an index only when another B-tree index preserves its row coverage and uniqueness. Partial unique indexes no longer make full indexes appear redundant; specialized index methods and unproved predicate relationships are excluded, and recommendations name only the safe replacement direction.
139
+ - **Migration logs identify which operations their count includes** — `@voltro/database`
140
+
141
+ Development auto-migration logs now identify their applied-operation count as the planner pass, excluding framework bootstrap and file-based migrations. A schema plan taken before boot can include work completed by those earlier stages; run a new plan after boot to verify that no operations remain.
142
+ - **Filter completed workflow pool owners before recovery transport** — `@voltro/cli`, `@voltro/voltro`, `@voltro/workflow`
143
+
144
+ Pool release recovery now persists its terminal settlement on submission and restart owners and filters those markers through indexed SQL predicates. Finished owner history no longer crosses the wire on every idle pass or after process restart. Lost release acknowledgements, held owners and missing evidence remain recoverable and reported; immutable owners and permit tombstones remain for receipt and replay safety. Normal framework schema migration adds two nullable settlement markers and their indexes; existing history is checked once in bounded pages. Settlement indexes use explicit short names within SQL identifier limits. Reconciliation cadence is unchanged.
145
+ - **Presence transport warnings follow actual subscription readiness** — `@voltro/plugin-presence`
146
+
147
+ Presence reports pending binding or subscription acquisition without a false missing-provider warning after five seconds. It reports cross-instance readiness only after acquiring the broadcast subscription, while local-only bindings and failed subscriptions still warn. Closing or replacing a binding prevents stale callbacks and releases subscriptions acquired afterward.
148
+ - **Self-updates finish after the old CLI installation is removed** — `@voltro/cli`, `@voltro/runtime`
149
+
150
+ `voltro update` loads its completion helpers before installing the target version, so removing the running CLI package no longer turns a successful upgrade into a missing-module failure. Error reporting uses the shared lightweight `@voltro/runtime/boot-refusal` entry loaded before dispatch; genuine failures keep their original message and exit code without loading the server dependency graph for help or version commands.
151
+ - **Compiled API servers start without a source-analysis dependency** — `@voltro/cli`
152
+
153
+ The development event-consumer audit loads its source compiler only when scanning. A compiled API server can start after relocation without app sources or a direct `ts-morph` dependency. Package-export consumer discovery keeps its existing scope and does not execute application modules.
154
+ - **SignalHeader centers its brand in the masthead** — `@voltro/ui-shadcn`
155
+
156
+ The `SignalHeader` brand slot is a centered flex row, so a brand link no longer sits on the text baseline and renders a few pixels above the masthead's center.
157
+ - **Update reports changed runtime patch assets before boot** — `@voltro/cli`
158
+
159
+ `voltro update` compares configured pnpm Effect and SQL-driver patches with the target CLI's assets during its codemod step, including `--codemods-only`. Changed bytes produce refresh and install instructions even without workflows. Same-version checks also report drift. Custom patch paths are named and files remain untouched.
160
+ - **Upgrade reviews omit locator counts and unchanged REST type plumbing** — `@voltro/cli`
161
+
162
+ The aggregate review excludes locator chains and local locator aliases while retaining uncertain query receivers. The idempotency review lists REST context constructions, context factories and guard definitions instead of every context or guard parameter annotation. Aliased imported calls in JavaScript custom hosts remain visible.
163
+
164
+ ### Internal (no consumer-facing effect)
165
+
166
+ - **Effect audits distinguish regression data from executable legacy APIs**
167
+
168
+ Effect migration audits allow test data to describe a foreign dependency's retained major. Removed package imports and obsolete bound API calls remain findings in tests and application code, while production migration-residue checks remain unchanged.
169
+ - **The doctor's table nullability manifest covers the billing history tables** — `@voltro/cli`
170
+
171
+ The generated nullability manifest `voltro doctor` reads was missing the invoice-history and customer-account tables the billing plugin added; it is regenerated from the declarations.
172
+ - **Installation checks refuse ambient workspaces and source overrides**
173
+
174
+ Installation checks require standalone directories before creating projects. Artifact consumers use shipped template and documentation assets without inheriting maintainer source overrides or Node module loaders. Registry, package-manager and explicit application settings remain available.
175
+ - **Installation checks require healthy applications and usable modules**
176
+
177
+ Installation checks require API readiness, successful web responses and transformed JavaScript modules while the development process remains running. HTTP errors and HTML fallbacks cannot satisfy those checks. Diagnostics distinguish application startup from shutdown.
178
+ - **Keep CLI fixture temporary roots and child outcomes explicit**
179
+
180
+ Automatic sidecar tests inspect the actual operating-system temporary directory and release their bound owner even when an assertion fails. Schema-boot fixtures retain the child's exit signal and assert the real exit tuple alongside readiness and migration counts, so a signal cannot become a false successful process result. Production security and signal guards remain unchanged.
181
+
182
+ Workflow recovery tests distinguish the recorded failure budget from concurrent dispatches already in flight. They retain the same prepared execution identity, require one body execution, and verify that stopped or accepted submissions cannot dispatch again.
183
+ - **Native SQL checks isolate schema ownership across fixtures**
184
+
185
+ Wallet and shop checks own separate server databases so concurrent schema creation cannot contend with another fixture's live writes. Independent pools within a fixture still share the real database. Cleanup closes all acquired pools before dropping only the owned namespace, and a native regression verifies isolation with identical wallet identities.
186
+ - **Native reload checks retain manifests published during SQL observation**
187
+
188
+ Native geometry checks establish the expected-version receiver before reload activation. A real transport regression holds the consumer until the new manifest arrives, so asynchronous SQL observation cannot hide a missed publication. Frame deadlines retain their original call sites.
189
+ - **Native snapshot probes join their scheduled driver**
190
+
191
+ Held-source stream probes quiesce and join the actual Host driver before directly pumping its captured graph. This prevents a scheduled turn from concurrently entering that graph and closing the fixture's native Session. Listener, SQL, controller, wire delivery, rights withdrawal and final cleanup assertions remain active; ordinary stream cases retain the running driver.
192
+ - **Bound the reviewed Sentry tool exception and retain every dependency instance**
193
+
194
+ The owner-reviewed exception accepts only sentry 0.45.0 under FSL-1.1-Apache-2.0 as unmodified external tooling for the Sentry integration. This does not classify FSL as permissive or remove its competing-use restriction. The runtime license walk checks every resolved instance, so an accepted version cannot hide a second version or license. Generated notices and the SBOM use actual package identities. Containment checks cover framework, workspace and scaffold patch files plus declared patches with arbitrary filenames; the API bundler leaves the tool external.
195
+ - **Stack scaffold checks require major-scoped runtime alignment**
196
+
197
+ The normal stack scaffold regression parses its generated workspace policy and verifies both Effect 4 selectors while refusing unqualified Effect and companion pins. Patch declaration and actual patch-byte checks remain, so the regression follows the preserved foreign-major contract instead of demanding its earlier unsafe global override. Its synthetic workspace declares its own pnpm version, making Compose baseline coverage independent of the test runner's package-manager environment.
198
+ - **Dependency security checks verify installed source remediations**
199
+
200
+ Dependency security checks accept a reviewed source remediation only after verifying exact patch and implementation hashes, patched references in every lockfile document, actual caller resolution and runtime behavior. Deepmerge's returned-object prototype protection preserves ordinary configuration merging. Unaffected dependency graphs receive no exception, and a local source remediation is never reported as an upstream fixed version.
201
+
202
+ ---
203
+
44
204
  ## [0.87.0] — 2026-10-31
45
205
 
46
206
  ### ⚠ BREAKING
@@ -3231,6 +3391,15 @@ _Changes staged for the next release accumulate here (rolled up from
3231
3391
  - **Prepare the exact XYFlow type correction before normal installation** — `@voltro/cli`
3232
3392
 
3233
3393
  `voltro add patches --xyflow 12.12.0` prepares the original XYFlow declaration correction and its complete license/notice before a normal package-manager or UI installation. Existing conflicting project patch assets are preserved and rejected before writes.
3394
+ - **Dispatchers drain accepted reads before store disposal** — `@voltro/runtime`, `@voltro/cli`
3395
+
3396
+ Runtime adds `Dispatcher.closeAndDrain()` to join accepted reads and deliveries before store disposal. Normal Dev and Serve API shutdown await it; synchronous `close()` remains available.
3397
+ - **Workflow cluster hosts declare shard groups and ClusterCron routing groups** — `@voltro/workflow`, `@voltro/cli`
3398
+
3399
+ Workflow cluster hosts can explicitly declare available/assigned shard groups and ClusterCron routing groups. Omitted settings retain existing routing; persistent journal migration is a separate prerequisite for changing groups.
3400
+ - **PostgreSQL workflow hosts can persist routing-generation admission** — `@voltro/workflow`, `@voltro/cli`
3401
+
3402
+ PostgreSQL workflow engine hosts can opt into persisted routing-generation admission with `journalRouting`; actual durable MessageStorage operations use the ownership guard. Full API-role wiring and maintenance rollout remain separate requirements.
3234
3403
 
3235
3404
  ### Changed
3236
3405
 
@@ -24321,9 +24490,3 @@ public registry yet.
24321
24490
 
24322
24491
  Subsequent releases record their deltas from here under dated headings, with
24323
24492
  `⚠ BREAKING` first.
24324
-
24325
- - Runtime adds `Dispatcher.closeAndDrain()` to join accepted reads and deliveries before store disposal. Normal Dev and Serve API shutdown await it; synchronous `close()` remains available.
24326
-
24327
- - Workflow cluster hosts can explicitly declare available/assigned shard groups and ClusterCron routing groups. Omitted settings retain existing routing; persistent journal migration is a separate prerequisite for changing groups.
24328
-
24329
- - PostgreSQL workflow engine hosts can opt into persisted routing-generation admission with `journalRouting`; actual durable MessageStorage operations use the ownership guard. Full API-role wiring and maintenance rollout remain separate requirements.
package/THIRD-PARTY-NOTICES.md CHANGED
@@ -1,15 +1,15 @@
1
1
  # Third-Party Notices — @voltro/plugin-duckdb
2
2
 
3
- This package uses the open-source software listed below. Each is the
3
+ This package uses the third-party software listed below. Each is the
4
4
  property of its respective copyright holders and is used under the terms of
5
5
  its license. This file is provided for attribution; it grants no rights in
6
6
  @voltro/plugin-duckdb itself, which is proprietary (see LICENSE).
7
7
 
8
- Generated from the resolved runtime dependency closure (48 packages).
8
+ Generated from the resolved runtime dependency closure (50 packages).
9
9
 
10
10
  ---
11
11
 
12
- ## @duckdb/node-api@1.5.5-r.5
12
+ ## @duckdb/node-api@2.0.0-r.1
13
13
 
14
14
  License: MIT
15
15
 
@@ -23,7 +23,7 @@ The above copyright notice and this permission notice shall be included in all c
23
23
  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
24
24
  ```
25
25
 
26
- ## @duckdb/node-bindings@1.5.5-r.5
26
+ ## @duckdb/node-bindings@2.0.0-r.1
27
27
 
28
28
  License: MIT
29
29
 
@@ -37,7 +37,7 @@ The above copyright notice and this permission notice shall be included in all c
37
37
  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
38
38
  ```
39
39
 
40
- ## @duckdb/node-bindings-linux-x64@1.5.5-r.5
40
+ ## @duckdb/node-bindings-linux-x64@2.0.0-r.1
41
41
 
42
42
  License: MIT
43
43
 
@@ -51,7 +51,7 @@ The above copyright notice and this permission notice shall be included in all c
51
51
  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
52
52
  ```
53
53
 
54
- ## @effect/platform-node@4.0.1
54
+ ## @effect/platform-node@4.1.0
55
55
 
56
56
  License: MIT
57
57
 
@@ -79,7 +79,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
79
79
  SOFTWARE.
80
80
  ```
81
81
 
82
- ## @effect/platform-node-shared@4.0.1
82
+ ## @effect/platform-node-shared@4.1.0
83
83
 
84
84
  License: MIT
85
85
 
@@ -107,7 +107,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
107
107
  SOFTWARE.
108
108
  ```
109
109
 
110
- ## @ioredis/commands@1.10.0
110
+ ## @ioredis/commands@2.0.0
111
111
 
112
112
  License: MIT
113
113
 
@@ -1384,7 +1384,7 @@ Apache License
1384
1384
  limitations under the License.
1385
1385
  ```
1386
1386
 
1387
- ## @opentelemetry/context-async-hooks@2.11.0
1387
+ ## @opentelemetry/context-async-hooks@2.12.0
1388
1388
 
1389
1389
  License: Apache-2.0
1390
1390
 
@@ -1592,7 +1592,7 @@ Apache License
1592
1592
  limitations under the License.
1593
1593
  ```
1594
1594
 
1595
- ## @opentelemetry/core@2.10.0
1595
+ ## @opentelemetry/core@2.12.0
1596
1596
 
1597
1597
  License: Apache-2.0
1598
1598
 
@@ -2840,6 +2840,214 @@ Apache License
2840
2840
  limitations under the License.
2841
2841
  ```
2842
2842
 
2843
+ ## @opentelemetry/resources@2.12.0
2844
+
2845
+ License: Apache-2.0
2846
+
2847
+ ```
2848
+ Apache License
2849
+ Version 2.0, January 2004
2850
+ http://www.apache.org/licenses/
2851
+
2852
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
2853
+
2854
+ 1. Definitions.
2855
+
2856
+ "License" shall mean the terms and conditions for use, reproduction,
2857
+ and distribution as defined by Sections 1 through 9 of this document.
2858
+
2859
+ "Licensor" shall mean the copyright owner or entity authorized by
2860
+ the copyright owner that is granting the License.
2861
+
2862
+ "Legal Entity" shall mean the union of the acting entity and all
2863
+ other entities that control, are controlled by, or are under common
2864
+ control with that entity. For the purposes of this definition,
2865
+ "control" means (i) the power, direct or indirect, to cause the
2866
+ direction or management of such entity, whether by contract or
2867
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
2868
+ outstanding shares, or (iii) beneficial ownership of such entity.
2869
+
2870
+ "You" (or "Your") shall mean an individual or Legal Entity
2871
+ exercising permissions granted by this License.
2872
+
2873
+ "Source" form shall mean the preferred form for making modifications,
2874
+ including but not limited to software source code, documentation
2875
+ source, and configuration files.
2876
+
2877
+ "Object" form shall mean any form resulting from mechanical
2878
+ transformation or translation of a Source form, including but
2879
+ not limited to compiled object code, generated documentation,
2880
+ and conversions to other media types.
2881
+
2882
+ "Work" shall mean the work of authorship, whether in Source or
2883
+ Object form, made available under the License, as indicated by a
2884
+ copyright notice that is included in or attached to the work
2885
+ (an example is provided in the Appendix below).
2886
+
2887
+ "Derivative Works" shall mean any work, whether in Source or Object
2888
+ form, that is based on (or derived from) the Work and for which the
2889
+ editorial revisions, annotations, elaborations, or other modifications
2890
+ represent, as a whole, an original work of authorship. For the purposes
2891
+ of this License, Derivative Works shall not include works that remain
2892
+ separable from, or merely link (or bind by name) to the interfaces of,
2893
+ the Work and Derivative Works thereof.
2894
+
2895
+ "Contribution" shall mean any work of authorship, including
2896
+ the original version of the Work and any modifications or additions
2897
+ to that Work or Derivative Works thereof, that is intentionally
2898
+ submitted to Licensor for inclusion in the Work by the copyright owner
2899
+ or by an individual or Legal Entity authorized to submit on behalf of
2900
+ the copyright owner. For the purposes of this definition, "submitted"
2901
+ means any form of electronic, verbal, or written communication sent
2902
+ to the Licensor or its representatives, including but not limited to
2903
+ communication on electronic mailing lists, source code control systems,
2904
+ and issue tracking systems that are managed by, or on behalf of, the
2905
+ Licensor for the purpose of discussing and improving the Work, but
2906
+ excluding communication that is conspicuously marked or otherwise
2907
+ designated in writing by the copyright owner as "Not a Contribution."
2908
+
2909
+ "Contributor" shall mean Licensor and any individual or Legal Entity
2910
+ on behalf of whom a Contribution has been received by Licensor and
2911
+ subsequently incorporated within the Work.
2912
+
2913
+ 2. Grant of Copyright License. Subject to the terms and conditions of
2914
+ this License, each Contributor hereby grants to You a perpetual,
2915
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
2916
+ copyright license to reproduce, prepare Derivative Works of,
2917
+ publicly display, publicly perform, sublicense, and distribute the
2918
+ Work and such Derivative Works in Source or Object form.
2919
+
2920
+ 3. Grant of Patent License. Subject to the terms and conditions of
2921
+ this License, each Contributor hereby grants to You a perpetual,
2922
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
2923
+ (except as stated in this section) patent license to make, have made,
2924
+ use, offer to sell, sell, import, and otherwise transfer the Work,
2925
+ where such license applies only to those patent claims licensable
2926
+ by such Contributor that are necessarily infringed by their
2927
+ Contribution(s) alone or by combination of their Contribution(s)
2928
+ with the Work to which such Contribution(s) was submitted. If You
2929
+ institute patent litigation against any entity (including a
2930
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
2931
+ or a Contribution incorporated within the Work constitutes direct
2932
+ or contributory patent infringement, then any patent licenses
2933
+ granted to You under this License for that Work shall terminate
2934
+ as of the date such litigation is filed.
2935
+
2936
+ 4. Redistribution. You may reproduce and distribute copies of the
2937
+ Work or Derivative Works thereof in any medium, with or without
2938
+ modifications, and in Source or Object form, provided that You
2939
+ meet the following conditions:
2940
+
2941
+ (a) You must give any other recipients of the Work or
2942
+ Derivative Works a copy of this License; and
2943
+
2944
+ (b) You must cause any modified files to carry prominent notices
2945
+ stating that You changed the files; and
2946
+
2947
+ (c) You must retain, in the Source form of any Derivative Works
2948
+ that You distribute, all copyright, patent, trademark, and
2949
+ attribution notices from the Source form of the Work,
2950
+ excluding those notices that do not pertain to any part of
2951
+ the Derivative Works; and
2952
+
2953
+ (d) If the Work includes a "NOTICE" text file as part of its
2954
+ distribution, then any Derivative Works that You distribute must
2955
+ include a readable copy of the attribution notices contained
2956
+ within such NOTICE file, excluding those notices that do not
2957
+ pertain to any part of the Derivative Works, in at least one
2958
+ of the following places: within a NOTICE text file distributed
2959
+ as part of the Derivative Works; within the Source form or
2960
+ documentation, if provided along with the Derivative Works; or,
2961
+ within a display generated by the Derivative Works, if and
2962
+ wherever such third-party notices normally appear. The contents
2963
+ of the NOTICE file are for informational purposes only and
2964
+ do not modify the License. You may add Your own attribution
2965
+ notices within Derivative Works that You distribute, alongside
2966
+ or as an addendum to the NOTICE text from the Work, provided
2967
+ that such additional attribution notices cannot be construed
2968
+ as modifying the License.
2969
+
2970
+ You may add Your own copyright statement to Your modifications and
2971
+ may provide additional or different license terms and conditions
2972
+ for use, reproduction, or distribution of Your modifications, or
2973
+ for any such Derivative Works as a whole, provided Your use,
2974
+ reproduction, and distribution of the Work otherwise complies with
2975
+ the conditions stated in this License.
2976
+
2977
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
2978
+ any Contribution intentionally submitted for inclusion in the Work
2979
+ by You to the Licensor shall be under the terms and conditions of
2980
+ this License, without any additional terms or conditions.
2981
+ Notwithstanding the above, nothing herein shall supersede or modify
2982
+ the terms of any separate license agreement you may have executed
2983
+ with Licensor regarding such Contributions.
2984
+
2985
+ 6. Trademarks. This License does not grant permission to use the trade
2986
+ names, trademarks, service marks, or product names of the Licensor,
2987
+ except as required for reasonable and customary use in describing the
2988
+ origin of the Work and reproducing the content of the NOTICE file.
2989
+
2990
+ 7. Disclaimer of Warranty. Unless required by applicable law or
2991
+ agreed to in writing, Licensor provides the Work (and each
2992
+ Contributor provides its Contributions) on an "AS IS" BASIS,
2993
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
2994
+ implied, including, without limitation, any warranties or conditions
2995
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
2996
+ PARTICULAR PURPOSE. You are solely responsible for determining the
2997
+ appropriateness of using or redistributing the Work and assume any
2998
+ risks associated with Your exercise of permissions under this License.
2999
+
3000
+ 8. Limitation of Liability. In no event and under no legal theory,
3001
+ whether in tort (including negligence), contract, or otherwise,
3002
+ unless required by applicable law (such as deliberate and grossly
3003
+ negligent acts) or agreed to in writing, shall any Contributor be
3004
+ liable to You for damages, including any direct, indirect, special,
3005
+ incidental, or consequential damages of any character arising as a
3006
+ result of this License or out of the use or inability to use the
3007
+ Work (including but not limited to damages for loss of goodwill,
3008
+ work stoppage, computer failure or malfunction, or any and all
3009
+ other commercial damages or losses), even if such Contributor
3010
+ has been advised of the possibility of such damages.
3011
+
3012
+ 9. Accepting Warranty or Additional Liability. While redistributing
3013
+ the Work or Derivative Works thereof, You may choose to offer,
3014
+ and charge a fee for, acceptance of support, warranty, indemnity,
3015
+ or other liability obligations and/or rights consistent with this
3016
+ License. However, in accepting such obligations, You may act only
3017
+ on Your own behalf and on Your sole responsibility, not on behalf
3018
+ of any other Contributor, and only if You agree to indemnify,
3019
+ defend, and hold each Contributor harmless for any liability
3020
+ incurred by, or claims asserted against, such Contributor by reason
3021
+ of your accepting any such warranty or additional liability.
3022
+
3023
+ END OF TERMS AND CONDITIONS
3024
+
3025
+ APPENDIX: How to apply the Apache License to your work.
3026
+
3027
+ To apply the Apache License to your work, attach the following
3028
+ boilerplate notice, with the fields enclosed by brackets "[]"
3029
+ replaced with your own identifying information. (Don't include
3030
+ the brackets!) The text should be enclosed in the appropriate
3031
+ comment syntax for the file format. We also recommend that a
3032
+ file or class name and description of purpose be included on the
3033
+ same "printed page" as the copyright notice for easier
3034
+ identification within third-party archives.
3035
+
3036
+ Copyright [yyyy] [name of copyright owner]
3037
+
3038
+ Licensed under the Apache License, Version 2.0 (the "License");
3039
+ you may not use this file except in compliance with the License.
3040
+ You may obtain a copy of the License at
3041
+
3042
+ http://www.apache.org/licenses/LICENSE-2.0
3043
+
3044
+ Unless required by applicable law or agreed to in writing, software
3045
+ distributed under the License is distributed on an "AS IS" BASIS,
3046
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
3047
+ See the License for the specific language governing permissions and
3048
+ limitations under the License.
3049
+ ```
3050
+
2843
3051
  ## @opentelemetry/sdk-logs@0.222.0
2844
3052
 
2845
3053
  License: Apache-2.0
@@ -3048,7 +3256,215 @@ Apache License
3048
3256
  limitations under the License.
3049
3257
  ```
3050
3258
 
3051
- ## @opentelemetry/sdk-metrics@2.11.0
3259
+ ## @opentelemetry/sdk-metrics@2.11.0
3260
+
3261
+ License: Apache-2.0
3262
+
3263
+ ```
3264
+ Apache License
3265
+ Version 2.0, January 2004
3266
+ http://www.apache.org/licenses/
3267
+
3268
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
3269
+
3270
+ 1. Definitions.
3271
+
3272
+ "License" shall mean the terms and conditions for use, reproduction,
3273
+ and distribution as defined by Sections 1 through 9 of this document.
3274
+
3275
+ "Licensor" shall mean the copyright owner or entity authorized by
3276
+ the copyright owner that is granting the License.
3277
+
3278
+ "Legal Entity" shall mean the union of the acting entity and all
3279
+ other entities that control, are controlled by, or are under common
3280
+ control with that entity. For the purposes of this definition,
3281
+ "control" means (i) the power, direct or indirect, to cause the
3282
+ direction or management of such entity, whether by contract or
3283
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
3284
+ outstanding shares, or (iii) beneficial ownership of such entity.
3285
+
3286
+ "You" (or "Your") shall mean an individual or Legal Entity
3287
+ exercising permissions granted by this License.
3288
+
3289
+ "Source" form shall mean the preferred form for making modifications,
3290
+ including but not limited to software source code, documentation
3291
+ source, and configuration files.
3292
+
3293
+ "Object" form shall mean any form resulting from mechanical
3294
+ transformation or translation of a Source form, including but
3295
+ not limited to compiled object code, generated documentation,
3296
+ and conversions to other media types.
3297
+
3298
+ "Work" shall mean the work of authorship, whether in Source or
3299
+ Object form, made available under the License, as indicated by a
3300
+ copyright notice that is included in or attached to the work
3301
+ (an example is provided in the Appendix below).
3302
+
3303
+ "Derivative Works" shall mean any work, whether in Source or Object
3304
+ form, that is based on (or derived from) the Work and for which the
3305
+ editorial revisions, annotations, elaborations, or other modifications
3306
+ represent, as a whole, an original work of authorship. For the purposes
3307
+ of this License, Derivative Works shall not include works that remain
3308
+ separable from, or merely link (or bind by name) to the interfaces of,
3309
+ the Work and Derivative Works thereof.
3310
+
3311
+ "Contribution" shall mean any work of authorship, including
3312
+ the original version of the Work and any modifications or additions
3313
+ to that Work or Derivative Works thereof, that is intentionally
3314
+ submitted to Licensor for inclusion in the Work by the copyright owner
3315
+ or by an individual or Legal Entity authorized to submit on behalf of
3316
+ the copyright owner. For the purposes of this definition, "submitted"
3317
+ means any form of electronic, verbal, or written communication sent
3318
+ to the Licensor or its representatives, including but not limited to
3319
+ communication on electronic mailing lists, source code control systems,
3320
+ and issue tracking systems that are managed by, or on behalf of, the
3321
+ Licensor for the purpose of discussing and improving the Work, but
3322
+ excluding communication that is conspicuously marked or otherwise
3323
+ designated in writing by the copyright owner as "Not a Contribution."
3324
+
3325
+ "Contributor" shall mean Licensor and any individual or Legal Entity
3326
+ on behalf of whom a Contribution has been received by Licensor and
3327
+ subsequently incorporated within the Work.
3328
+
3329
+ 2. Grant of Copyright License. Subject to the terms and conditions of
3330
+ this License, each Contributor hereby grants to You a perpetual,
3331
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3332
+ copyright license to reproduce, prepare Derivative Works of,
3333
+ publicly display, publicly perform, sublicense, and distribute the
3334
+ Work and such Derivative Works in Source or Object form.
3335
+
3336
+ 3. Grant of Patent License. Subject to the terms and conditions of
3337
+ this License, each Contributor hereby grants to You a perpetual,
3338
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3339
+ (except as stated in this section) patent license to make, have made,
3340
+ use, offer to sell, sell, import, and otherwise transfer the Work,
3341
+ where such license applies only to those patent claims licensable
3342
+ by such Contributor that are necessarily infringed by their
3343
+ Contribution(s) alone or by combination of their Contribution(s)
3344
+ with the Work to which such Contribution(s) was submitted. If You
3345
+ institute patent litigation against any entity (including a
3346
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
3347
+ or a Contribution incorporated within the Work constitutes direct
3348
+ or contributory patent infringement, then any patent licenses
3349
+ granted to You under this License for that Work shall terminate
3350
+ as of the date such litigation is filed.
3351
+
3352
+ 4. Redistribution. You may reproduce and distribute copies of the
3353
+ Work or Derivative Works thereof in any medium, with or without
3354
+ modifications, and in Source or Object form, provided that You
3355
+ meet the following conditions:
3356
+
3357
+ (a) You must give any other recipients of the Work or
3358
+ Derivative Works a copy of this License; and
3359
+
3360
+ (b) You must cause any modified files to carry prominent notices
3361
+ stating that You changed the files; and
3362
+
3363
+ (c) You must retain, in the Source form of any Derivative Works
3364
+ that You distribute, all copyright, patent, trademark, and
3365
+ attribution notices from the Source form of the Work,
3366
+ excluding those notices that do not pertain to any part of
3367
+ the Derivative Works; and
3368
+
3369
+ (d) If the Work includes a "NOTICE" text file as part of its
3370
+ distribution, then any Derivative Works that You distribute must
3371
+ include a readable copy of the attribution notices contained
3372
+ within such NOTICE file, excluding those notices that do not
3373
+ pertain to any part of the Derivative Works, in at least one
3374
+ of the following places: within a NOTICE text file distributed
3375
+ as part of the Derivative Works; within the Source form or
3376
+ documentation, if provided along with the Derivative Works; or,
3377
+ within a display generated by the Derivative Works, if and
3378
+ wherever such third-party notices normally appear. The contents
3379
+ of the NOTICE file are for informational purposes only and
3380
+ do not modify the License. You may add Your own attribution
3381
+ notices within Derivative Works that You distribute, alongside
3382
+ or as an addendum to the NOTICE text from the Work, provided
3383
+ that such additional attribution notices cannot be construed
3384
+ as modifying the License.
3385
+
3386
+ You may add Your own copyright statement to Your modifications and
3387
+ may provide additional or different license terms and conditions
3388
+ for use, reproduction, or distribution of Your modifications, or
3389
+ for any such Derivative Works as a whole, provided Your use,
3390
+ reproduction, and distribution of the Work otherwise complies with
3391
+ the conditions stated in this License.
3392
+
3393
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
3394
+ any Contribution intentionally submitted for inclusion in the Work
3395
+ by You to the Licensor shall be under the terms and conditions of
3396
+ this License, without any additional terms or conditions.
3397
+ Notwithstanding the above, nothing herein shall supersede or modify
3398
+ the terms of any separate license agreement you may have executed
3399
+ with Licensor regarding such Contributions.
3400
+
3401
+ 6. Trademarks. This License does not grant permission to use the trade
3402
+ names, trademarks, service marks, or product names of the Licensor,
3403
+ except as required for reasonable and customary use in describing the
3404
+ origin of the Work and reproducing the content of the NOTICE file.
3405
+
3406
+ 7. Disclaimer of Warranty. Unless required by applicable law or
3407
+ agreed to in writing, Licensor provides the Work (and each
3408
+ Contributor provides its Contributions) on an "AS IS" BASIS,
3409
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
3410
+ implied, including, without limitation, any warranties or conditions
3411
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
3412
+ PARTICULAR PURPOSE. You are solely responsible for determining the
3413
+ appropriateness of using or redistributing the Work and assume any
3414
+ risks associated with Your exercise of permissions under this License.
3415
+
3416
+ 8. Limitation of Liability. In no event and under no legal theory,
3417
+ whether in tort (including negligence), contract, or otherwise,
3418
+ unless required by applicable law (such as deliberate and grossly
3419
+ negligent acts) or agreed to in writing, shall any Contributor be
3420
+ liable to You for damages, including any direct, indirect, special,
3421
+ incidental, or consequential damages of any character arising as a
3422
+ result of this License or out of the use or inability to use the
3423
+ Work (including but not limited to damages for loss of goodwill,
3424
+ work stoppage, computer failure or malfunction, or any and all
3425
+ other commercial damages or losses), even if such Contributor
3426
+ has been advised of the possibility of such damages.
3427
+
3428
+ 9. Accepting Warranty or Additional Liability. While redistributing
3429
+ the Work or Derivative Works thereof, You may choose to offer,
3430
+ and charge a fee for, acceptance of support, warranty, indemnity,
3431
+ or other liability obligations and/or rights consistent with this
3432
+ License. However, in accepting such obligations, You may act only
3433
+ on Your own behalf and on Your sole responsibility, not on behalf
3434
+ of any other Contributor, and only if You agree to indemnify,
3435
+ defend, and hold each Contributor harmless for any liability
3436
+ incurred by, or claims asserted against, such Contributor by reason
3437
+ of your accepting any such warranty or additional liability.
3438
+
3439
+ END OF TERMS AND CONDITIONS
3440
+
3441
+ APPENDIX: How to apply the Apache License to your work.
3442
+
3443
+ To apply the Apache License to your work, attach the following
3444
+ boilerplate notice, with the fields enclosed by brackets "[]"
3445
+ replaced with your own identifying information. (Don't include
3446
+ the brackets!) The text should be enclosed in the appropriate
3447
+ comment syntax for the file format. We also recommend that a
3448
+ file or class name and description of purpose be included on the
3449
+ same "printed page" as the copyright notice for easier
3450
+ identification within third-party archives.
3451
+
3452
+ Copyright [yyyy] [name of copyright owner]
3453
+
3454
+ Licensed under the Apache License, Version 2.0 (the "License");
3455
+ you may not use this file except in compliance with the License.
3456
+ You may obtain a copy of the License at
3457
+
3458
+ http://www.apache.org/licenses/LICENSE-2.0
3459
+
3460
+ Unless required by applicable law or agreed to in writing, software
3461
+ distributed under the License is distributed on an "AS IS" BASIS,
3462
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
3463
+ See the License for the specific language governing permissions and
3464
+ limitations under the License.
3465
+ ```
3466
+
3467
+ ## @opentelemetry/sdk-metrics@2.12.0
3052
3468
 
3053
3469
  License: Apache-2.0
3054
3470
 
@@ -3464,7 +3880,215 @@ Apache License
3464
3880
  limitations under the License.
3465
3881
  ```
3466
3882
 
3467
- ## @opentelemetry/sdk-trace-base@2.11.0
3883
+ ## @opentelemetry/sdk-trace@2.12.0
3884
+
3885
+ License: Apache-2.0
3886
+
3887
+ ```
3888
+ Apache License
3889
+ Version 2.0, January 2004
3890
+ http://www.apache.org/licenses/
3891
+
3892
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
3893
+
3894
+ 1. Definitions.
3895
+
3896
+ "License" shall mean the terms and conditions for use, reproduction,
3897
+ and distribution as defined by Sections 1 through 9 of this document.
3898
+
3899
+ "Licensor" shall mean the copyright owner or entity authorized by
3900
+ the copyright owner that is granting the License.
3901
+
3902
+ "Legal Entity" shall mean the union of the acting entity and all
3903
+ other entities that control, are controlled by, or are under common
3904
+ control with that entity. For the purposes of this definition,
3905
+ "control" means (i) the power, direct or indirect, to cause the
3906
+ direction or management of such entity, whether by contract or
3907
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
3908
+ outstanding shares, or (iii) beneficial ownership of such entity.
3909
+
3910
+ "You" (or "Your") shall mean an individual or Legal Entity
3911
+ exercising permissions granted by this License.
3912
+
3913
+ "Source" form shall mean the preferred form for making modifications,
3914
+ including but not limited to software source code, documentation
3915
+ source, and configuration files.
3916
+
3917
+ "Object" form shall mean any form resulting from mechanical
3918
+ transformation or translation of a Source form, including but
3919
+ not limited to compiled object code, generated documentation,
3920
+ and conversions to other media types.
3921
+
3922
+ "Work" shall mean the work of authorship, whether in Source or
3923
+ Object form, made available under the License, as indicated by a
3924
+ copyright notice that is included in or attached to the work
3925
+ (an example is provided in the Appendix below).
3926
+
3927
+ "Derivative Works" shall mean any work, whether in Source or Object
3928
+ form, that is based on (or derived from) the Work and for which the
3929
+ editorial revisions, annotations, elaborations, or other modifications
3930
+ represent, as a whole, an original work of authorship. For the purposes
3931
+ of this License, Derivative Works shall not include works that remain
3932
+ separable from, or merely link (or bind by name) to the interfaces of,
3933
+ the Work and Derivative Works thereof.
3934
+
3935
+ "Contribution" shall mean any work of authorship, including
3936
+ the original version of the Work and any modifications or additions
3937
+ to that Work or Derivative Works thereof, that is intentionally
3938
+ submitted to Licensor for inclusion in the Work by the copyright owner
3939
+ or by an individual or Legal Entity authorized to submit on behalf of
3940
+ the copyright owner. For the purposes of this definition, "submitted"
3941
+ means any form of electronic, verbal, or written communication sent
3942
+ to the Licensor or its representatives, including but not limited to
3943
+ communication on electronic mailing lists, source code control systems,
3944
+ and issue tracking systems that are managed by, or on behalf of, the
3945
+ Licensor for the purpose of discussing and improving the Work, but
3946
+ excluding communication that is conspicuously marked or otherwise
3947
+ designated in writing by the copyright owner as "Not a Contribution."
3948
+
3949
+ "Contributor" shall mean Licensor and any individual or Legal Entity
3950
+ on behalf of whom a Contribution has been received by Licensor and
3951
+ subsequently incorporated within the Work.
3952
+
3953
+ 2. Grant of Copyright License. Subject to the terms and conditions of
3954
+ this License, each Contributor hereby grants to You a perpetual,
3955
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3956
+ copyright license to reproduce, prepare Derivative Works of,
3957
+ publicly display, publicly perform, sublicense, and distribute the
3958
+ Work and such Derivative Works in Source or Object form.
3959
+
3960
+ 3. Grant of Patent License. Subject to the terms and conditions of
3961
+ this License, each Contributor hereby grants to You a perpetual,
3962
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
3963
+ (except as stated in this section) patent license to make, have made,
3964
+ use, offer to sell, sell, import, and otherwise transfer the Work,
3965
+ where such license applies only to those patent claims licensable
3966
+ by such Contributor that are necessarily infringed by their
3967
+ Contribution(s) alone or by combination of their Contribution(s)
3968
+ with the Work to which such Contribution(s) was submitted. If You
3969
+ institute patent litigation against any entity (including a
3970
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
3971
+ or a Contribution incorporated within the Work constitutes direct
3972
+ or contributory patent infringement, then any patent licenses
3973
+ granted to You under this License for that Work shall terminate
3974
+ as of the date such litigation is filed.
3975
+
3976
+ 4. Redistribution. You may reproduce and distribute copies of the
3977
+ Work or Derivative Works thereof in any medium, with or without
3978
+ modifications, and in Source or Object form, provided that You
3979
+ meet the following conditions:
3980
+
3981
+ (a) You must give any other recipients of the Work or
3982
+ Derivative Works a copy of this License; and
3983
+
3984
+ (b) You must cause any modified files to carry prominent notices
3985
+ stating that You changed the files; and
3986
+
3987
+ (c) You must retain, in the Source form of any Derivative Works
3988
+ that You distribute, all copyright, patent, trademark, and
3989
+ attribution notices from the Source form of the Work,
3990
+ excluding those notices that do not pertain to any part of
3991
+ the Derivative Works; and
3992
+
3993
+ (d) If the Work includes a "NOTICE" text file as part of its
3994
+ distribution, then any Derivative Works that You distribute must
3995
+ include a readable copy of the attribution notices contained
3996
+ within such NOTICE file, excluding those notices that do not
3997
+ pertain to any part of the Derivative Works, in at least one
3998
+ of the following places: within a NOTICE text file distributed
3999
+ as part of the Derivative Works; within the Source form or
4000
+ documentation, if provided along with the Derivative Works; or,
4001
+ within a display generated by the Derivative Works, if and
4002
+ wherever such third-party notices normally appear. The contents
4003
+ of the NOTICE file are for informational purposes only and
4004
+ do not modify the License. You may add Your own attribution
4005
+ notices within Derivative Works that You distribute, alongside
4006
+ or as an addendum to the NOTICE text from the Work, provided
4007
+ that such additional attribution notices cannot be construed
4008
+ as modifying the License.
4009
+
4010
+ You may add Your own copyright statement to Your modifications and
4011
+ may provide additional or different license terms and conditions
4012
+ for use, reproduction, or distribution of Your modifications, or
4013
+ for any such Derivative Works as a whole, provided Your use,
4014
+ reproduction, and distribution of the Work otherwise complies with
4015
+ the conditions stated in this License.
4016
+
4017
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
4018
+ any Contribution intentionally submitted for inclusion in the Work
4019
+ by You to the Licensor shall be under the terms and conditions of
4020
+ this License, without any additional terms or conditions.
4021
+ Notwithstanding the above, nothing herein shall supersede or modify
4022
+ the terms of any separate license agreement you may have executed
4023
+ with Licensor regarding such Contributions.
4024
+
4025
+ 6. Trademarks. This License does not grant permission to use the trade
4026
+ names, trademarks, service marks, or product names of the Licensor,
4027
+ except as required for reasonable and customary use in describing the
4028
+ origin of the Work and reproducing the content of the NOTICE file.
4029
+
4030
+ 7. Disclaimer of Warranty. Unless required by applicable law or
4031
+ agreed to in writing, Licensor provides the Work (and each
4032
+ Contributor provides its Contributions) on an "AS IS" BASIS,
4033
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
4034
+ implied, including, without limitation, any warranties or conditions
4035
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
4036
+ PARTICULAR PURPOSE. You are solely responsible for determining the
4037
+ appropriateness of using or redistributing the Work and assume any
4038
+ risks associated with Your exercise of permissions under this License.
4039
+
4040
+ 8. Limitation of Liability. In no event and under no legal theory,
4041
+ whether in tort (including negligence), contract, or otherwise,
4042
+ unless required by applicable law (such as deliberate and grossly
4043
+ negligent acts) or agreed to in writing, shall any Contributor be
4044
+ liable to You for damages, including any direct, indirect, special,
4045
+ incidental, or consequential damages of any character arising as a
4046
+ result of this License or out of the use or inability to use the
4047
+ Work (including but not limited to damages for loss of goodwill,
4048
+ work stoppage, computer failure or malfunction, or any and all
4049
+ other commercial damages or losses), even if such Contributor
4050
+ has been advised of the possibility of such damages.
4051
+
4052
+ 9. Accepting Warranty or Additional Liability. While redistributing
4053
+ the Work or Derivative Works thereof, You may choose to offer,
4054
+ and charge a fee for, acceptance of support, warranty, indemnity,
4055
+ or other liability obligations and/or rights consistent with this
4056
+ License. However, in accepting such obligations, You may act only
4057
+ on Your own behalf and on Your sole responsibility, not on behalf
4058
+ of any other Contributor, and only if You agree to indemnify,
4059
+ defend, and hold each Contributor harmless for any liability
4060
+ incurred by, or claims asserted against, such Contributor by reason
4061
+ of your accepting any such warranty or additional liability.
4062
+
4063
+ END OF TERMS AND CONDITIONS
4064
+
4065
+ APPENDIX: How to apply the Apache License to your work.
4066
+
4067
+ To apply the Apache License to your work, attach the following
4068
+ boilerplate notice, with the fields enclosed by brackets "[]"
4069
+ replaced with your own identifying information. (Don't include
4070
+ the brackets!) The text should be enclosed in the appropriate
4071
+ comment syntax for the file format. We also recommend that a
4072
+ file or class name and description of purpose be included on the
4073
+ same "printed page" as the copyright notice for easier
4074
+ identification within third-party archives.
4075
+
4076
+ Copyright [yyyy] [name of copyright owner]
4077
+
4078
+ Licensed under the Apache License, Version 2.0 (the "License");
4079
+ you may not use this file except in compliance with the License.
4080
+ You may obtain a copy of the License at
4081
+
4082
+ http://www.apache.org/licenses/LICENSE-2.0
4083
+
4084
+ Unless required by applicable law or agreed to in writing, software
4085
+ distributed under the License is distributed on an "AS IS" BASIS,
4086
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
4087
+ See the License for the specific language governing permissions and
4088
+ limitations under the License.
4089
+ ```
4090
+
4091
+ ## @opentelemetry/sdk-trace-base@2.12.0
3468
4092
 
3469
4093
  License: Apache-2.0
3470
4094
 
@@ -3672,7 +4296,7 @@ Apache License
3672
4296
  limitations under the License.
3673
4297
  ```
3674
4298
 
3675
- ## @opentelemetry/sdk-trace-node@2.11.0
4299
+ ## @opentelemetry/sdk-trace-node@2.12.0
3676
4300
 
3677
4301
  License: Apache-2.0
3678
4302
 
@@ -3880,7 +4504,7 @@ Apache License
3880
4504
  limitations under the License.
3881
4505
  ```
3882
4506
 
3883
- ## @opentelemetry/semantic-conventions@1.43.0
4507
+ ## @opentelemetry/semantic-conventions@1.44.0
3884
4508
 
3885
4509
  License: Apache-2.0
3886
4510
 
@@ -4088,7 +4712,7 @@ Apache License
4088
4712
  limitations under the License.
4089
4713
  ```
4090
4714
 
4091
- ## @types/node@26.4.1
4715
+ ## @types/node@26.6.6
4092
4716
 
4093
4717
  License: MIT
4094
4718
 
@@ -4116,7 +4740,7 @@ MIT License
4116
4740
  SOFTWARE
4117
4741
  ```
4118
4742
 
4119
- ## @types/ws@8.18.1
4743
+ ## @types/ws@8.18.2
4120
4744
 
4121
4745
  License: MIT
4122
4746
 
@@ -4144,7 +4768,7 @@ MIT License
4144
4768
  SOFTWARE
4145
4769
  ```
4146
4770
 
4147
- ## @upstash/redis@1.38.4
4771
+ ## @upstash/redis@1.40.0
4148
4772
 
4149
4773
  License: MIT
4150
4774
 
@@ -4634,7 +5258,7 @@ Apache License
4634
5258
  limitations under the License.
4635
5259
  ```
4636
5260
 
4637
- ## ioredis@5.11.1
5261
+ ## ioredis@6.0.0
4638
5262
 
4639
5263
  License: MIT
4640
5264
 
@@ -4690,7 +5314,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4690
5314
  SOFTWARE.
4691
5315
  ```
4692
5316
 
4693
- ## jose@6.2.12
5317
+ ## jose@6.2.13
4694
5318
 
4695
5319
  License: MIT
4696
5320
 
@@ -4718,7 +5342,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4718
5342
  SOFTWARE.
4719
5343
  ```
4720
5344
 
4721
- ## lib0@0.2.117
5345
+ ## lib0@0.2.119
4722
5346
 
4723
5347
  License: MIT
4724
5348
 
@@ -4802,34 +5426,6 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4802
5426
  SOFTWARE.
4803
5427
  ```
4804
5428
 
4805
- ## redis-parser@3.0.0
4806
-
4807
- License: MIT
4808
-
4809
- ```
4810
- The MIT License (MIT)
4811
-
4812
- Copyright (c) 2015 NodeRedis
4813
-
4814
- Permission is hereby granted, free of charge, to any person obtaining a copy
4815
- of this software and associated documentation files (the "Software"), to deal
4816
- in the Software without restriction, including without limitation the rights
4817
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
4818
- copies of the Software, and to permit persons to whom the Software is
4819
- furnished to do so, subject to the following conditions:
4820
-
4821
- The above copyright notice and this permission notice shall be included in all
4822
- copies or substantial portions of the Software.
4823
-
4824
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
4825
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
4826
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
4827
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
4828
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
4829
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4830
- SOFTWARE.
4831
- ```
4832
-
4833
5429
  ## standard-as-callback@2.1.0
4834
5430
 
4835
5431
  License: MIT
@@ -4974,7 +5570,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
4974
5570
  SOFTWARE.
4975
5571
  ```
4976
5572
 
4977
- ## undici-types@8.3.0
5573
+ ## undici-types@8.9.0
4978
5574
 
4979
5575
  License: MIT
4980
5576
 
@@ -5002,7 +5598,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
5002
5598
  SOFTWARE.
5003
5599
  ```
5004
5600
 
5005
- ## ws@8.21.0
5601
+ ## ws@8.22.0
5006
5602
 
5007
5603
  License: MIT
5008
5604
 
@@ -5057,7 +5653,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
5057
5653
  SOFTWARE.
5058
5654
  ```
5059
5655
 
5060
- ## yjs@13.6.32
5656
+ ## yjs@13.6.33
5061
5657
 
5062
5658
  License: MIT
5063
5659
 
package/dist/index.js CHANGED
@@ -1,5 +1,5 @@
1
1
  import { buildDuckdbSink as e, closeDuckdbState as t, initializeDuckdbState as n } from "./sink.js";
2
- //#region src/index.ts
2
+ // src/index.ts
3
3
  var r = (r = {}) => {
4
4
  let i = {
5
5
  conn: null,
@@ -13,5 +13,4 @@ var r = (r = {}) => {
13
13
  dispose: () => t(i)
14
14
  };
15
15
  };
16
- //#endregion
17
16
  export { r as duckdbAnalytics };
package/dist/sink.js CHANGED
@@ -1,6 +1,6 @@
1
1
  import { Effect as e } from "effect";
2
2
  import { AnalyticsError as t } from "@voltro/runtime";
3
- //#region src/sink.ts
3
+ // src/sink.ts
4
4
  var n = "duckdb", r = "voltro_events", i = null, a = () => i === null ? e.tryPromise({
5
5
  try: async () => {
6
6
  let e = await import("@duckdb/node-api");
@@ -223,5 +223,4 @@ var n = "duckdb", r = "voltro_events", i = null, a = () => i === null ? e.tryPro
223
223
  err: t
224
224
  }))));
225
225
  });
226
- //#endregion
227
226
  export { w as buildDuckdbSink, E as closeDuckdbState, T as initializeDuckdbState, s as mirrorTableName };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@voltro/plugin-duckdb",
3
- "version": "0.87.0",
3
+ "version": "0.88.0",
4
4
  "description": "Embedded DuckDB AnalyticsSink. Runs DuckDB in-process for real OLAP performance without an external service. Events land in a DuckDB column-store table; aggregate / timeseries / topN queries execute vectorized.",
5
5
  "keywords": [
6
6
  "voltro",
@@ -33,13 +33,13 @@
33
33
  "node": ">=24.0.0"
34
34
  },
35
35
  "dependencies": {
36
- "@voltro/runtime": "0.87.0"
36
+ "@voltro/runtime": "0.88.0"
37
37
  },
38
38
  "optionalDependencies": {
39
- "@duckdb/node-api": "1.5.5-r.5"
39
+ "@duckdb/node-api": "2.0.0-r.1"
40
40
  },
41
41
  "peerDependencies": {
42
- "effect": "4.0.1"
42
+ "effect": "4.1.0"
43
43
  },
44
44
  "publishConfig": {
45
45
  "access": "public"