Skip to content

v0.47.0

Latest

Choose a tag to compare

@github-actions github-actions released this 18 Nov 15:23
· 1 commit to main since this release

A map of your schema in the admin, and OneSignal pushes with current API keys

v0.47.0 adds a Schema page to the admin that draws your collections and the relations between them, and fixes OneSignal push delivery for the API keys OneSignal issues now. Nothing in this release needs a change on your side.

Added

  • Admin: a Schema page. A new Schema item in the sidebar draws the collections as cards on a canvas, with an arrow for each relation field, from the field's row to the collection it points at. Drag to pan, scroll to zoom, and drag a card to move it; each browser remembers where you put the cards. Hover a card or an arrow to light up what it connects and read what happens on delete (set null, cascade or restrict). Click a relation to jump to its target, and a card's name to open the schema editor. Relations only shrinks the cards for a large schema. The page reads the collections the admin already loads and changes nothing. See Schema.

Fixed

  • OneSignal pushes with current API keys (#16). The App API keys OneSignal issues now (os_v2_app_…) were sent with Authorization: Basic, which OneSignal accepts only for legacy REST API keys. Every push failed with 401, and a new OneSignal app, which can't create a legacy key, couldn't deliver at all. Current keys are sent with Authorization: Key; a legacy key keeps Basic, so installs that work today are unchanged.
  • OneSignal Test connection with an App API key. The button read GET /apps/<id>; it now reads one row of the app's message list, which an App API key may do. It still sends nothing.

SDKs

No SDK release is needed. JS SDK 0.12.0, and Dart vaultbase 0.7.2 with vaultbase_flutter 0.1.6, work with this release.

See the changelog for the full list.

Upgrade notes

  • None. Upgrades are supported from v0.24.0; from an older install, upgrade to 0.24.x first.

Full Changelog: v0.46.0...v0.47.0