Osy#betaRun it on Osyrin: osyrin.com

What's new

What changed in osy 0.19.x.

Every published version of the toolchain, newest first, with the notes its release carries. The same notes in your terminal: osy whats-new. Install or update with curl -fsSL https://osysharp.com/get | sh. Older releases.

osy 0.19.15 16 November 2026

This release brings organisation policy for packages, keyed secrets, the Artifacts kit, a large round of security fixes and a larger Admin bundle limit. Every app on Osyrin Cloud moves to 0.19.15 automatically. If you run the platform yourself, upgrade the control plane, Admin, the zone and the CLI together. To upgrade, run osy upgrade, then osy update in a project.

Breaking changes

  • ⚠ People signed in before the upgrade sign in again within about an hour. A sign-in ticket now names the app (and environment) it was issued for, and is accepted only there. Tickets issued before the upgrade keep working until they expire, but are not renewed.
  • ⚠ Admin 23.0.0 is a major version. It needs platform 0.19.15 or newer (0.19.14 was never released). A restore no longer takes a separate transfer grant, and every GitHub CI deployer of an app must be made again, now naming the repository by its id (the refusal says which ids to use).
  • ⚠ Backup files uploaded for a restore before this release must be uploaded again. A zone now loads only uploads recorded for that app and environment, and uploads made before this release have no record.
  • ⚠ A deploy now drops configuration you removed from your app — an API, MCP, OAuth or auth block — even without --prune.
  • ⚠ Raising an event on a cancelled workflow run is now an error (WorkflowCancelled) for a caller the event's [Authorize] admits; it used to be ignored silently. An event that declares no [Authorize]-checked raiser, or a run whose row is gone, stays a quiet no-op.
  • ⚠ A rename line in a migration must name the old entity, field or enum member in the same letter case. A line that matched only when case was ignored used to lose the old table's rows or leave a renamed field empty. It is now refused at every door.
  • ⚠ RecordOutsideModelCall charges a call with an Account to key:<Account> itself; naming a key: scope yourself is refused.
  • ⚠ In Admin, adding a member to an organisation sends an invitation. Creating an app when you belong to several organisations must name the organisation (osyrin app create --org).

Language

  • Keyed secrets: new Secret("X") { Keyed = true, MayWrite = P } holds one value per id (Secret.X.For(id), IsSetFor, WritesFor, RetireFor), with who may write each one decided by a policy you name.
  • FileAsset.Versions lists a file's history.
  • onFocus, onFocusWithin and onBlurWithin, so whatever opens on hover can open from the keyboard too (WCAG 1.4.13). onFocus runs when the element itself takes focus, and an element with onFocus becomes a stop in the tab order. onFocusWithin runs when focus enters an element or anything inside it, and onBlurWithin runs when focus leaves all of it. Moving between controls inside does not run either. Close what opened with onEscape: open ? Hide : null. See osy docs onFocus.

Runtime

  • A live call passed a list of rows binds them as the viewer sees them, in page order (it used to receive bare ids).
  • A write to a field the writer may change but not see always lands.
  • Creating an app's settings row on first use never discards other changes the same request made.
  • Zone deploys no longer fail their dry run with "version app_vN has no model blob" when a live workflow run still records an older version.
  • A request handed to the new runtime during a move is logged as handed on, not as a 500.
  • Admin's database schema is brought up to the model a node serves before any session uses it, so an upgrade no longer fails on a column the new model added (42703).
  • An Admin bundle larger than 30 MB can be deployed. The control plane's deploy route read at most 30 MB, the web server's default, although it allows 512 MB. Admin 23.0.0 is just over 30 MB, so 0.19.14 could not install it. 0.19.15 is 0.19.14 with this fix; 0.19.14 itself was never released.

Security

  • Sign-in tickets are bound to their app. A ticket from one app is refused by another, and one from another environment of the same app is refused too. Only an app's own sign-in can issue a ticket for its own accounts.
  • Routes closed. REST APIs no longer accept the anonymous ticket (your data rules still applied, but the door is now shut). The zone gateway's diagnostics route (/_diag) answers only with the gateway's own token, and the old self-registration route is gone. Compile helpers need a Developer. Control-plane routes refuse any ticket but the control plane's own. Uploading over an existing public file is refused.
  • Admin fixes. Backups, restores and backup deletions check permission before acting, and a backup can only be downloaded from its own app's place. A custom domain is verified only through DNS. A team's release move is only a request for the release it is approved for. An app's admin can no longer make themselves its owner. Organisation owners can no longer change their own organisation's status, type, backup records and backup key, or zone placement.
  • Package code runs as the package that wrote it, and app code as the app — including a default value one of them gives a field the other creates. A package's allowed hosts are reached only by that package's code.
  • osy query never returns a credential. Answers that would carry one are refused, with a redaction backstop.
  • A function kept only so a live workflow run can finish is never callable by a request. Removed functions and removed security {} rules no longer survive a deploy, except that a function a live run still calls stays, uncallable by requests, until no run needs it.
  • Rate limits and the sign-in trail use the real visitor address. The gateway and the control plane take it only from the trusted hop in front of them. The sign-in trail records where each sign-in came from, and marks a ticket not issued by the sign-in flow.
  • Anonymous server calls are limited to 300 a minute per address (then 429); signed-in callers are not counted. Kit mail and invitation sending have limits.
  • A host refuses to start on a file store that would let two writers overwrite each other (create-if-absent is checked at startup).
  • Cascaded deletes are judged by the same rules as the delete that started them.

Osyrin Cloud

  • Approved and required packages. An organisation's packages.approved rule refuses, at the deploy ask, a package it does not cover; what each package reaches is recorded, signed into the deploy and checked against its files at the zone. A packages.required rule names packages every app must compose. On a single-node platform the rule also holds at compile, git deploy and push, osy test and debug.
  • Each platform release records the kits it carries and what each can reach, for organisations that approve packages.
  • Builders see the policy before they build: osy policy [egress|packages|settings], and early warnings from osy validate and osy deploy about hosts and packages the organisation has not approved. A refusal explains which rule refused, what it allows and how to comply; osy policy request asks a policy admin for an exception. An organisation can hide a rule's entries from builders and set where and by how many an exception may be approved.
  • Refused deploys are recorded and shown on the organisation's Policy page; an app's own policy requests are listed per environment.
  • Admin 23.0.0: organisations ask for another plan from Billing and operators approve; invoices numbered per organisation per year behind a random customer code; operators issue, void and credit invoices.

Testing

  • Under osy test --pixels, a control a box cuts off can no longer be clicked or filled. Ui.Click, Ui.Fill, Ui.Select and Ui.Check refuse a control that lies outside what an overflow: Hidden box around it shows, and the error names the box. A person cannot see or press such a control. Before, the test passed anyway. A box that scrolls is not refused.
  • Ui.Focus(control) moves the keyboard to a control, as a Tab that reached it would, so a test can show that hover content also opens on focus. It refuses a control the keyboard cannot reach. Read where focus is with Assert.Focused. It also finds a stop by its label: alone (a chart, a list box, a radio group), which before only worked for something you could click.

