Skip to content
Lunora
Releases1407 releases

Changelog

Every release across the Lunora packages, newest first. Lunora is alpha: the API still moves, and this is where it is written down.

Oct 5, 2026

Dependency updates only, across 40 packages.

@lunora/studiochore

1.0.0-alpha.264

diff

Tests

  • studio: give the capability-gate tests the route-load timeout (#988) (dc3f719)

Dependencies

  • @lunora/client: upgraded to 1.0.0-alpha.179
  • @lunora/react: upgraded to 1.0.0-alpha.191
  • @lunora/mail: upgraded to 1.0.0-alpha.98
  • @lunora/notify: upgraded to 1.0.0-alpha.74
Oct 4, 2026

Dependency updates only, across 21 packages.

@lunora/clifeature

1.0.0-alpha.346

diff

Added

Dependencies

  • @lunora/codegen: upgraded to 1.0.0-alpha.261
  • @lunora/config: upgraded to 1.0.0-alpha.304
  • @lunora/mcp: upgraded to 1.0.0-alpha.211
  • @lunora/seed: upgraded to 1.0.0-alpha.189
  • @lunora/testing: upgraded to 1.0.0-alpha.232
@lunora/codegenfix

1.0.0-alpha.262

diff

Fixed

  • root-cause the rspack watch and cli registry-items CI timeouts (#985) (b1938a5)

Dependencies

  • @lunora/agent: upgraded to 1.0.0-alpha.176
@lunora/configfeature

1.0.0-alpha.304

diff

Added

Dependencies

  • @lunora/codegen: upgraded to 1.0.0-alpha.261
  • @lunora/seed: upgraded to 1.0.0-alpha.189
  • @lunora/studio: upgraded to 1.0.0-alpha.261
@lunora/rspackfix

1.0.0-alpha.26

diff

Fixed

  • root-cause the rspack watch and cli registry-items CI timeouts (#985) (b1938a5)

Dependencies

  • @lunora/codegen: upgraded to 1.0.0-alpha.262
  • @lunora/config: upgraded to 1.0.0-alpha.305
  • @lunora/studio: upgraded to 1.0.0-alpha.262
@lunora/rspackfeature

1.0.0-alpha.25

diff

Added

Dependencies

  • @lunora/codegen: upgraded to 1.0.0-alpha.261
  • @lunora/config: upgraded to 1.0.0-alpha.304
  • @lunora/studio: upgraded to 1.0.0-alpha.261
@lunora/vitefeature

1.0.0-alpha.302

diff

Added

Dependencies

  • @lunora/codegen: upgraded to 1.0.0-alpha.261
  • @lunora/config: upgraded to 1.0.0-alpha.304
  • @lunora/studio: upgraded to 1.0.0-alpha.261
Oct 3, 2026

Dependency updates only, across 50 packages.

@lunora/advisorfix

1.0.0-alpha.189

diff

Fixed

@lunora/advisorfix

1.0.0-alpha.188

diff

Fixed

  • codegen: owner-scope only the mutator's own args parameter (#958) (cf4003a), closes #957

Dependencies

  • @lunora/server: upgraded to 1.0.0-alpha.177
@lunora/advisorfix

1.0.0-alpha.187

diff

Fixed

  • codegen: attribute helper writes to their exported callers (#954) (91467c4)

Dependencies

  • @lunora/server: upgraded to 1.0.0-alpha.176
@lunora/advisorchore

1.0.0-alpha.183

diff

⚠ BREAKING CHANGES

  • @lunora/bindings/analytics no longer exports createAnalyticsSqlClient, AnalyticsSqlError or the AnalyticsSqlClient, AnalyticsSqlConfig, AnalyticsSqlResult and AnalyticsSqlColumnMeta types, and the ANALYTICS_SQL_ERROR code is gone. Query with ctx.analyticsSql or createAnalyticsSql({ binding: createAnalyticsSqlRest(...) }) in the Analytics SQL dialect; failures are AnalyticsSqlQueryError (ANALYTICS_SQL_QUERY_ERROR). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • refactor(advisor): read ae metrics in the analytics sql dialect only The quarantined Analytics Engine feeder speaks only the Analytics SQL dialect, the one ctx.analyticsSql runs: events.analyticsEngine."<dataset>", the SQL API's sample-weighted COUNT(*), and every value bound as a parameter - $since, $event, and $group when a group is given. The AnalyticsMetricsDialect union, dialectParts, the sqlString literal escaper and the hidden "were params passed" dialect switch are gone; the dataset, which names the table and so cannot be a parameter, keeps its identifier guard.
  • AnalyticsMetricsOptions requires since (an ISO-8601 lower timestamp bound) and has no dialect; AnalyticsMetricsSource.query always receives params; the AnalyticsMetricsDialect type is removed. Pass ctx.analyticsSql as the source. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • fix(studio): ask the host for usage panels by key, never with sql The Analytics tab has one runner, analyticsSqlQuery(panel), which receives a panel key ("volume", "latency", "hotShards") and resolves the rows. The host answers through an admin-gated action that builds the statement server-side with functionUsageQuery(panel) and runs it on ctx.analyticsSql. The old shape handed the host a SQL string to execute, which invited an action that runs caller-supplied SQL against the whole account. The prop docs and the not-wired message now say the action must be admin-only and take the key. The panel drops the second (token-dialect) runner, the precedence between the two, the dataset prop (now the server's choice) and toPanelResult: columns are string[], read off the first row's keys in SELECT order.
  • StudioProps.analyticsQuery is removed and analyticsSqlQuery now has the signature (panel: FunctionUsagePanel) => Promise<AnalyticsSqlQueryResult>. AnalyticsPanelProps loses dataset and runAnalyticsSql, and its runQuery takes a panel key. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • fix(config): report artifacts as unsupported in the alchemy translation The Alchemy translator emits only D1, R2, KV and Queue resources, but an artifacts[] binding was neither emitted nor listed in unsupported, so a config using ctx.artifacts produced a Worker without env.ARTIFACTS and no diagnostic. Raised by review on #941. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • docs(bindings): list the analytics-sql subpath in the readme table Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Added

  • cloudflare analytics sql binding as ctx.analyticsSql (#946) (9c931dd)

Dependencies

  • @lunora/errors: upgraded to 1.0.0-alpha.50
  • @lunora/server: upgraded to 1.0.0-alpha.172
  • @lunora/values: upgraded to 1.0.0-alpha.60
@lunora/authfeature

1.0.0-alpha.184

diff

Added

  • cloudflare changelog 2026-10-01/02 parity (#923) (23287d9)

Dependencies

  • @lunora/config: upgraded to 1.0.0-alpha.294
  • @lunora/runtime: upgraded to 1.0.0-alpha.172
  • @lunora/server: upgraded to 1.0.0-alpha.171
@lunora/bindingschore

1.0.0-alpha.93

diff

⚠ BREAKING CHANGES

  • @lunora/bindings/analytics no longer exports createAnalyticsSqlClient, AnalyticsSqlError or the AnalyticsSqlClient, AnalyticsSqlConfig, AnalyticsSqlResult and AnalyticsSqlColumnMeta types, and the ANALYTICS_SQL_ERROR code is gone. Query with ctx.analyticsSql or createAnalyticsSql({ binding: createAnalyticsSqlRest(...) }) in the Analytics SQL dialect; failures are AnalyticsSqlQueryError (ANALYTICS_SQL_QUERY_ERROR). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • refactor(advisor): read ae metrics in the analytics sql dialect only The quarantined Analytics Engine feeder speaks only the Analytics SQL dialect, the one ctx.analyticsSql runs: events.analyticsEngine."<dataset>", the SQL API's sample-weighted COUNT(*), and every value bound as a parameter - $since, $event, and $group when a group is given. The AnalyticsMetricsDialect union, dialectParts, the sqlString literal escaper and the hidden "were params passed" dialect switch are gone; the dataset, which names the table and so cannot be a parameter, keeps its identifier guard.
  • AnalyticsMetricsOptions requires since (an ISO-8601 lower timestamp bound) and has no dialect; AnalyticsMetricsSource.query always receives params; the AnalyticsMetricsDialect type is removed. Pass ctx.analyticsSql as the source. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • fix(studio): ask the host for usage panels by key, never with sql The Analytics tab has one runner, analyticsSqlQuery(panel), which receives a panel key ("volume", "latency", "hotShards") and resolves the rows. The host answers through an admin-gated action that builds the statement server-side with functionUsageQuery(panel) and runs it on ctx.analyticsSql. The old shape handed the host a SQL string to execute, which invited an action that runs caller-supplied SQL against the whole account. The prop docs and the not-wired message now say the action must be admin-only and take the key. The panel drops the second (token-dialect) runner, the precedence between the two, the dataset prop (now the server's choice) and toPanelResult: columns are string[], read off the first row's keys in SELECT order.
  • StudioProps.analyticsQuery is removed and analyticsSqlQuery now has the signature (panel: FunctionUsagePanel) => Promise<AnalyticsSqlQueryResult>. AnalyticsPanelProps loses dataset and runAnalyticsSql, and its runQuery takes a panel key. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • fix(config): report artifacts as unsupported in the alchemy translation The Alchemy translator emits only D1, R2, KV and Queue resources, but an artifacts[] binding was neither emitted nor listed in unsupported, so a config using ctx.artifacts produced a Worker without env.ARTIFACTS and no diagnostic. Raised by review on #941. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • docs(bindings): list the analytics-sql subpath in the readme table Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Added

  • cloudflare analytics sql binding as ctx.analyticsSql (#946) (9c931dd)

Dependencies

  • @lunora/errors: upgraded to 1.0.0-alpha.50
  • @lunora/platform: upgraded to 1.0.0-alpha.52
@lunora/clifix

1.0.0-alpha.342

diff

Fixed

  • codegen: attribute helper writes to their exported callers (#954) (91467c4)

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.187
  • @lunora/codegen: upgraded to 1.0.0-alpha.257
  • @lunora/config: upgraded to 1.0.0-alpha.300
  • @lunora/seed: upgraded to 1.0.0-alpha.185
  • @lunora/testing: upgraded to 1.0.0-alpha.228
@lunora/clichore

1.0.0-alpha.339

diff

⚠ BREAKING CHANGES

  • capability inference and the codegen probe surface changed.

Added

  • cli: add lunora dev --tunnel via cloudflare quick tunnels (#941) (1446ad1)

Fixed

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.185
  • @lunora/bindings: upgraded to 1.0.0-alpha.95
  • @lunora/codegen: upgraded to 1.0.0-alpha.254
  • @lunora/config: upgraded to 1.0.0-alpha.297
  • @lunora/container: upgraded to 1.0.0-alpha.69
  • @lunora/d1: upgraded to 1.0.0-alpha.161
  • @lunora/mcp: upgraded to 1.0.0-alpha.208
  • @lunora/runtime: upgraded to 1.0.0-alpha.175
  • @lunora/seed: upgraded to 1.0.0-alpha.182
  • @lunora/testing: upgraded to 1.0.0-alpha.225
@lunora/clichore

1.0.0-alpha.337

diff

⚠ BREAKING CHANGES

  • @lunora/bindings/analytics no longer exports createAnalyticsSqlClient, AnalyticsSqlError or the AnalyticsSqlClient, AnalyticsSqlConfig, AnalyticsSqlResult and AnalyticsSqlColumnMeta types, and the ANALYTICS_SQL_ERROR code is gone. Query with ctx.analyticsSql or createAnalyticsSql({ binding: createAnalyticsSqlRest(...) }) in the Analytics SQL dialect; failures are AnalyticsSqlQueryError (ANALYTICS_SQL_QUERY_ERROR). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • refactor(advisor): read ae metrics in the analytics sql dialect only The quarantined Analytics Engine feeder speaks only the Analytics SQL dialect, the one ctx.analyticsSql runs: events.analyticsEngine."<dataset>", the SQL API's sample-weighted COUNT(*), and every value bound as a parameter - $since, $event, and $group when a group is given. The AnalyticsMetricsDialect union, dialectParts, the sqlString literal escaper and the hidden "were params passed" dialect switch are gone; the dataset, which names the table and so cannot be a parameter, keeps its identifier guard.
  • AnalyticsMetricsOptions requires since (an ISO-8601 lower timestamp bound) and has no dialect; AnalyticsMetricsSource.query always receives params; the AnalyticsMetricsDialect type is removed. Pass ctx.analyticsSql as the source. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • fix(studio): ask the host for usage panels by key, never with sql The Analytics tab has one runner, analyticsSqlQuery(panel), which receives a panel key ("volume", "latency", "hotShards") and resolves the rows. The host answers through an admin-gated action that builds the statement server-side with functionUsageQuery(panel) and runs it on ctx.analyticsSql. The old shape handed the host a SQL string to execute, which invited an action that runs caller-supplied SQL against the whole account. The prop docs and the not-wired message now say the action must be admin-only and take the key. The panel drops the second (token-dialect) runner, the precedence between the two, the dataset prop (now the server's choice) and toPanelResult: columns are string[], read off the first row's keys in SELECT order.
  • StudioProps.analyticsQuery is removed and analyticsSqlQuery now has the signature (panel: FunctionUsagePanel) => Promise<AnalyticsSqlQueryResult>. AnalyticsPanelProps loses dataset and runAnalyticsSql, and its runQuery takes a panel key. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • fix(config): report artifacts as unsupported in the alchemy translation The Alchemy translator emits only D1, R2, KV and Queue resources, but an artifacts[] binding was neither emitted nor listed in unsupported, so a config using ctx.artifacts produced a Worker without env.ARTIFACTS and no diagnostic. Raised by review on #941. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • docs(bindings): list the analytics-sql subpath in the readme table Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Added

  • cloudflare analytics sql binding as ctx.analyticsSql (#946) (9c931dd)

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.183
  • @lunora/bindings: upgraded to 1.0.0-alpha.93
  • @lunora/codegen: upgraded to 1.0.0-alpha.252
  • @lunora/config: upgraded to 1.0.0-alpha.295
  • @lunora/container: upgraded to 1.0.0-alpha.68
  • @lunora/d1: upgraded to 1.0.0-alpha.160
  • @lunora/errors: upgraded to 1.0.0-alpha.50
  • @lunora/mcp: upgraded to 1.0.0-alpha.206
  • @lunora/runtime: upgraded to 1.0.0-alpha.173
  • @lunora/seed: upgraded to 1.0.0-alpha.180
  • @lunora/testing: upgraded to 1.0.0-alpha.223
@lunora/clifeature

1.0.0-alpha.336

diff

Added

  • cloudflare changelog 2026-10-01/02 parity (#923) (23287d9)

Fixed

  • cloudflare oct 2026 limits + observability block (#942) (6145c8c)

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.182
  • @lunora/bindings: upgraded to 1.0.0-alpha.92
  • @lunora/codegen: upgraded to 1.0.0-alpha.251
  • @lunora/config: upgraded to 1.0.0-alpha.294
  • @lunora/container: upgraded to 1.0.0-alpha.67
  • @lunora/d1: upgraded to 1.0.0-alpha.159
  • @lunora/mcp: upgraded to 1.0.0-alpha.205
  • @lunora/runtime: upgraded to 1.0.0-alpha.172
  • @lunora/seed: upgraded to 1.0.0-alpha.179
  • @lunora/testing: upgraded to 1.0.0-alpha.222
@lunora/codegenfix

1.0.0-alpha.260

diff

Fixed

Dependencies

  • @lunora/agent: upgraded to 1.0.0-alpha.174
@lunora/codegenfix

1.0.0-alpha.258

diff

Fixed

  • codegen: owner-scope only the mutator's own args parameter (#958) (cf4003a), closes #957

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.188
  • @lunora/agent: upgraded to 1.0.0-alpha.171
  • @lunora/server: upgraded to 1.0.0-alpha.177
@lunora/codegenfix

1.0.0-alpha.257

diff

Fixed

  • codegen: attribute helper writes to their exported callers (#954) (91467c4)

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.187
  • @lunora/agent: upgraded to 1.0.0-alpha.170
  • @lunora/server: upgraded to 1.0.0-alpha.176
@lunora/codegenfeature

1.0.0-alpha.256

diff

Added

  • observability: set error status on failed host spans (#953) (112ef1e), closes #939

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.186
  • @lunora/agent: upgraded to 1.0.0-alpha.169
  • @lunora/platform: upgraded to 1.0.0-alpha.55
  • @lunora/queue: upgraded to 1.0.0-alpha.91
  • @lunora/scheduler: upgraded to 1.0.0-alpha.109
  • @lunora/bindings: upgraded to 1.0.0-alpha.96
  • @lunora/do: upgraded to 1.0.0-alpha.193
  • @lunora/server: upgraded to 1.0.0-alpha.175
  • @lunora/shard-engine: upgraded to 1.0.0-alpha.111
@lunora/codegenchore

1.0.0-alpha.254

diff

⚠ BREAKING CHANGES

  • capability inference and the codegen probe surface changed.

Fixed

Tests

  • codegen: realign the analytics-sql golden with the storage stub (#952) (4b7895d), closes #947 #946

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.185
  • @lunora/agent: upgraded to 1.0.0-alpha.167
  • @lunora/container: upgraded to 1.0.0-alpha.69
  • @lunora/platform: upgraded to 1.0.0-alpha.54
  • @lunora/queue: upgraded to 1.0.0-alpha.90
  • @lunora/scheduler: upgraded to 1.0.0-alpha.108
  • @lunora/bindings: upgraded to 1.0.0-alpha.95
  • @lunora/do: upgraded to 1.0.0-alpha.192
  • @lunora/server: upgraded to 1.0.0-alpha.174
  • @lunora/shard-engine: upgraded to 1.0.0-alpha.110
@lunora/codegenfeature

1.0.0-alpha.253

diff

Added

Fixed

  • server: type multipart, list and upload on action ctx.storage (#947) (36341e5), closes #940

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.184
  • @lunora/agent: upgraded to 1.0.0-alpha.166
  • @lunora/do: upgraded to 1.0.0-alpha.191
  • @lunora/server: upgraded to 1.0.0-alpha.173
@lunora/codegenchore

1.0.0-alpha.252

diff

⚠ BREAKING CHANGES

  • @lunora/bindings/analytics no longer exports createAnalyticsSqlClient, AnalyticsSqlError or the AnalyticsSqlClient, AnalyticsSqlConfig, AnalyticsSqlResult and AnalyticsSqlColumnMeta types, and the ANALYTICS_SQL_ERROR code is gone. Query with ctx.analyticsSql or createAnalyticsSql({ binding: createAnalyticsSqlRest(...) }) in the Analytics SQL dialect; failures are AnalyticsSqlQueryError (ANALYTICS_SQL_QUERY_ERROR). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • refactor(advisor): read ae metrics in the analytics sql dialect only The quarantined Analytics Engine feeder speaks only the Analytics SQL dialect, the one ctx.analyticsSql runs: events.analyticsEngine."<dataset>", the SQL API's sample-weighted COUNT(*), and every value bound as a parameter - $since, $event, and $group when a group is given. The AnalyticsMetricsDialect union, dialectParts, the sqlString literal escaper and the hidden "were params passed" dialect switch are gone; the dataset, which names the table and so cannot be a parameter, keeps its identifier guard.
  • AnalyticsMetricsOptions requires since (an ISO-8601 lower timestamp bound) and has no dialect; AnalyticsMetricsSource.query always receives params; the AnalyticsMetricsDialect type is removed. Pass ctx.analyticsSql as the source. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • fix(studio): ask the host for usage panels by key, never with sql The Analytics tab has one runner, analyticsSqlQuery(panel), which receives a panel key ("volume", "latency", "hotShards") and resolves the rows. The host answers through an admin-gated action that builds the statement server-side with functionUsageQuery(panel) and runs it on ctx.analyticsSql. The old shape handed the host a SQL string to execute, which invited an action that runs caller-supplied SQL against the whole account. The prop docs and the not-wired message now say the action must be admin-only and take the key. The panel drops the second (token-dialect) runner, the precedence between the two, the dataset prop (now the server's choice) and toPanelResult: columns are string[], read off the first row's keys in SELECT order.
  • StudioProps.analyticsQuery is removed and analyticsSqlQuery now has the signature (panel: FunctionUsagePanel) => Promise<AnalyticsSqlQueryResult>. AnalyticsPanelProps loses dataset and runAnalyticsSql, and its runQuery takes a panel key. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • fix(config): report artifacts as unsupported in the alchemy translation The Alchemy translator emits only D1, R2, KV and Queue resources, but an artifacts[] binding was neither emitted nor listed in unsupported, so a config using ctx.artifacts produced a Worker without env.ARTIFACTS and no diagnostic. Raised by review on #941. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • docs(bindings): list the analytics-sql subpath in the readme table Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Added

  • cloudflare analytics sql binding as ctx.analyticsSql (#946) (9c931dd)

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.183
  • @lunora/agent: upgraded to 1.0.0-alpha.165
  • @lunora/container: upgraded to 1.0.0-alpha.68
  • @lunora/errors: upgraded to 1.0.0-alpha.50
  • @lunora/platform: upgraded to 1.0.0-alpha.52
  • @lunora/queue: upgraded to 1.0.0-alpha.88
  • @lunora/scheduler: upgraded to 1.0.0-alpha.106
  • @lunora/values: upgraded to 1.0.0-alpha.60
  • @lunora/workflow: upgraded to 1.0.0-alpha.71
  • @lunora/bindings: upgraded to 1.0.0-alpha.93
  • @lunora/do: upgraded to 1.0.0-alpha.190
  • @lunora/server: upgraded to 1.0.0-alpha.172
  • @lunora/shard-engine: upgraded to 1.0.0-alpha.108
@lunora/codegenrefactor

1.0.0-alpha.251

diff

Refactored

  • codegen: capability-table follow-up and config binding inference fix (#945) (66b7d12)

Dependencies

  • @lunora/advisor: upgraded to 1.0.0-alpha.182
  • @lunora/agent: upgraded to 1.0.0-alpha.164
  • @lunora/container: upgraded to 1.0.0-alpha.67
  • @lunora/platform: upgraded to 1.0.0-alpha.51
  • @lunora/queue: upgraded to 1.0.0-alpha.87
  • @lunora/scheduler: upgraded to 1.0.0-alpha.105
  • @lunora/bindings: upgraded to 1.0.0-alpha.92
  • @lunora/do: upgraded to 1.0.0-alpha.189
  • @lunora/server: upgraded to 1.0.0-alpha.171
  • @lunora/shard-engine: upgraded to 1.0.0-alpha.107
@lunora/configchore

1.0.0-alpha.297

diff

⚠ BREAKING CHANGES

  • capability inference and the codegen probe surface changed.

Added

  • cli: add lunora dev --tunnel via cloudflare quick tunnels (#941) (1446ad1)

Fixed

Dependencies

  • @lunora/codegen: upgraded to 1.0.0-alpha.254
  • @lunora/container: upgraded to 1.0.0-alpha.69
  • @lunora/seed: upgraded to 1.0.0-alpha.182
  • @lunora/studio: upgraded to 1.0.0-alpha.256
@lunora/configchore

1.0.0-alpha.295

diff

⚠ BREAKING CHANGES

  • @lunora/bindings/analytics no longer exports createAnalyticsSqlClient, AnalyticsSqlError or the AnalyticsSqlClient, AnalyticsSqlConfig, AnalyticsSqlResult and AnalyticsSqlColumnMeta types, and the ANALYTICS_SQL_ERROR code is gone. Query with ctx.analyticsSql or createAnalyticsSql({ binding: createAnalyticsSqlRest(...) }) in the Analytics SQL dialect; failures are AnalyticsSqlQueryError (ANALYTICS_SQL_QUERY_ERROR). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • refactor(advisor): read ae metrics in the analytics sql dialect only The quarantined Analytics Engine feeder speaks only the Analytics SQL dialect, the one ctx.analyticsSql runs: events.analyticsEngine."<dataset>", the SQL API's sample-weighted COUNT(*), and every value bound as a parameter - $since, $event, and $group when a group is given. The AnalyticsMetricsDialect union, dialectParts, the sqlString literal escaper and the hidden "were params passed" dialect switch are gone; the dataset, which names the table and so cannot be a parameter, keeps its identifier guard.
  • AnalyticsMetricsOptions requires since (an ISO-8601 lower timestamp bound) and has no dialect; AnalyticsMetricsSource.query always receives params; the AnalyticsMetricsDialect type is removed. Pass ctx.analyticsSql as the source. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • fix(studio): ask the host for usage panels by key, never with sql The Analytics tab has one runner, analyticsSqlQuery(panel), which receives a panel key ("volume", "latency", "hotShards") and resolves the rows. The host answers through an admin-gated action that builds the statement server-side with functionUsageQuery(panel) and runs it on ctx.analyticsSql. The old shape handed the host a SQL string to execute, which invited an action that runs caller-supplied SQL against the whole account. The prop docs and the not-wired message now say the action must be admin-only and take the key. The panel drops the second (token-dialect) runner, the precedence between the two, the dataset prop (now the server's choice) and toPanelResult: columns are string[], read off the first row's keys in SELECT order.
  • StudioProps.analyticsQuery is removed and analyticsSqlQuery now has the signature (panel: FunctionUsagePanel) => Promise<AnalyticsSqlQueryResult>. AnalyticsPanelProps loses dataset and runAnalyticsSql, and its runQuery takes a panel key. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • fix(config): report artifacts as unsupported in the alchemy translation The Alchemy translator emits only D1, R2, KV and Queue resources, but an artifacts[] binding was neither emitted nor listed in unsupported, so a config using ctx.artifacts produced a Worker without env.ARTIFACTS and no diagnostic. Raised by review on #941. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
  • docs(bindings): list the analytics-sql subpath in the readme table Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Added

  • cloudflare analytics sql binding as ctx.analyticsSql (#946) (9c931dd)

Dependencies

  • @lunora/codegen: upgraded to 1.0.0-alpha.252
  • @lunora/container: upgraded to 1.0.0-alpha.68
  • @lunora/errors: upgraded to 1.0.0-alpha.50
  • @lunora/seed: upgraded to 1.0.0-alpha.180
  • @lunora/studio: upgraded to 1.0.0-alpha.254
Open source

Built in the open, on purpose.

Nothing about Lunora is a black box. Read it, fork it, or send the fix yourself.

Lunora on GitHubStar on GitHubContribution guide