What changed
@sistent/sistent 0.22.0 fixes a share bug that had been live since April: the share modal sent a snake_case access payload (grant_access / revoke_access / notify_users / actor_id) that the cloud API silently dropped, so sharing a design or view appeared to succeed while granting nothing (layer5io/sistent#1786). 0.22.0 emits the camelCase names the API actually reads.
Kanvas picks this up in layer5labs/meshery-extensions#4324. Note the fix reaches users when meshery/meshery's UI ships the 0.22.0 pin - @sistent/sistent is externalized, so the host supplies the runtime copy.
Why this needs a docs change
Two things are now user-visible and undocumented:
1. The share behaviour itself. Anyone who shared a design or view between April and this release should be told their grants may not have been applied, and to re-check the People with Access list on anything they believed they had shared. This is the part that matters most - a silent grant failure means people may believe collaborators have access who do not.
2. Three new notifications the Kanvas PR adds, all replacing what were previously silent failures:
- Changing visibility on a resource kind that has no visibility mutation now reports that it is unsupported, instead of reporting success.
- Clicking Share while the design body is still loading (or failed to load) now says sharing is unavailable, instead of doing nothing at all.
- A failed load of the access list now says so, instead of rendering as though nobody has access - which previously also hid the owner row and left no way to revoke existing grants.
Suggested scope
A short note in the Kanvas sharing/collaboration docs covering the corrected behaviour and the re-check advice, plus the three messages so support has something to point at. Happy to draft it if someone points me at the right page.
What changed
@sistent/sistent0.22.0 fixes a share bug that had been live since April: the share modal sent a snake_case access payload (grant_access/revoke_access/notify_users/actor_id) that the cloud API silently dropped, so sharing a design or view appeared to succeed while granting nothing (layer5io/sistent#1786). 0.22.0 emits the camelCase names the API actually reads.Kanvas picks this up in layer5labs/meshery-extensions#4324. Note the fix reaches users when
meshery/meshery's UI ships the 0.22.0 pin -@sistent/sistentis externalized, so the host supplies the runtime copy.Why this needs a docs change
Two things are now user-visible and undocumented:
1. The share behaviour itself. Anyone who shared a design or view between April and this release should be told their grants may not have been applied, and to re-check the People with Access list on anything they believed they had shared. This is the part that matters most - a silent grant failure means people may believe collaborators have access who do not.
2. Three new notifications the Kanvas PR adds, all replacing what were previously silent failures:
Suggested scope
A short note in the Kanvas sharing/collaboration docs covering the corrected behaviour and the re-check advice, plus the three messages so support has something to point at. Happy to draft it if someone points me at the right page.