Skip to content

chore(deps): require @norbix.ai/ts 4.11.0 (database last wave) - #42

Merged
Domantas merged 3 commits into
mainfrom
chore/ts-4.11-database-last-wave
Oct 5, 2026
Merged

Domantas merged 3 commits into
mainfrom
chore/ts-4.11-database-last-wave

Conversation

@Domantas

@Domantas Domantas commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Moves @norbix.ai/react-redux onto @norbix.ai/ts 4.11.0, the core SDK release for the last gateway Database wave.

  • @norbix.ai/ts peer >=4.11.0, dev ^4.11.0.
  • No hook added or removed: 4.11.0 has the same SDK method list as 4.10.0. The hook-per-SDK-method guards for hub.database (73) and api.database (22) pass.
  • New tests: through the real SDK over a fake fetch, updateManyRecords sends PUT …/collections/orders/many and deleteManyRecords sends DELETE …/collections/orders/many, both with allRecords: true.
  • README: "Bulk record writes (core SDK 4.11.0)" — allRecords for an empty filter, and the new errors 035 / 036 / 037.

Checks in the worktree: typecheck clean, lint clean, vitest run 256 / 256 passed, build ok. Task file: docs/tasks/database-last-wave.md.

🤖 Generated with Claude Code

Domantas and others added 3 commits October 5, 2026 23:55
@norbix.ai/ts 4.11.0 follows the last gateway Database wave: update many /
delete many take allRecords, taxonomy rows carry dependencyRefs, trigger
rows carry env. Same SDK method list as 4.10.0, so no hook changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e many

Through the real @norbix.ai/ts client over a fake fetch, updateManyRecords
sends PUT .../collections/orders/many and deleteManyRecords sends DELETE
.../collections/orders/many, both with allRecords: true.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Explains allRecords for an empty filter and the new database errors
(035, 036, 037) the bulk and write hooks can now return. Task file
docs/tasks/database-last-wave.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

🚀 Release preview

Next version on merge to main: none

semantic-release dry-run output
[8:56:54 PM] [semantic-release] › ℹ  Running semantic-release version 25.0.9
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/npm"
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/github"
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/npm"
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/npm"
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/github"
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/npm"
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/github"
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/github"
[8:56:55 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/github"
[8:56:57 PM] [semantic-release] › ℹ  This test run was triggered on the branch refs/pull/42/merge, while semantic-release is configured to only publish from main, therefore a new version won’t be published.

If next_version is none, your commits don't trigger a release. Use feat: for minor (breaking changes too, until launch), fix: / perf: for patch.

@Domantas
Domantas merged commit 892d7d5 into main Oct 5, 2026
2 of 5 checks passed
@Domantas
Domantas deleted the chore/ts-4.11-database-last-wave branch October 5, 2026 21:17
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

🎉 This PR is included in version 1.8.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant