Skip to content
Romy

Releases

A release is called Romy YY.MM.n with a codename and moves through three channels, from Internal through Beta to Stable. Every move has fixed thresholds and fixed times, and a person gives the Go.

Who it is for

For your Intune and Teams admins who install new versions, and for anyone who wants to know when something changes.

Why this page exists

So you can follow which version is where right now, by which rules it moves on, and how to check every file. A new release never arrives unannounced.

How to install a new release is in Setup, step 11.

The three channels

You pick a channel and get every release that arrives there. Today the channels apply to the Romy App for Windows, the Teams package and the Intune setup. The service itself, with platform, Diagnostics and Teams bot, always runs the newest version.

Stable

Romy 26.10.4 „Arber“

since 15.10.2026

The default for customers. A release moves here on Tuesdays and Thursdays at 10:00.

Beta

Romy 26.10.4 „Arber“

since 15.10.2026

For customers who want to test earlier. A release moves here on weekdays at 10:00 if it meets the thresholds.

Internal

Romy 26.10.4 „Arber“

since 14.10.2026

The newest cut. It runs at Romy itself and on two test devices first.

What is in each channel right now

Pick a channel. You see every product with its version, file, size and SHA-256. One release covers all products at once.

Romy 26.10.4 „Arber“ · stabil · 15.10.2026

Tag romy/26.10.4 · Romy App dcdee5f9b956

Three files, in the order you set them up. Each card says who needs it and where the step is explained.

  1. 1 / 3

    Romy Intune setup (RBAC)

    For whom

    • Intune adminruns the scripts

    This is where you decide who may deploy Romy and which devices it reaches. Four PowerShell scripts do the work without a secret, and -WhatIf shows you first what would happen.

    After you install

    1. 1The groups “Romy Pilot Devices” and “Romy Intune Admins” are in Entra ID.
    2. 2The role “Romy App Installer” with 5 permissions covers the pilot devices only.
    3. 3Next, script 2 uploads the Romy App.
    The four scripts in the package
    • 1-gruppen-und-rolle.ps1 creates the groups, the scope tag ROMY and the role “Romy App Installer”.
    • 2-romy-app-hochladen.ps1 uploads or updates the Romy App for Windows and assigns it to the pilot devices.
    • 3-teams-app.ps1 (optional) publishes or updates Romy on Teams in your org catalog.
    • 4-dienstkonto-rolle.ps1 (optional) creates the role “Romy Geräteaktionen” for a Romy service account.
    • Instructions in German and English are included.
    Download· 18.1 KB

    romy-intune-einrichtung-26.10.4.zip

    Romy 26.10.4 „Arber“ · stabil · 15.10.2026

    SHA-256 checksum
    35fb9808c882f41d6e71a819c65fb1155863eb366b92f0f50e1136475ae2d36d
  2. 2 / 3

    Romy App for Windows

    For whom

    • Intune admindeploys the app
    • Employeeshave it on their device

    The Romy App lets Romy help right on the device. It only reads when someone asks and only acts when the person confirms.

    After you install

    1. 1Intune brings the app to the pilot devices within an hour.
    2. 2The device shows the notice page “What Romy does on this device”.
    3. 3Romy operations approves the device, and Romy can help there.
    Download· 110 KB

    romy-app-26.10.4.intunewin

    Romy 26.10.4 „Arber“ · stabil · 15.10.2026

    SHA-256 checksum
    57f19216009bc33f2221e2296a3ea8c31bec70280f0cbe06dc290f0b36ee0f4d
  3. 3 / 3

    Romy on Teams

    For whom

    • Teams adminuploads the package
    • Employeessee Romy in Teams

    Teams is where your people ask their questions, right where they already work. Romy reaches the pilot group first, and you decide when more people see it.

    After you install

    1. 1Romy is in your org catalog, for the pilot group only at first.
    2. 2Pilot users find Romy in Teams under Apps → “Built for your org”.
    3. 3They message Romy and confirm every action themselves.
    Download· 32.5 KB

    romy-teams-26.10.4.zip

    Romy 26.10.4 „Arber“ · stabil · 15.10.2026

    SHA-256 checksum
    91527bd75e011eab164d2bad17b333cf75cee6493e66deb4761d27be2ed5f0ad
These parts run at Romy, there is nothing to install.Romy Platform 26.10.4Romy Diagnostics 26.10.4Romy Engage 26.10.4

How a release reaches you

What arrives, when it arrives, how you find out, what you do and how you roll back.

