Version Packages by github-actions[bot] · Pull Request #858 · OpenSaasAU/stack

github-actions · 2026-08-01T08:16:20Z

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@opensaas/stack-cli@0.36.0

Minor Changes

#857 cdca174 Thanks @borisno2! - Add needs to the base field config: a computed field can declare the immediate relations its resolveOutput hook depends on, so the read fetches exactly those — without widening what the caller receives (ADR-0025).

Since ADR-0024, a bare read (no caller include) returns a row's own columns only, so a virtual field reading item.someRelation silently computed over undefined unless a caller happened to include it. needs fixes that:
```
Order: list({
  fields: {
    lineItems: relationship({ ref: 'LineItem.order', many: true }),
    total: virtual({
      type: 'number',
      needs: ['lineItems'],
      hooks: {
        resolveOutput: ({ item }) =>
          item.lineItems.reduce((sum, li) => sum + li.price * li.quantity, 0),
      },
    }),
  },
})
```
The declared relation is fetched wherever the field is computed — at the root of a read and at every nested level — and is scoped through the Access Filter exactly like a caller-named relation: a dependency the session can't query is not fetched, and the hook sees nothing in its place. A field always computes on whatever it can see, so a partially-denied dependency still produces a value rather than being withheld. The relation itself is stripped from the result unless the caller named it too, for both include reads and fragment query reads.

needs is available on every field type, not only virtual(). opensaas generate now also validates every needs declaration: an entry naming a non-relationship or non-existent field, or a declaration closure that can't fit within the read-include depth cap from any starting point, fails generation with a message naming the offending field/chain rather than silently truncating at runtime.

See docs/adr/0025-a-computed-field-declares-the-relations-it-needs.md.

Patch Changes

#859 ebb4cd3 Thanks @borisno2! - Fix isIndexed: true on text, decimal and calendarDay emitting an invalid inline @index attribute, producing a schema Prisma rejects with "Attribute not known: @index".
Non-unique indexes are now emitted as block-level @@index([field]); isIndexed: 'unique' is unchanged.
Updated dependencies [cdca174, ebb4cd3]:
- @opensaas/stack-core@0.36.0

@opensaas/stack-core@0.36.0

Minor Changes

#857 cdca174 Thanks @borisno2! - Add needs to the base field config: a computed field can declare the immediate relations its resolveOutput hook depends on, so the read fetches exactly those — without widening what the caller receives (ADR-0025).

Since ADR-0024, a bare read (no caller include) returns a row's own columns only, so a virtual field reading item.someRelation silently computed over undefined unless a caller happened to include it. needs fixes that:
```
Order: list({
  fields: {
    lineItems: relationship({ ref: 'LineItem.order', many: true }),
    total: virtual({
      type: 'number',
      needs: ['lineItems'],
      hooks: {
        resolveOutput: ({ item }) =>
          item.lineItems.reduce((sum, li) => sum + li.price * li.quantity, 0),
      },
    }),
  },
})
```
The declared relation is fetched wherever the field is computed — at the root of a read and at every nested level — and is scoped through the Access Filter exactly like a caller-named relation: a dependency the session can't query is not fetched, and the hook sees nothing in its place. A field always computes on whatever it can see, so a partially-denied dependency still produces a value rather than being withheld. The relation itself is stripped from the result unless the caller named it too, for both include reads and fragment query reads.

needs is available on every field type, not only virtual(). opensaas generate now also validates every needs declaration: an entry naming a non-relationship or non-existent field, or a declaration closure that can't fit within the read-include depth cap from any starting point, fails generation with a message naming the offending field/chain rather than silently truncating at runtime.

See docs/adr/0025-a-computed-field-declares-the-relations-it-needs.md.

Patch Changes

#859 ebb4cd3 Thanks @borisno2! - Fix isIndexed: true on text, decimal and calendarDay emitting an invalid inline @index attribute, producing a schema Prisma rejects with "Attribute not known: @index".
Non-unique indexes are now emitted as block-level @@index([field]); isIndexed: 'unique' is unchanged.

@opensaas/stack-auth@0.36.0

@opensaas/stack-rag@0.36.0

@opensaas/stack-storage@0.36.0

@opensaas/stack-storage-s3@0.36.0

@opensaas/stack-storage-vercel@0.36.0

@opensaas/stack-tiptap@0.36.0

@opensaas/stack-ui@0.36.0

vercel · 2026-08-01T08:16:24Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
stack-docs	Ready	Preview	Aug 2, 2026 3:25am

github-actions · 2026-08-02T03:37:34Z