Skip to content

Releases

Apps 0.29.1: discoverable indexed filters

Choose a tag to compare

@sthamann sthamann released this 11 Nov 00:40

App hosts can derive discoverable list filters from actual indexed entity fields with model 0.14.0. Generic filters expose their names, scalar types, localized labels and string choices; authored schemas remain intact. Existing storage admission continues to enforce identity, permissions, index, count and byte limits.

Validation includes model tests, Clippy, the actual PostgreSQL storage contract, independent runtime and data-service checks, and the component image build. Veyndo integration and hosted agent acceptance are tracked separately.

Apps 0.29.0: independent job supervision

Choose a tag to compare

@sthamann sthamann released this 06 Nov 15:44

App Data service 0.5.0 supervises existing App jobs through HTTP, OpenAPI, MCP and the unchanged JavaScript SDK: bounded history/detail and approved cancel, retry, resolve and archive operations.

Original control transitions, row revisions, retained worker leases and atomic events remain shared. Native Veyndo consumes the same extracted current-rights/current-package result redaction and queued-event selection.

The explicit schema-5 serving profile uses fixed signed-RLS storage and exact control-only nonowner grants. It cannot enqueue, change worker input/results or create SQL objects. Actual trusted producers, worker-package provisioning and execution remain separate owners.

Actual Rust/PostgreSQL/HTTP/MCP/SDK and nonroot Linux container acceptance pass, including two shops and actors, revocation/redaction, all controls, uncertain-outcome approval, races, late rollback, SQL grants and restart. Existing record/settings/install journeys remain passing.

Guide: data-service/jobs.md. Executable example: data-service/examples/jobs.mjs.

Apps 0.28.0: independent package installation

Choose a tag to compare

@sthamann sthamann released this 06 Nov 14:54

The App Data service 0.4.0 can independently review and install complete private data Apps, configure their encrypted settings and use their records through HTTP, MCP and the existing JavaScript SDK. The complete compiler, original atomic installation sequence and extracted native model installer are shared with Veyndo.

The explicit schema-4 profile preserves current personal administrator authority, exact permission/digest/revision consent, immutable versions, signed tenant isolation and original row/byte budgets in fixed shared tables. No Core process or migration credential is needed in the serving image.

Component and actual nonroot Rust container acceptance pass, including two shops, revocation, concurrent installs, additive upgrades, immutable versions, late rollback, quotas, settings/records and restart.

Setup: data-service/installation.md. Executable example: data-service/examples/install.mjs. Standalone native resources, jobs, restore and release orchestration remain separate follow-ups.

App components 0.27.0: independent encrypted settings

Choose a tag to compare

@sthamann sthamann released this 06 Nov 13:59

App Data service 0.3.0 can configure installed Apps through HTTP, MCP and the existing JavaScript SDK. Secret settings remain encrypted and have no read/export endpoint. Native Veyndo and the independent host share the same settings read/partial-update/CAS transaction and original platform AES-GCM envelope.

The explicit settings profile requires schema 3, narrow database grants, its own operator vault key and current nondelegatable personal live administrator authority. Default reader and managed-record profiles retain their existing grants. Trusted package installation/digest registration remain with their owner.

Verified through the actual Rust process and restricted PostgreSQL login: two shops, current scope/claim rejection, secret-safe projection, retained omitted secrets, package upgrades, concurrent CAS, late event rollback, wrong keys/ciphertext binding, reconnect and HTTP/MCP/SDK. Linux CI and the nonroot read-only container pass. Shared storage contracts and native App/Studio/surface/secret/isolation integration pass.

Setup: https://github.com/veyndo/apps/blob/main/data-service/settings.md
Source: 5e24268

Managed App Data writes 0.26.0

Pre-release

Choose a tag to compare

@sthamann sthamann released this 06 Nov 13:18

Adds an explicit optional App Data write profile with approved package-bound record CAS changes, current merchant/action rights, original App-owned states/immutable fields, retained historical read scopes and atomic minimized outbox events. HTTP/OpenAPI/MCP and the existing generic JavaScript SDK share the same operations. Default read-only schema and grants remain unchanged.

The explicit schema-2 upgrade uses restricted nonowner serving credentials. Package row locks cannot modify packages; models/schema/install remain outside the service. Unsupported native resource/translation/index/commerce policies deny without fallback. Native Veyndo consumes the original shared lifecycle/history hooks while keeping full native admission.