Kits

  • New: Osysharp.Artifacts 0.1.0 — things made for review (HTML prototypes, pictures, PDFs, notes) kept with every version, commented per version, and shown in a viewer the browser sandboxes, so an agent-made page can never act as your app.
  • Agents: work an app records as an agent's can be charged to the app's own scopes (chargedTo, ChargesAgentWorkTo); delegation and conversations between agents; an agent's work can run on a named model key (AgentRef.WithKey).
  • Llm: a call can name which of the app's model keys serves it (LlmCall.Key), each key held by one budget; a model call measured elsewhere can be recorded on the meter (RecordOutsideModelCall) and counts against the budgets after the fact.
  • UserAccounts: a phone number on an account says what it is for — calls (any number, never texted) or texts (a mobile confirmed by a code). Invitations and access changes run as narrow actors.
  • Lists, menus, pickers and tips are never cut off by the box they open in. A SelectField's list, a Menu, the calendar of a DatePicker (and the DateTimePicker, TimePicker and DurationField popovers) and a tip now open in the browser's top layer, above every panel, card, dialog and scrolling box, whatever its overflow. Each one stays attached to the field that opened it as the page scrolls or resizes. It opens above the field when there is no room below. Keyboard, focus and Escape work as before. Before, a panel with overflow: Hidden or a scrolling side panel cut them off, so the last days or options could not be chosen.
  • A chart's readout works from the keyboard (Osysharp.Charts 1.9.0). The plot is one tab stop, named after the chart. When focus arrives, the readout shows the first category's values. The arrow keys move it one category at a time, and Home and End go to the first and last. Escape hides it and focus stays on the chart. The readout also hides when focus leaves. A screen reader hears each point in the words the readout shows. A readout opened by the pointer now also hides on Escape (WCAG 2.1.1, 1.4.13).
  • Tips close on Escape. A tip shown on hover or keyboard focus (the key tip on a button, the label on a collapsed rail or sidebar mark, and any inside X.Hover/inside X.Focus block that changes Display) now hides when you press Escape, with the focus and the pointer left where they are. It shows again when you move away and come back (WCAG 1.4.13).
  • Osyrin.Look: an open hover title (ClampText, RelativeDate, LevelMark, ReadinessMarks, DependsMark, SummaryEntry) now closes on Escape. With focusable: true, the part is also a keyboard stop: its title opens on focus and closes when focus leaves.
  • Every kit dropdown now draws the kit's own chevron (Osysharp.Ui 3.4.0). SelectField used to show the browser's arrow. It now shows a 12px chevron in Colors.SelectChevronInk, which defaults to your theme's MetaText. The box keeps Length.SelectChevronRoom (30px) clear at its right for it and shows a pointer cursor. Its height, padding tokens, line and words are as before; the words sit about 4px further left, because the browser's own inset goes with its arrow. The select is still the browser's own control: its keyboard, its screen reader and its option list. To restyle the chevron, set those two tokens in your theme.
  • A setting's choice is the kit's dropdown. SettingChoice renders through SelectField, so it offers an enum's members in their [Label] words exactly as SelectField does and wears the same chevron. SelectField has three new parameters: onChange (runs after a pick is written), showLabel: false (names the select without drawing a caption), and setting: true (the face a setting row uses).
  • A dropdown can say what each option means (Osysharp.Ui 3.4.0). Give SelectField a detail: and it opens the kit's own list instead of the browser's: each option shows its words and, under them, a line saying what it means ("Business" over "$199 a month, 25 applications"). words: names options that are rows rather than enum members (options: plans, words: p => p.Name). Closed, the box looks as before and shows the chosen option's words. It is an ARIA listbox: ↓ or Enter opens it on the chosen option, ↓/↑/Home/End move, typing letters goes to the next option whose words start with them, Enter chooses, Escape or Tab closes it without choosing, and the keyboard returns to the box. A screen reader hears each option's words, then what it means. SettingChoice takes the same two parameters. A SelectField without them is unchanged.
  • A number box groups its digits while you are not typing in it. 200,000 with no culture declared, 200 000 under sv-SE. Click into the box and it shows 200000. A number below 10 000 is not grouped, so a year shows as 2026; this follows the common style rule (SI, the Swedish language rules and many style guides). You can type a number with or without separators. What is stored is always the plain number.

The release on GitHub, with every asset and its SHA-256

osy 0.19.13 14 November 2026

This is a security release. It closes ways a signed-in person could run parts of an app they were never meant to reach, including one way to get another account's sign-in ticket. Every app on Osyrin Cloud has already been moved to 0.19.13. If you run the platform yourself, upgrade now. To upgrade, run osy upgrade, then osy update in a project.