How a release reaches you
  1. 1InternalWe test every new version ourselves first.Nothing changes on your side.
  2. 2BetaFor customers who want to test earlier.After one day at the earliest, weekdays at 10:00.
  3. 3StableYour default. This is what customers get.Two days after Beta at the earliest, Tuesdays and Thursdays at 10:00.
  4. 4Your devicesYour Intune admin installs it.Whenever you want. Nothing arrives by itself.

How do I find out?

Every new release appears on the Releases page, with every file and its SHA-256. No release arrives unannounced.

To the files

What do I do?

Your Intune admin uploads the new Romy App. If the Teams package is new, your Teams admin uploads that too. It takes about 10 minutes.

Setup, step 11

How do I see it has arrived?

Ask Romy in Teams “Which version are you?”. The answer names the version on your device.

How do I roll back?

Upload the previous version from the Releases page again. Romy takes a faulty release out of the channel within one hour.

Freeze and rollback

How we approve a release

A release only moves on if it meets every condition. If a measurement is missing, it does not move, and the condition stays as it is. A person at Romy approves every move.

From Internal to Beta

Monday to Friday, 10:00 Berlin

  • ≥ 24 hThe release ran at Romy for at least a day.
  • ≥ 3Every device check ran without errors at least three times on both test devices, with exactly this Romy App.
  • ≥ 95 %At least 95 percent of our chat tests passed.
  • 0In those tests Romy did nothing it was not allowed to do.
  • ✓Every device check is monitored and raises an alert if something fails.

From Beta to Stable

Tuesday and Thursday, 10:00 Berlin

  • ≥ 48 hThe release ran in Beta for at least two days.
  • ≥ 5Since Beta, every device check ran without errors at least five times on each device.
  • ≥In Beta, Romy solves problems at least as often as internally at Romy.

Upcoming cuts

These are the times when the numbers are checked. Whether a release moves is up to the thresholds.

  1. —

Who does what in a release

WhoWhatWhyWith which permission
Romy, automaticallyBuilds the Romy App, Teams package and Intune setup from every new version and writes the SHA-256 for each file.So you can verify every file.Our own code only. No access to Azure, no secret.
Romy, automaticallyChecks every condition at each date at 10:00 and proposes the move when all are met.So measurements decide, not gut feeling.Reads our measurements only.
Romy operationsApproves the move.So a person owns every move.May change the channels.
Your Intune adminUploads the new release (step 5).You decide when it reaches your devices.Role “Romy App Installer”.
Your Teams adminUpdates the Teams package when it is new (step 7).It carries the same number as the app.Teams Administrator.

Freeze and rollback

2 h

Freeze

Anything built in the two hours before a cut does not move with it. The only exception is a fix that is explicitly marked as one.

≤ 1 h

Rollback

Romy brings back the channel’s previous version, and a version that was taken back never re-enters that channel. The fault is fixed internally and the 24-hour clock starts again.

1 channel

per customer

Romy itself is on Internal. Customers are on Stable, or on Beta if they ask. You choose the channel and never a single version.

Changelog

Every cut with its date, Romy App version and Teams version. As soon as a release moves to Beta or Stable, it appears here.

  1. Romy 26.10.4 „Arber“

    14.10.2026 · in Beta and Stable since 15.10.2026Romy App dcdee5f9b956 · Teams 26.10.4
    • FixedRe-installing through Intune now reaches the device even if the Romy App was installed before.
    • NewOne admin bundle per release for all customers, with Intune setup under RBAC, Teams package and checksums.
  2. Romy 26.10.3 „Arber“

    14.10.2026 · InternalRomy App dcdee5f9b956 · Teams 26.10.3
    • NewReleases carry a name. Romy answers “Which version are you?” in the chat, for the service and for your device.
    • NewThe diagnosis result arrives as a card in portal and Teams, and Teams shows that Romy is typing.
    • ImprovedThe chat names your organisation and always serves the asking person’s organisation.
    • FixedThe install status now looks for the Romy App specifically instead of the first app in the list.
  3. Romy 26.10.2 „Arber“

    13.10.2026 · InternalRomy App acd509c28b08 · Teams 0.1.2
    • NewDevice diagnosis, wave 1. Health, management (Entra, Intune, BitLocker, Defender), network, updates, certificates and drivers, confirmed by card in the chat.
  4. Romy 26.10.1 „Arber“

    12.10.2026 · InternalRomy App 1e7c7bd2f020 · Teams 0.1.2
    • NewThe first cut with a receipt. Every file has a SHA-256, plus the Intune package and RBAC template.