Skip to content

Ridu v0.11.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Oct 06:55
v0.11.0
1dfefbf

Ridu 0.11.0

This release lets applications hide collections and globals from the admin without changing their
API behavior, and removes the need for migrations when only admin presentation settings change.

Changes

  • Set CollectionAdmin.Hidden or GlobalAdmin.Hidden to omit a resource from admin navigation,
    the dashboard, and search. Its admin routes show not-found, including custom document views.
  • Hidden resources remain available through REST, GraphQL, and the Local API. Access rules, hooks,
    cascading deletes, and relationship selection/editing still apply. Hiding a resource is a
    presentation choice; use access rules to restrict its data.
  • Relationships to hidden resources keep their labels and editor flows without links to admin
    pages that do not exist.
  • Migration currentness and production readiness ignore explicit Admin presentation metadata
    on collections, globals, fields, and blocks. Changing settings such as Hidden or Group
    therefore needs no migration. Storage-schema drift and migration-ledger corruption still fail
    readiness checks.
  • Production migration fingerprints bind the ordered artifact identities, recorded head digest,
    and schema with admin presentation removed.

Breaking change and upgrade

Update the Go module and every Ridu npm package to 0.11.0 together, regenerate application
contracts, and rebuild with the matching CLI.

migration.DigestArtifactHistory now requires three arguments: the ordered artifact identities,
the recorded head manifest digest, and the manifest. Its fingerprint encoding has changed. Update
custom Go callers and recompute manually embedded migration-history fingerprints. Applications
built through ridu build receive the new fingerprint automatically.

Persisted migration artifacts and database ledgers retain their existing encodings. Do not rewrite
them to adopt this release. Admin-only changes require no new migration; use the ordinary migration
workflow for application storage-schema changes. Manifest, protocol, and plugin format/API counters
remain unchanged.

Assets 24
Loading