⚠ Read first

  • ⚠ A request can now run only the functions your app's pages call. Before this release, anyone signed in to an app could run any of its top-level functions by naming it, with arguments of their choosing. Now a page's request may run only a function your pages call (an action, a component member, its render, or a helper those run, also one the browser runs itself), a function marked [AllowAnonymous], or a sign-in method ([AuthMethod]). Anything else is refused with "is not exposed to a request". REST endpoints, MCP tools, offered actions and osy run are not affected by this rule: each runs the function it declares. Your app is rebuilt on this release when it moves, and that rebuild records which functions your pages call. If a client of yours other than your pages named a function directly, give it a REST endpoint or an MCP tool.
  • ⚠ A function that returns a sign-in ticket or a signed token can no longer be called by a request. This covers a function that returns Security.IssueJwt(…), or a token signed with Crypto.SignRs256 or Crypto.SignEs256 (for example a GitHub App's JWT), either directly or in a field of what it returns. It is refused on every request path, including REST endpoints and MCP tools, unless it is an [AuthMethod]. Sign people in through an [AuthMethod], and call such a helper from your own server code.

Security

  • Osysharp.UserAccounts 1.5.0. Only the sign-in flow can sign an account in. Admit and ContinueSignIn now refuse every caller except the sign-in flow (an [AuthMethod], or code inside runas (AuthBootstrap)). Before, a signed-in account could get another account's ticket through them. Your own sign-in steps that end in ContinueSignIn from an [AuthMethod] work as before. Apps still on 1.4.0 are protected by the two rules above once they run on 0.19.13. Move to 1.5.0 when you next deploy (osy update).

Admin

  • Admin 22.3.1 carries the Osysharp.UserAccounts fix above.

The release on GitHub, with every asset and its SHA-256

osy 0.19.12 14 November 2026

This release closes several ways a package or an app could act with more rights than it was given, makes an organisation's outbound-host policy hold on every path an app sends from, makes app migrations' copy/merge/split/transform lines work again, and makes a commit that creates many rows with Markdown members much cheaper. To upgrade, run osy upgrade, then osy update in a project.

⚠ Read first

  • ⚠ Agents 2.0.0 (major). An agent now works for the person the platform recorded, never for a person your code names. Agents.Of<X>().For(Principal) is removed. App authors change three things:
    • Name the row the work is about, not the person. For(row) works for whoever made row, as its [CreatedBy] stamp records. Add the stamp to the entity if it has none, and fill it for the rows you already have with a migration in the same deploy.

      Before (Agents 1):

      var outcome = await Agents.Of<Editor>().For(report.Employee.User).Do(new Summarise(), report.Title, about: report.Title);

      After (Agents 2):

      entity Report {
        [CreatedBy] Guid? CreatedBy;
        [Required] Employee Employee;
        string Title = "";
      }
      
      var outcome = await Agents.Of<Editor>().For(report).Do(new Summarise(), report.Title, about: report.Title);

      And in the deploy's migration, for the reports made before the stamp:

      migration "reports record their maker" {
        backfill Report.CreatedBy = r => r.Employee.User;
      }

      Change every call that passes a person. Agents 2.0.0 still compiles one, but the work is then for whoever made that person's account, or for nobody, and then the agent acts alone with its own rights. The kit's next release refuses such a call when it runs.

    • Say where a proposal is answered, and relay the answer, not the person. If your code puts an agent's proposal where a person answers it, call AwaitProposalAnswerIn(proposal, row) with that row. RelayProposalDecision now takes the row the person answered with, where it took the person. The platform reads who answered from that row's [CreatedBy], and the row must [RollsUpTo] the row the proposal was put in. An answer given anywhere else decides nothing. The Agents.HumanRequests bridge does all of this for you.

      Before (Agents 1):

      [On] void PutOnSlip(AgentProposed e) {
        new Slip { Proposal = e.Proposal.Id, Title = e.Proposal.Label };
      }
      
      var person = Principal.FirstOrDefault(p => p.Id == answer.AnsweredBy);
      RelayProposalDecision(proposal, answer.Yes, "", person);

      After (Agents 2):

      entity SlipAnswer {
        [Required, RollsUpTo] Slip Slip;
        [CreatedBy] Guid? AnsweredBy;
        bool Yes;
      }
      
      [On] void PutOnSlip(AgentProposed e) {
        var slip = new Slip { Proposal = e.Proposal.Id, Title = e.Proposal.Label };
        AwaitProposalAnswerIn(e.Proposal, slip);
      }
      
      RelayProposalDecision(proposal, answer.Yes, "", answer);
    • Move the agents family together. Agents goes to @2, Inspector and Management to @3, and the others to @2.

      Before:

      use Osysharp.Agents@1;
      use Osysharp.Agents.Management@2;
      use Osysharp.Agents.Inspector@2;

      After:

      use Osysharp.Agents@2;
      use Osysharp.Agents.Management@3;
      use Osysharp.Agents.Inspector@3;
  • ⚠ If you deployed copy X -> Y; together with drop property X; before this release, X's values were removed and not copied. Restore them from a backup taken before that deploy.
  • ⚠ A migration line you deployed before this release runs on your next deploy that still carries it. An app migration's copy, merge, split and transform lines, and backfill on an optional member, were accepted and did nothing from 29 Jun 2026 through 0.19.11. They work again — including a backfill whose value is counted or summed over a related collection — and each writes only the rows of its own type (a subtype stored in its base's table no longer touches the base's other rows). Each line runs once per database, on the first deploy that carries it. A platform upgrade runs no app migration.
  • ⚠ merge, split and transform rewrite every row of their type. copy and backfill fill only values that are still empty. So a transform you deployed months ago also rewrites every row written since then. Read your migration files before your next deploy.
  • ⚠ A workflow that runs as its declared actor now acts for the person who started the run (the run row's [CreatedBy]), automatically. Every read and write is allowed only when both the actor and that person may. A run nobody is recorded as starting acts as the actor alone. A starter who has been switched off or removed counts as nobody: they have only the rights of a visitor who is not signed in. Adding [CreatedBy] to a run row therefore narrows that workflow's bodies to what the starter may do.
  • ⚠ In such a body, runas (<that actor>, onBehalfOf: p) now runs only when p is the person who started the run. Any other person is refused, and so is any onBehalfOf: when the run's row has no [CreatedBy]. Code that passed a person of its own choosing stops working. Declare [CreatedBy] Guid? StartedBy; on the run's row and write onBehalfOf: this.Item.StartedBy, or leave onBehalfOf: out, since the starter is already acted for.
  • ⚠ A kit's hidden or credential field read through your own entity that derives from the kit's entity no longer compiles. Before, a deploy accepted it; now it is refused as it is on the kit's own entity. An app that deployed such a read must change it before it can deploy again.

Security

  • A package's code runs only with its own capabilities, secrets and permissions, whatever namespace or path its files claim. Every server build checks each package archive; osy package check runs the same check offline. osy validate and osy publish in a package's folder refuse a package that grants the package it uses the computer, and warn (PACKAGE_GRANT_TO_DEPENDENCY_IGNORED) on any other grant to it. Such a grant never gave anything: the app grants.
  • A zone builds only the packages the control plane signed for a deploy; any other package a deploy names is refused by name before anything is compiled.
  • A zone builds a package archive for an organization only if that organization has itself uploaded it to that zone. A deploy that names an archive its organization never uploaded must carry it, or it is refused, naming the package. The platform's own packages are exempt. Each organization's first deploy after this release uploads its packages once more, so it is slower once.
  • An application file whose path contains :: is refused at compile (APP_PATH_HAS_CARRIER_SEPARATOR), so it can no longer be read as a package's file and take that package's permissions. A package archive that holds a file whose name contains :: is refused when it is installed or checked; osy package pack and osy publish refuse one before it is published, with the same message. osy validate now refuses an application file under Capabilities/ or Core/ the same way the server does (APP_PATH_UNDER_COMPOSED_FOLDER).
  • Inside runas (…, onBehalfOf: person), a switched-off person has only the rights of a visitor who is not signed in, and a call into another kit's function is still checked against that person's rights.
  • runas (Actor, onBehalfOf: X) now warns (ON_BEHALF_OF_NOT_ATTESTED) unless X is a person the platform itself recorded: the signed-in caller (Session.CurrentUser), a row's [CreatedBy] or [CreatedFor] stamp, Records.CreatedBy(row), null, or a local variable set from one of these and never changed. A later release refuses it.
  • A package no longer chooses whose rights a [JudgedFor] function's writes are checked against: [JudgedFor] must name the row's [CreatedBy] stamp. A kit's own build (osy validate, osy package pack, osy publish) refuses a [JudgedFor] that names anything else. An app that already uses a published kit release written the old way (Osysharp.Invitations 2.0.1) still builds: it gets the warning JUDGEDFOR_NOT_STAMPED, which names the kit, and that kit's rows are checked as before. Update the kit (Invitations 2.1.0) to clear the warning. This is planned to become an error in 0.20.0.
  • Links an app builds for itself (App.BaseUrl, a page's canonical address, a mailed link) no longer follow an address a visitor sends in a header: only a zone's own gateway can set it, and the gateway no longer passes on one a caller sent.
  • An application's own sign-in can no longer read traces: every /api/trace route refuses it. osy trace start --full, which records the values every run held, needs a developer of the application.
  • Every download of an app's data — a backup, or a restored copy as rows or a dump — is now recorded (who, when, which app and environment, what kind, how big) and shown to the organization's Owners and Admins under Data downloads.

Organisation policy

  • An organisation's outbound-host policy now also holds an app's osy test runs (including [AllowNetwork] tests), its embeddings (OpenAI, Gemini, or a BaseUrl it names), its sign-in and connected-account calls to OAuth/OIDC providers, and the images its pages load. A refused host fails with the organisation's policy message, and nothing is sent. When the platform cannot read the organisation's policy, nothing is sent either; before, it could be.
  • Under an organisation that allows only some hosts, an app's pages load images only from the app itself, inline images, the app's declared browser hosts and the allowed hosts. External images on other hosts no longer load there.
  • A sign-in through a provider the organisation does not allow is refused before the visitor is sent to it: "Signing in with X is not available: …". An app no longer fetches signing keys from, or accepts bearer tokens issued by, an identity provider its organisation refuses.
  • Organisation policy now holds the app settings it governs: saving a value that a lock or range forbids is refused, and so is a bulk update or insert that would write one. An app with no governed setting pays nothing for the check.
  • When the policy refuses a write of a governed setting, the REST API answers 403 with the policy's sentence, and MCP denies it with that sentence.
  • A generated settings page shows the policy's sentence when a save is refused, and puts back the edits the person may not make.
  • A deploy whose migration would write a value your organisation's policy forbids for a governed setting (for example a backfill outside a bounded range, a backfill that reads along a reference or counts over a collection into a locked setting, or a copy into a locked setting) is refused before anything is written, on every deploy path including zone builds.
  • A new compile warning, ORG_POLICY_WRITTEN_AT_COMMIT, says when a package's governed field is one the platform writes itself at save (a [Counter] or a row stamp): the policy can refuse that save, but cannot choose the value.
  • osy import under a policy: when one batch of rows is refused, the files after it are no longer refused for that batch's rows.
  • /policy/draft and /policy/revert now require basedOnNumber (the comingNumber read from /policy/draft-state); a call without it is refused with the number to send. A policy version can no longer be saved or approved with an in-force date in the past.
  • Admin's policy catalogue now says where a governed app setting is enforced. It also says what is not yet covered: values stored before a lock or range are not changed to fit it.

Fixes

  • A page part whose live data depends on its parent's data no longer stays on its loading placeholder when the parent's data changes while it loads.
  • Adopting existing rows into a workflow whose state arms a timer or offers work no longer fails with "Object reference not set to an instance of an object".
  • A workflow whose Tracks names a row type from another namespace (through using) now works. Before, every new row failed with "'State' is required", and X.Start(run) did not compile.
  • An app entity or class may share a name with a platform entity (such as Counter); before, creating one in a test or a server function failed with "entity … not found".
  • A [Client] function or a public page action may now call pure built-in members such as a regex match's Groups[...]; before, they were refused as running on the server.
  • allow read via F now reads the stored value of a row handed to F as an argument, and of a row of a subtype of the entity, so a kit can check a field it hides from everyone; a member a subtype adds and hides stays hidden from F. F reads the same inside runas (Actor) { … } as outside.
  • After Delete() and UnitOfWork.Commit() (or Discard()), a deleted row is no longer reported as an unsaved change.
  • Deleting a row and creating its replacement with the same [Unique] value before one save now saves as a replacement; a real duplicate is still refused.
  • A migration line the deploy cannot carry out is refused before anything is written (MIGRATION_DATA_VERB_REFUSED): a member that does not exist, values moved between entities stored in different tables, a copy between two types, a copy between references to different entities, or a lambda that cannot run in the database. A copy from a reference into a Guid member copies the id the reference holds. A backfill lambda can read one hop along a reference: r => r.Team.Lead.
  • A [Test(F)] whose fixture does not compile reports the fixture's own error, not "unknown fixture".
  • A function that calls a helper that did not compile now says so (CALLEE_DID_NOT_COMPILE: "it calls 'X', which did not compile"), after the helper's own error, instead of calling it a gap in the compiler.

Performance

  • A commit that creates many rows with Markdown members no longer asks the database anything per row: in our measurement, 400 rows took 11 statements instead of about 10,900 and about 2 s instead of 15–26 s, and the cost now grows in step with the rows.

Platform and tools

  • osy validate and osy publish in a package's folder now say what the package reaches (outbound calls, secrets, browser code, scripts, the computer, native code), read from its own manifest and files; anything the reader does not recognise counts as reaching everything. The line only reports; it refuses nothing.
  • A package's entry in the package index now gives its use line with the grants its manifest asks for, for example in osy package search.
  • [CreatedFor] Guid? X; is a new row stamp: it records the person a row was made on behalf of. Inside runas (…, onBehalfOf: p) that is p; otherwise it is the signed-in caller. No code can write it. Records.CreatedBy(row) returns any row's stored [CreatedBy].
  • A Button's new busyLabel: "Saving…" shows your words in place of its label while its action works. A busy button is now marked aria-busy, and under reduced motion its spinner stands still.
  • The lint security-read-via-asks-about-one-row now also warns when a protected field of a row the function was handed or looked up is compared with a value from one of its parameters.
  • In osy test: a stub answering a click can call the real function, the test-only runas works inside such a stub, and Ui.HoldServer holds a page action's server call so that its busy state can be tested.

Admin

  • Slow actions show that they are working. A pressed button shows a spinner and its verb ("Deploying…", "Restoring…", "Approving…", "Saving…", "Making it available…"). A confirmation cannot be cancelled while its action runs, and after a second it says what is happening.
  • The organisation policy pages have a new look: the Policies, Versions and Approvals tabs open with a summary band. When two people approve at once, the Approvals tab shows the conflict.
  • Invitations sent before this release keep working: their sender is filled in from the invitation's inviter.
  • If a policy draft is open when this release is installed, approve or replace it before saving it again: until then, two people saving and approving it at once are not stopped.

Kits

  • New kit: Osysharp.Diff 1.0.0 shows a unified diff with changed-word highlights, unchanged runs folded (opened in place when you pass the whole old and new text) and a side-by-side view; all text is shown as plain text.
  • Agents 2.0.0 (see ⚠ above), with the agents family: Agents.Inspector and Agents.Management 3.0.0; Agents.HumanRequests, Agents.Processes, Agents.Teaching, Agents.Testing, Assignments.Agents, Privacy.Agents, Privacy.Agents.HumanRequests, Shop.Agents, WorkRepositories.Agents 2.0.0. An answer relayed from another request decides nothing, yes or no. Work tried again is for whoever the first work was for; work opened before 2.0.0, which records nobody, acts as the agent alone.
  • HumanRequests 1.6.0: each answer is recorded as a GivenAnswer made in the answerer's own request, and rolls up to its request.
  • Invitations 2.1.0: records who sent an invitation (SentBy) and checks what accepting it grants against that person's rights. If your app has pending invitations, add copy Osysharp.Invitations.Invitation.InvitedBy -> Osysharp.Invitations.Invitation.SentBy; to the migration of the same deploy that moves to 2.1.0.
  • Patch releases: Mail.Resend 0.2.1, Sms.FortySixElks 0.2.1 (they no longer write a grant for the package they use: it never took effect, and your app's grant is unchanged), Assignments.Allocations 1.3.1, Assignments.WorkQueues 1.3.1, HumanRequests.Processes 1.3.1.

The release on GitHub, with every asset and its SHA-256

osy 0.19.11 13 November 2026

This release fixes rows that could be lost when a page saved while other work was writing, a page that could show a person their old words after saving a Markdown text, background work on a zone that could not build the app's public address, and requests answered "nothing is routed here" while an app moved between runtimes. A call refused by an organisation's policy or its host lists now answers 403 with a short message. A commit that writes many Markdown documents is checked in time proportional to their number, and a runtime's first start throws far fewer exceptions. In Osyrin Cloud's Admin, a policy's outbound hosts are edited, compared and approved on the Policies tab. A few things that ran before now answer differently; each has its fix beside it. To upgrade, run osy upgrade, then osy update in a project.

Breaking changes

  • A call refused by your organisation answers 403, not 500. A call refused by the organisation's policy or by its two host lists in Admin answers 403 at a REST endpoint and a page call, and a tool error with code denied at an MCP tool, where it answered 500 or a generic error. This holds inside Parallel and a blocking wait too. In the app, a caught refusal's e.Type is PolicyRefused; a refusal by the host lists was InvalidOperationException. When another Parallel leg fails with a real fault beside the refusal, the caller gets the 403 and the fault is logged at Error with its stack. Who sees a difference: an app in an organisation whose host lists or policy refuse one of its outbound calls. Fix: test for PolicyRefused, or for 403, where you tested for InvalidOperationException or 500.
  • A refusal's message says less. What an app's catch, Http.Refusal and a signed-in caller receive says what was refused, that your organisation (or its policy) does not allow it, and the policy's reason. It no longer lists the organisation's allowed hosts, nor names the organisation, the policy's version, who set it or when, nor says how to change it. A caller with no account is told only "Operation not permitted.". The full sentence is written to the platform log under Osy.PolicyRefusal, at Warning, on release hosts too; identical refusals are written once and then counted per minute. Fix: read the platform log for the full sentence, not the message.
  • A page function paused inside a catch block cannot be resumed by an older release. After a rollback, or while an app moves between releases, such a pause fails and the person starts that step again. Fix: none needed.

Runtime

  • throw; works after a resume. After a page's call into the browser or a workflow wait, a throw; in a catch body rethrows what was caught; it answered 400 "throw; … ran with no exception in flight". A refusal kept across such a wait is still a refusal when the function resumes.

Fixes

  • Rows written while a page saves are no longer lost. A row that a stream or another flow wrote while a page's changes were being committed could be cleared without being written. It is now written by the next commit, keeping who wrote each column. A delete from another flow during a commit waits until the commit has finished, and a change the committing flow itself makes to a row it has just written goes into the next commit.
  • A page that saves a Markdown text and shows it again in the same session now shows the new text. Before, it could show the text as it was when the row was created.
  • A row with a Markdown text that is made, given its text and deleted in one call now leaves nothing. Before, it failed with a permission error about creating the text's sections.
  • Background work on a zone now sees the app's public address in App.BaseUrl. Scheduled jobs and workflow steps on a zone runtime read App.BaseUrl as the placement's public address. Before, it was built on nothing there, so mail links built in background work failed (for example, the notification kit's hourly digest).
  • A request that arrives while an app moves between runtimes now waits for the new runtime instead of being answered "nothing is routed here".
  • An app's first deploy on a zone no longer goes briefly unrouted before it is assigned.
  • A rare crash (exit 139) at a runtime's first start, while it compiled Osy#, no longer reproduces. The code that turns functions into browser code is split into smaller methods, and it no longer throws an exception for each function that cannot run in the browser.

Performance

  • A commit that writes many Markdown documents is checked in time proportional to their number. Before, the cost grew with the square of the number of documents.
  • A runtime's first start throws far fewer exceptions. Compiling an app no longer throws an exception for each function that cannot run in the browser, and checking a time-zone name no longer throws for an ordinary string.
  • Checking a large app allocates less memory. The checks walk each function body without allocating per node, look functions up by name in an index, and share one index of the app's entities between all its function bodies. On Admin, osy validate allocated about a fifth less.

Osyrin Cloud

  • Admin's policy editor. A policy's allowed and blocked outbound hosts can be edited, reviewed and saved as a draft on the Policies tab. The editor shows what a draft changes and the exact text its hash is taken over, compares your edits with a colleague's when they saved first, can save and approve in one step where you may approve, and sets the day a version comes into force; a day before today is refused. A save never replaces a draft someone else approved or saved meanwhile.
  • A version in force whose rules cannot be found is shown as in force. POST /organizations/policy/in-force gains rulesMissing and answers inForce: true for that version, where it answered inForce: false. Admin's Policies tab says the version is in force, its rules could not be read, and every outbound call of the organisation's applications is refused until a new version is approved.
  • Saving a policy draft names the draft it was based on. POST /organizations/policy/draft and /policy/revert take basedOnHash, the content hash of the open draft read before editing, and answer 409 if someone else changed the draft in the meantime; a basedOnRevision other than 0 without basedOnHash is a 400. A new read, POST /organizations/policy/draft-state, gives the open draft's state and its hash.
  • Changing how many approvals a policy version needs takes an optional was. POST /organizations/policy/approvals-needed answers 409 when the number has moved since then, or when two changes land at the same moment.
  • Admin's navigation rail runs the full height of the window at its left edge.

The release on GitHub, with every asset and its SHA-256

osy 0.19.9 13 November 2026

This release makes an app's settings obey its organisation's policy: a setting a package declares governed reads as the organisation's rule says, wherever the app reads it. It also fixes a page that could not load in a new browser after its cached tree was swept, and a settings page that read its change history once per field; and in Osyrin Cloud's Admin, setting a secret from the browser for a zone at another address, the warning a deploy token's deploy gave, and the Policy page. A few things that ran before now answer differently; each has its fix beside it. To upgrade, run osy upgrade, then osy update in a project.

Breaking changes

  • A governed setting reads as the organisation's policy says. App.Setting<T>() now applies the rules of the organisation's policy version in force to every member a package declares with [OrgPolicy], for the package's code and the app's code alike: a lock gives the organisation's value whatever the app assigns, a range holds the app's value to its bounds, and a default gives the organisation's value where the app's source does not assign the member. A new policy version binds from the next request; a later version without the rule gives the app's own value back. Who sees a difference: an app that composes a package with [OrgPolicy] members (for example the user-accounts kit's sign-up switch and minimum password length) in an organisation whose policy sets one of them. With no policy in force, or a policy that names none of the app's settings, the app reads its own values as before. Fix: none needed; to change a governed value, change the organisation's policy, not the app.
  • A governed setting that cannot be read is refused, not guessed. When the policy in force sets a lock or a range the server cannot read (its rules are missing, or the organisation's answer cannot be had), the read fails with a policy refusal that names the setting ("The setting … is refused: …"); it never falls back to the app's value or the package's default. A default that cannot be read is ignored. Who can be newly refused: an app reading a governed setting while its organisation's policy cannot be read. Fix: none in the app; once the organisation's policy can be read again (an operator's step), read again.
  • A value worked out from a governed setting is kept for one request only. A setting your app computes from a class that has a governed member is worked out again for each request instead of being kept across requests, so it follows the policy. Values that read no governed class are kept as before. Who sees a difference: an app whose worked-out setting is costly to compute; work outside a request (a worker, a workflow step, a scheduled job) works it out at every read. Fix: none needed; to keep a costly value, work it out from a class with no governed member.

Organisation policy

  • The policy is read once per request. The first read of a governed setting in a request asks for the organisation's answer; later reads in that request use it. A single server reads the policy again when it is changed there, on a version's start date, and otherwise every 30 seconds; a zone answers from the latest description of the zone it holds.
  • On a zone, an app the zone's description does not cover is refused a locked or ranged setting. When the zone's description does not say what the app's organisation's policy is (no description yet, the app not in it, or its organisation not described), a setting a package declares with a lock or a range cannot be read and is refused, even when the organisation has no policy.
  • A registry that cannot be reached. A server whose last answer was "no version in force" keeps serving that answer, with one warning per outage; any other last answer, or none, refuses as above.

Fixes

  • A page loads in a fresh browser after its cached tree was swept. A page's tree is again served to a browser that does not hold it yet after the server's cache sweep dropped the tree's entry while the page stayed in use; before, such a browser got "not found" for the tree until the app was deployed again.
  • A settings page asks for its change history once. A page that shows a row's change history next to several of its fields reads that history in one statement again, where it read it once per field.

Osyrin Cloud

  • A secret can be set from Admin for an app on a zone at another address. Admin's Secrets page could not send a value to a zone whose gateway has an address of its own: the browser refused the request before it left. It now can. When a set fails, the form says so on the spot, says "Nothing was changed" where that is true, and asks for the value again.
  • A deploy by an app's deploy token no longer warns that a set secret has no value. The deploy now sees which of the app's secrets a person has already set, and warns only of the ones nobody has.
  • Admin's Policy page. An organisation's policy is managed on one page with three tabs: Policies (what is in force, what the rules are), Versions (each version and its approvals, approving a draft, and starting a new draft from a replaced version), and Approvals (how many approvals a version needs, and whether machine accounts may approve; a machine account can change neither).
  • Admin's pages in the new look. Admin's tables stack into one column on a phone, and a card no longer clips a menu or a hover title that leaves it.

The release on GitHub, with every asset and its SHA-256

osy 0.19.8 12 November 2026

This release makes a zone refuse every outbound call of an organisation's apps when the organisation's policy version in force cannot be read, as a single server already does, and fixes how a list of rows is passed to a function, how the browser divides a whole number by a decimal, which edits wake a live read of a Markdown text, and what a recorded trace keeps. A few things that ran before now answer differently; each has its fix beside it. To upgrade, run osy upgrade, then osy update in a project.

Breaking changes

  • A list of rows passed to a function names only rows the caller can read. A function parameter that is a List<T> or a HashSet<T> of a stored entity now looks up each id it is sent the way a single T parameter does. An id that names no row, or a row the caller may not read, answers Not Found (404), naming the element (for example items[1]) and nothing of the row, and the function does not run. Before, such an id was passed in as an empty row, or the call failed with a server error. A value that is not a JSON array is refused as invalid. Who can be newly refused: a caller that sends ids of deleted rows, or of rows it cannot read. Fix: send only ids the caller can read, or drop the ones that answer Not Found and call again.
  • A Markdown tool's own error is an error. An MCP markdown_* tool that cannot carry out a request (an anchor that is not there, a missing argument) now answers as a failed tool call (isError), not as a successful one whose text is the error. Who sees a difference: an MCP client that read the error out of a successful call's text. Fix: treat a call answered with isError as failed and read its message from that call's text.
  • [OrgPolicy] declarations are checked when an app is compiled. A setting key declared by two packages, a field given two modes, and a governed field a setting class inherits from its base class are refused. Fix: compose only one of the two packages, or rename the type in one of them; give the field one mode, in its declaring package's [OrgPolicy(OrgPolicyMode.…)]; move an inherited field and its attribute into the setting class itself, or take [OrgPolicy] off it. An [OrgPolicy] in an app's own source, or in composed source whose file names no package, is a warning: it is not a control. Nothing reads an organisation's value for a setting in this release.
  • Function names starting __OrgPolicy_ or __OrgPolicyAssigned_ are reserved. The compiler makes functions under these names for a package's [OrgPolicy] fields, so a function of yours named so is refused as a reserved name. Fix: rename it.
  • A whole number divided by a decimal gives the decimal in the browser too. Arithmetic of a long with a double in a page (for example bytes / 1024.0) now gives the fraction, as the server always did: 9.8, where the browser showed 9. Arithmetic of two whole numbers, and comparisons, are unchanged. Who sees a difference: a page that shows such a value. Fix: none needed; to keep the whole number, round it (Math.Floor) or divide by a whole number.

Organisation policy

  • A zone refuses when the policy in force cannot be read. When an organisation's policy version in force has lost the revision it approved, every outbound call of the organisation's apps on a zone is refused with the sentence a single server gives ("…its rules cannot be found. Until it can, every outbound call of the organization's apps is refused — nothing was sent."). Before, the zone read such an organisation as having no policy, and the organisation's allowed and blocked hosts decided.
  • Upgrade in this order: the control plane, then each zone's agent, then the zone's apps. The refusal holds only when all three run this release. Until then a zone decides as it did before, by the organisation's two host lists; nothing is less safe than before in any order.
  • A zone's app restarted on a different release than its zone's agent waits for the agent. It drops the copy of the zone's description it kept on disk and holds none until the agent next hands it one.

Fixes

  • A live read of a Markdown text wakes only for its own row. A live var that reads a Markdown member's text is asked again when that row's text is edited, and no longer when another row's document is edited. Docs
  • A recorded trace does not keep credentials. A run's recorded trace, as osy inspect --fault prints a failing one, no longer holds a key or token the run issued (Security.NewApiKey, RandomId, RandomHex, IssueJwt, a test's Api.KeyFor/TokenFor), a value written to a member a deny read rule guards, or a pk_ key or JWT by its shape; each is masked. Docs
  • A policy's parameter type is read where the policy is written. Asking a policy from a file that does not import the type of the policy's parameter no longer fails to compile.

The release on GitHub, with every asset and its SHA-256

osy 0.19.7 12 November 2026

This release makes the rules on outbound hosts cover the Host header of a call as well as its address, refuses a request header that carries a line break or another control character, and lets an organisation keep an outbound host for one package. A few things that passed before are now refused; each has its fix beside it. To upgrade, run osy upgrade, then osy update in a project.

Breaking changes

  • A Host header that names another host must pass the same rules as the address. An outbound call (Http.Get/Post/Put/Patch/Delete, Http.Stream, Http.StreamEvents, Http.GetToFile, Http.PutFile, Http.PostToSecrets) that sets a Host header different from the host in its URL is sent only if the named host passes too: the organisation's blocked and allowed hosts, the app's own rules and, for a package, the hosts the app granted it. Before, only the URL's host was checked. The two hosts are compared by the name a host resolves as, so a Host header equal to the URL's host (in any case, with a trailing dot, in its Unicode or xn-- form, with a port) changes nothing, and an app with no host rules in an organisation with none may still set a different one. Who can be newly refused: an app or a kit that sets a Host header different from its URL's host while its rules do not allow the named host. Fix: allow the named host as well, or stop setting the header.
  • A request header with a line break or another control character is refused. A header whose name or value contains a line break or another control character is refused and nothing is sent. A tab, and text outside ASCII, are treated as before. Fix: remove the character from the value before the call.
  • More than one Host header, an empty one, or one that is not a host is refused, whatever rules are set. A Host header is a host name or an address, with or without :port. The refusal says what was wrong and does not repeat the value. Fix: set one Host header, holding a host, or none.
  • A secret goes only where its secretIn line allows, the Host header included. When a call that sends a secret in a query parameter or body field names a different host in its Host header, the secret's line must cover the named host as well as the URL's host. Fix: declare the secret for the named host too, or stop setting the header.
  • A Host header counts against a rate limit. The host named in a Host header counts against that host's per-minute rule as well as the URL's. Fix: none needed unless the named host's limit is reached; then raise it or send fewer calls.
  • A stored rule with an asterisk that is not the plain * matches nothing. A rule already stored as *.example.com or ﹡.example.com (full-width or small asterisk) is no longer read as a wildcard: as an allow it allows no host, and as a block it blocks none. Such a rule has been refused when set since 0.19.6. Fix: rewrite a rule stored earlier with the plain *. This replaces 0.19.6's "one already stored is compared as the wildcard".

Fixes

  • The .egress file check refuses what the server refuses. A non-plain asterisk, a second * behind the *. prefix and a name over 253 characters are reported by the file's own check, in osy compile, osy egress and a deploy, instead of the server rejecting the rules afterwards.

Organisation policy

  • A host for one package. An organisation's egress.hosts rule can name a host for one package: [email protected]. Only code of the package named so reaches that host, from the server, and only where the app grants the package the host. The app's own code and every other package are refused it, also when they name the host in a Host header.
  • The name is all that is checked. The package is matched by its full name, exactly. An app that composes its own package under that name reaches the host.
  • What counts as the package's code. Code of the app that the package calls back into is the app's and is refused the host. A function of the package that sends to an address its caller hands it still sends as the package, so the app reaches the host through such a function. A workflow the package declares is the package's code and reaches the host.
  • Such a host is never added to a page's policy by a grant. A browser grant that covers it is dropped for every package, the named one included.
  • Such a host is not an allowed host. It does not by itself limit the organisation's apps to a list. A blocked host stays blocked for the named package too, and -host@Package is not accepted.
  • Two packages. The same host named for two packages is accepted, and both reach it. Two different patterns that cover the same host and name different packages are refused when the policy is saved.
  • Upgrade the platform first. Every platform that runs the organisation's apps must have this release before a version with such an entry is approved. An older platform cannot read the entry and refuses every outbound call of the organisation's apps until it can.
  • GET /api/egress says more. The answer gains onlyVia, the hosts kept for one package with the package's name. Each package grant gains onlyThrough, the packages its host is kept for when that is why it is refused, and why on a browser grant that is not admitted because it covers such a host. A caught PolicyRefused gains OnlyThrough, which is empty when the entries shut the host to everyone.
  • A machine account is told by its address as well as its registration. An account at the machine accounts' address that is not registered as a machine is now refused approving a policy while the organisation does not let machines approve. Before, it approved as a person. While machines may approve, its approval is recorded as a machine's and stops counting when machines are turned off.

Not covered

  • X-Forwarded-Host, Forwarded, X-Host and X-Original-Host are passed on unchanged and are not checked against the rules. The port in a Host header is not checked.

The release on GitHub, with every asset and its SHA-256

osy 0.19.6 12 November 2026

This release makes the rules on outbound hosts hold however a host's name is spelled, stops an ordering from revealing a value you may not read, and lets an organisation keep its outbound hosts as a versioned policy. One thing that passed before is now refused: an allow written exactly *.. To upgrade, run osy upgrade, then osy update in a project.

Breaking changes

  • A blocked outbound host is blocked under every spelling of its name. Host rules are now compared by the name a host resolves as: case, a trailing dot (also the ideographic and full-width dots 。 . 。), the Unicode and xn-- forms of one name, and compatibility characters (full-width letters, ſ for s). A call to a blocked host written one of those ways used to pass the block; it is refused now, from your app's code, from a kit and in Http.Refusal. A block that was itself written with a trailing dot or in Unicode now applies to the name written plainly. Nothing to change in an app: a name written plainly against a rule written plainly is decided exactly as before.
  • An allow written exactly *. matches nothing. An asterisk, a dot and nothing after used to allow every host called with a trailing dot. It now allows none. This is the one case where a call that no block was meant to stop is newly refused. Fix: write the hosts you mean, such as *.example.com.
  • A rate limit on a host counts every spelling. A call to a rate-limited host written with a trailing dot or as its Unicode or xn-- twin counts against the rule's limit.
  • A rule with an asterisk that is not the plain * is refused when it is set. *.example.com (full-width or small asterisk) in a deploy's rules is refused; one already stored is compared as the wildcard.
  • Ordering by a member you may not read no longer reveals its order. $orderby in REST, the MCP query tools and the context endpoint used to place a row by a value that a deny read hides from the caller. Rows whose value is hidden from the caller now stand together, in id order. An order on a field no rule hides is unchanged. Docs

Fixes

  • A host you allowed is allowed under every spelling. A host on an allow list (your app's or your organisation's), a package's granted host and the declared host of a secret are matched by the name they resolve to, in any of the spellings above. Blocks and the organisation's list still decide after.
  • GET /api/egress says when an organisation's policy decides. It names the policy version the organisation's rules came from, and says when every outbound call is refused because that version's hosts cannot be read.

Organisation policy (REST only, no page yet)

  • An organisation can keep a policy in versions. Its Owner and Admin save a draft, approve it and revert to an earlier version through the REST API of Admin, and anyone in the organisation can read the version in force. The routes, all POST: /organizations/policy/draft, /organizations/policy/approve, /organizations/policy/revert, /organizations/policy/in-force, /organizations/policy/approvals-needed and /organizations/policy/machines-may-approve. A platform operator can read a policy and cannot save or approve one.
  • Approvals. An organisation sets how many approvals a version needs; only an Owner lowers the number, and only an Owner decides whether a machine account may approve.
  • Outbound hosts from the policy. A version's egress.hosts rule is the organisation's list of outbound hosts for its apps once that version is in force. An entry that is a pasted address is refused at the save, with the host to write instead. An organisation with no policy version, or a version without that rule, keeps its allowed and blocked hosts in Admin as before.

Kits

  • MarkdownEditor 1.2.1. A pending save goes out when the editor is closed, so text typed just before a drawer closes or a link is followed is no longer lost, and "dirty" is raised on every change of state.

The release on GitHub, with every asset and its SHA-256

osy 0.19.5 12 November 2026

This release makes the kits follow your app's own rules, and closes the audit trail unless you open it. A few things that passed before are now refused; each has its fix beside it. To upgrade, run osy upgrade, then osy update in a project. Take UserManagement 0.11.0, Invitations 2.0.1 and Organizations 0.8.0 together with it.

Breaking changes

  • Your app's deny on a kit's rows now binds the kit. A deny your app writes on a kit entity such as RoleGrant or MembershipRole holds on every route the kit offers: giving and taking a role, adding an integration, accepting an invitation, removing a member. A refused change is recorded as refused and the caller is told with your rule's own message. Fix: if a kit route should pass, narrow your rule's where, or give the role through your own function. It takes effect at your app's next compile. Docs
  • An invitation's role is judged for the person who sent it. When an invitation is accepted, your rules are checked against the inviter as they stand at that moment. An inviter who has since lost the standing, or whose account is switched off, no longer gives the role: the invitation is refused at the door and nothing lands. Fix: send a new invitation. Docs
  • An audit trail nobody was given the read of is read by nobody. An app that keeps a trail and reads it in a function, on a page or over GET …/entities/<E>/{id}/audit with no Read declared for that surface now gets no rows (REST answers 403 naming the line to add). Fix: app.Audit = new AuditConfig { EntityAuditRecord = new AuditSurface { Read = user => <who> } };. <Entity>.Changes(id) answers only for a row the caller may read. Docs
  • A field with a deny read is not written to the change trail. It is recorded as changed, with its value redacted on both sides, in your app and in every kit you use. Rows recorded before this version keep the values they hold. Docs
  • MCP refusals are errors. get_ of a row that is missing or that the caller may not read now answers an error with the code not-found; a bad id or a missing argument is invalid. Every refusal carries its code in _meta["osy/error"]. Fix: a client that read the text of a "not found" answer as a success checks isError. Docs

Fixes

  • MCP tools that answer a row work on a fresh host. query_, get_ and update_ could fail with a serializer error until some other call had run. A write now produces its answer before it commits, so a failed answer writes nothing.
  • watch over MCP no longer fails when entity_type is left out, and knows the entities of typed catalogs.
  • Removing a member is refused whole. When your app's rule forbids taking a role away, the Organizations kit's removal is recorded as refused, takes back what it had done, and says your rule's message.
  • A resent invitation starts its time over. It used to lapse on the first send's clock.

Language

  • Short entity names in REST and MCP. The full name always works. The short name works when exactly one entity that surface exposes has it: /entities/Product, query_Product. Listings (tools/list, openapi.json) show the short name when it is unique. If a later version adds a second entity with the same short name, the short name is refused and the full name keeps working. Docs
  • [JudgedFor] for kit authors. A kit function can have the app's rules judged for a person a row of its own names, such as an invitation's sender. Docs

Kits

  • UserManagement 0.11.0. Everything from 0.10.0 is still there. AddIntegration("Relay") makes an integration that holds no role until your app gives it one through its own route. The person drawer keeps its two destructive actions together, each asking first, and "Add role" shows every role with the held ones marked. API keys, integrations and access changes are tables. An app places any kit settings section in its own group and order. Docs
  • Invitations 2.0.1 and Organizations 0.8.0 carry the changes above.
  • Also released: Dns 0.3.0 and Ui 3.3.0.

The release on GitHub, with every asset and its SHA-256

osy 0.19.4 12 November 2026

This release closes several places where a deploy or a policy could give a wrong answer without saying so. Some things that passed before are now refused, each with the fix beside it, so read the breaking changes first. To upgrade, run osy upgrade, then osy update in a project to take the new kit releases.

Breaking changes

  • A deploy that would change what stored enum values mean is refused. A row stores an enum member's value, and a move rewrites no row. When a column's enum moves to another namespace, is renamed or is swapped for another, every stored value must still name the same member. Reordered or renumbered members are refused with ENUM_RETARGET_CHANGES_STORED_VALUES, naming the column and each value that would change. Fix: keep the old order in the new enum and add new members at the end, or give a member its old value (Parked = 1). Docs
  • The security lint reads more rows, and osy check fails on what it finds. The rule for organization rows open to every account (TENANT_ROWS_OPEN_TO_EVERY_ACCOUNT) now judges rows declared in your app's own packages, and rows that reach their organization through required references, such as a card on a board that belongs to a team. osy validate prints a warning. osy check fails. Fix: add the where the finding prints, for example where IsMemberOf(Board.Team). Docs
  • Policy forms that cannot answer the same everywhere are compile errors. A class value or a list passed to a policy from code is refused at the call. Fix: declare the parameter as the single value the body compares, and ask once per value. An enum's .Label or .Description in a policy or rule is refused, because both are translated for the reader. Fix: compare the member, its .Name or its .Value. Docs
  • A token with no address is refused. A command given OSYRIN_TOKEN or OSYRIN_ADMIN_TOKEN takes its server only from --server or the project's osyrin.json. With neither it stops before sending anything, where it used to fall back to the server you were signed in to. Fix: pass --server <url> in CI, or link the project. Docs
  • Your app grants every package that asks for authority, by name. Code in a package uses only what your app granted that package. A package that arrives through another one and needs a host, a secret or a client certificate is no longer covered by the package that brings it. The compile stops and prints the use line to write. Fix: add that line. Docs
  • A run-time error in a UI action fails its test. An index out of range, a null, a failed cast or a divide by zero in an action now fails the test at that step, under osy test and osy test --pixels. Fix: correct the action. A throw your app wrote and a refusal from the server are still outcomes a test can assert. Docs
  • osy cancel-runs asks how many runs you mean to end. A version with live runs needs --cancel-live <N>, where N is the number osy versions shows. --yes does not stand in for it. Docs
  • New warnings. THEME_MODE_MAP_WITHOUT_LIGHT when a theme token names a variant and no light value. PACKAGE_PAGE_FUNCTIONS_KEPT when a package page you left out still has callable functions behind it. A warning for a [Test] that queries the run tables directly. osy lint also has four new workflow rules, one of them workflow-zero-seats-beside-a-plain-wait.

Fixes

  • A policy called from code gets its arguments. Called from a function, a test or a workflow with an enum member, a string, a number, a bool or a date, a policy used to answer no for everyone on a clean compile. It now answers what a rule making the same call answers. A policy that derives a value from its argument (d.Name, "Duty." + d, k.ToUpper()) answers alike in a rule, a where and from code. Docs
  • A migration can retire a whole enum that has a namespace. drop enum Shop.Orders.JobStatus; is accepted as the deploy's refusal prints it, including for an enum that only moved namespace. A short name is refused with the reason. A line that could mean both a type and a member is refused, naming both. Docs
  • validate, lint and test make no network request when the lock resolves. That includes a workspace package with no lock of its own, which is now checked against its app's osyrin.lock. A loop of checks no longer spends a GitHub token's hourly limit. Docs
  • Workflow versions follow what changed. Editing the body of a namespaced function a workflow calls now makes a new version, so a run parked mid-body finishes on the body it started with. Moving a workflow further down its file no longer makes a new revision.
  • Parked runs keep up with a deploy. An in-place deploy that changes a workflow moves the runs still on its previous revision, with their clocks and waits. A wait the new version adds to a state is armed on runs already parked there. A deploy that keeps a fan-out no longer strands the runs parked on it. Docs
  • A child run is started by the principal you would expect. The innermost open runas block starts it, in every kind of body and in background work. Docs
  • Smaller fixes. A conditional Autostart over a base type no longer fails the commit of a subtype row. A field left out of a class argument keeps its declared default. A member made [Searchable] on an existing table gets its search column in the deploy. A workflow raise inside a try is held until the block completes. The first person to sign up is the app's Admin even when the app declares actors. osy status shows an app that serves no version yet. osy compile --json keeps its output clean JSON. Kit and database downloads retry a failed request.
  • Your local data stays. Starting a local platform no longer deletes the stopped platform of a project you still have. Only osy instances --prune does. Docs

Language

  • A workflow in several files. The root workflow W { … } lists every state and writes state Building; for a body kept elsewhere. A partial workflow W { state Building { … } } in another file gives that body. The split workflow is the same revision as its one-file form, so running workflows do not notice the move. Docs
  • Start a run by name. <Workflow>.Start(row) starts one run for a row whatever Autostart says, and <Workflow>.StartAgain(row) gives a row whose run has ended a new one. <Workflow>.Version is the app version the code runs in. Docs
  • A policy takes any single value. An enum member, a string, a number, a bool, a date, or a nullable one, beside rows and ids. Docs
  • A stream<T> REST endpoint answers server-sent events. Each yield return is sent as it happens, with open, item, done and error events. Docs
  • MCP tool failures carry stable codes. A failed call says why in _meta["osy/error"]: denied, not-found, invalid, conflict, unavailable, too-many-attempts or fault, and a refused workflow step adds a reason such as not-holder. Docs

Tooling

  • osy migrate prove. Proves a workflow migration before it ships. It parks a run in every state of the old version on a throwaway local platform, deploys the new version with your .migration, and reports each state as moved, ended, refused, lost or in the wrong state. It exits 1 when any state failed. Docs
  • osy deploy shows each stage and waits on the platform's word. Dry run, backup, build and migrate, and roll out are printed with their times, and a failure names its stage. The deploy succeeds when the platform says the version is served. A separate line says whether the app's address answers with it. --wait sets how long to wait (45 minutes by default). Exit codes: 0 served, 1 refused or failed, 2 the wait ended and the deploy goes on. It also refuses before building when the environment runs a release older than what your app calls. Docs
  • osy query names your app's functions and workflows. osy query "CountOpen()" runs the deployed body. A function that writes is refused. Docs
  • A local platform that stays up. --keepalive 0 turns the idle stop off, and an open page keeps its local platform running however long you only watch. Docs
  • The layout check. layout "Acme.Shop"; in the manifest turns on a check that each model file opens with the namespace its folders spell and is named after a declaration in it. Opt in; without the line nothing is checked. Docs
  • Tests say more. osy test --announce prints a line as each test starts, so a hang names its test. Cost.RequestPathsSince(mark) and Cost.StatementLinesSince(mark) say which requests and which lines a step's cost came from. A test that lost a brace is one error that names what it swallowed. Docs

UI kit

  • Six status tones. Tone.Info and Tone.Waiting join the others on Badge, Lamp and nav badges, with a filled pill. Badge(size: Size.Sm) is a count pill and Tab(count:) draws it. Docs
  • Link tabs and a native select. Tab(to:) is a tab that is a link. Select, Option and the kit's SelectField give you the browser's own select. Bullets and Bullet draw a list with markers. Docs
  • Declared settings do more. A [Settings] section can save only through a function you name (Writer), open a review of the changes before saving (Save = Review), hold a list of rows edited in a drawer, be kept per site or team with a chooser, and say where each value comes from. Docs
  • Forms line up. The kit's form parts sit on one grid, so fields in the same column have the same width.

Kits

  • UserManagement 0.10.0. AddIntegration(name, role, organization: company) adds an integration whose role is held in one organization and nowhere else: an API key for one customer or one team. MayInvite may now read a table, such as permissions kept as rows. Write PeopleManager() and the page asks the server who may invite. Docs
  • HumanRequests 1.5.0. An option says what happens, what speaks for and against it, and who acts. A request can carry a recommended option with its reason, taken with AcceptRecommendation. A new kind, OwnerStep, asks a person to do one step and answer Done. Docs
  • Memory 2.1.0. Memory.ByMeaning() tells a page whether search by meaning is on, or running on words alone. Docs
  • The UI kit changes above come with osy 0.19.4 itself (the Ui kit it carries). Ui.Looks 0.5.0 gives every look its Info and Waiting colours.
  • Also released: KnowledgeBase 1.3.0, Notifications 1.4.0, and the ten Shop.Looks kits at 0.5.0.

The release on GitHub, with every asset and its SHA-256