Actual Rust/PostgreSQL/current-identity/HTTP/MCP/SDK and Linux nonroot container acceptance pass: two shops, positive/excessive grants, approval/digest/revision rejection, concurrent CAS, states, historical rights/retention, late event/history/output rollback and reconnect. Original storage/runtime/service CI also passes. Full independent installation/native-policy/settings/jobs/restore/publication and Flow dispatch remain separately tracked.

App Data reader bundle 0.25.1

Pre-release

Choose a tag to compare

@sthamann sthamann released this 06 Nov 12:32

App Data reader service 0.1.1 now rejects explicit null values for optional limit, after and id fields, consistently with its HTTP/OpenAPI/MCP query contract. Missing fields retain their defaults. Storage remains 0.25.0 and shared authority 0.1.0; native behavior is unchanged.

The final source passes actual Rust/PostgreSQL/current-identity/HTTP/MCP/SDK tests including all null cases, the existing storage/runtime/service checks and the real nonroot read-only container acceptance on Linux. This bundle includes the independent reader introduced in 0.25.0. Full independent installation/write/settings/jobs hosting remains separately tracked.

App Data reader 0.25.0

Pre-release

Choose a tag to compare

@sthamann sthamann released this 06 Nov 12:23

Adds an independent read-only App Data service with HTTP/OpenAPI/MCP and unchanged Veyndo SDK/Fetch examples. Current OAuth merchant/action authority, a supported fixed reader schema, restricted nonowner login and signed read-only transactions are required. Original native page preparation/projection and database scope signing now share one owner; the existing Runtime service uses the shared current identity adapter.

Local and Linux CI validate the actual Rust process, independent PostgreSQL/identity endpoint, two shops, current permissions and revocation, package disable, denied SQL forgery/writes, field projection, pagination, native resolver denial and HTTP/MCP/SDK parity. Both data reader and runtime container acceptance pass.

This prerelease covers reads. Complete independent installation, writes, settings, jobs and native object resolver hosting remain tracked separately. No public deployment or production data cutover is included.

Apps 0.24.0: independent runtime HTTP OpenAPI and MCP service

Choose a tag to compare

@sthamann sthamann released this 06 Nov 11:45

Run the same bounded WIT commerce engine as an independent Rust service, without starting Veyndo or PostgreSQL. HTTP, OpenAPI and stateless MCP share typed price/shipping/discount/validation simulation, source/input fingerprints and explicit no-effect results. The existing Veyndo SDK connects unchanged.

Fresh fixed-endpoint OAuth introspection admits current subject, workspace, scope, audience and expiry. Strict source/snapshot/money budgets, sanitized errors and task-owned global/tenant/subject permits preserve bounds across timeout/disconnect. Includes Fetch/SDK examples, a non-root Rust-only Docker recipe, focused service CI and actual Linux container identity/HTTP/MCP/SDK acceptance.

Model 0.13.0 exposes original frozen-value bounds; the native full contextual validator preserves its prior checks. Runtime 0.2.0 remains the shared engine. Full standalone app data/installation identity, schema provisioning, APIs and hosted deployment remain separate component tasks.

Apps 0.23.0: schema migration and bounded recovery snapshots

Choose a tag to compare

@sthamann sthamann released this 06 Nov 11:03

The shared storage crate now owns the original explicit schema conversion and bounded recovery snapshot workflow inside package installation. Required host field/language validation uses the original transaction; complete compiler, identity, trust, consent, reference projection and commit remain host-owned.

Preserves declared old values/manifests, 2,000-row/4 MB/16 MB limits, model/record revisions and atomic schema event. Exhausted record revisions reject after validation. No new schema, identity, pool, independent commit or automatic schema rewind.

Includes a runnable schema_upgrade example, exact Core provenance and actual PostgreSQL installer/rollback/isolation/budget/overflow tests. Both independent Linux verification runs pass. Native product acceptance is documented separately in the main repository.

Apps 0.22.0: package activation and dependency fencing

Choose a tag to compare

@sthamann sthamann released this 06 Nov 10:41

Share original app activation/deactivation sequencing, active-dependant checks and revision CAS behind mandatory current host config/activation/connected-frontend admission. Native Veyndo uses the same code and retains management/merchant/signed identity, current consent/operator trust/dependencies/commerce/lifecycle and caller commit. Original error order, same-state revision behavior and retained operational data remain unchanged. No new schema, events or implicit installation.

Real PostgreSQL tests use actual shared installer/writer fences to prove dependency race exclusion in both orders, concurrent state CAS, host denial, error order, rollback/reconnect and revision exhaustion. Two Linux component runs, 74 native App units and seven native integration modules pass. Includes denied-without-authority executable example. Standalone production identity/schema/API/MCP hosting remains open.