Release v1.12.0

Applications can now collect product feedback from their users with the new Notes part, and Stage Manager can run published Stage applications permanently or for a period.

Added

• Cratis.Showrunner.Notes.Contracts: public events for feedback given on the current context, chosen slices, a screen, a component or a suggested change to a component's property, and for the answers sent back (acknowledged, addressed in a version, declined). See Notes. (#69)
• Cratis.Showrunner.Notes: commands for an application's signed-in users to give, suggest and withdraw notes, the live MyNotes list with each note's status, and publishing of notes to the people building the application; NotesOptions.BindFrom reads the options from configuration. (#69)
• Cratis.Showrunner.Notes.Collecting: the receiving side that records an application's notes in the right tenant and answers them. (#69)
• Notes can travel over HTTP between an application and a receiver on a different Chronicle kernel, authenticated by a token per publication, with Notes__Transport=Http. See Transports. (#69)
• @cratis/showrunner.notes and @cratis/showrunner.notes.react: the feedback button with its drop-down (this context, specific slices, this screen, point at a component to describe it or suggest a property change, my feedback), the same button in slice-owned dialogs, and the feedback dialogs. (part of #70)
• Stage Manager runs a published Stage application from a Performance with spec.application.published: the exported package from a ConfigMap, storage from a Secret, sign-in through AuthProxy, Notes over HTTP, rollouts that roll back on failure with a version history, and CPU and memory usage in the status. See Published Stage applications. (#71)
• A Performance can run permanently or until a given time (spec.lifetime); at that time its public route is removed, it is scaled to zero and its phase becomes Expired. (#71)

Changed

• The JavaScript packages require @cratis/arc 22.155 or later.