Présentation de AIS Runner
live20 versions

AIS Runner — notes de version

Chaque version publiée de AIS Runner, de la plus récente à la plus ancienne, avec ce qui a changé — écrit au moment de la release, pas reconstitué après coup. Les notes elles-mêmes sont publiées en anglais.

Exécutez et testez vos Azure Logic Apps en local sans déployer sur Azure. Démarrage Azurite + func en un clic, historique d'exécutions en direct, barre d'analyse des workflows, comptage des files Service Bus, vue CI/CD DevOps, testeur de templates Liquid et graphe des chaînes de workflows — le tout dans une seule app de bureau.

Version actuelle

Version 0.5.50, publiée le 8 septembre 2026. C’est celle qu’installent les boutons de téléchargement ci-dessous.

Changed

  • Sample projects and screenshots now use a neutral placeholder company name instead of a real customer's.
  • A pre-commit hook keeps customer names and internal hostnames out of commits.

Gratuit pour un usage personnel, éducatif et non lucratif. L'usage commercial — y compris un consultant indépendant en mission — requiert une licence. Chaque build est produit par la CI de release et servi depuis mayorana.ch.

Toutes les versions

AIS Runner 0.5.49

Added

  • Ctrl-C, kill, a logout or a cancelled CI step now run the same teardown as quitting the app: connections.json and workflow.json are restored to the committed versions, local.settings.json is returned to its pre-scenario state, and every emulator or func process the app started is stopped. Previously a signal took the process out between two instructions and left patched files patched and Azurite reparented to init.

AIS Runner 0.5.48

Added

  • Opening a project heals patches left behind by a session that did not exit cleanly. connections.json and workflow.json files still carrying local run patches are restored from their snapshots instead of staying dirty in the working tree indefinitely.

Changed

  • A failed run now explains itself one level down: instead of the runtime's "An action failed. No dependent actions succeeded.", the panel walks into the Foreach repetition and the invoked workflow's response body to report the action that actually broke.

AIS Runner 0.5.47

Changed

  • Release pipeline only — no user-visible change.

AIS Runner 0.5.46

Fixed

  • Window titles no longer carry a "Local" prefix, so two AIS windows are distinguishable in the macOS window list.

AIS Runner 0.5.45

Added

  • Overlap analysis for Event Grid subscriptions. Two subscriptions on the same system topic whose filters overlap deliver the same event twice, and nothing in the Azure portal says so — the Event Grid panel now flags the overlapping pairs, along with subscriptions that have no dead-letter destination and so discard events once the retry policy is exhausted.

AIS Runner 0.5.44

Added

  • Event Grid subscriptions are grouped by topic in the panel, with the overlapping ones drawn together rather than scattered down a flat list.

AIS Runner 0.5.43

Added

  • JDK selection for Java function apps. AIS Runner detects the JDKs installed on the machine and lets you pick which one mvn package and mvn azure-functions:run use, instead of inheriting whatever JAVA_HOME happens to hold.
  • Workflow authentication patching for local runs. HTTP actions that authenticate with ActiveDirectoryOAuth cannot resolve their tenant, client id and secret locally — the parameters come from app settings that only exist in Azure — so the action failed before it ever reached a stub. The auth block is now stripped for the local run and restored when func stops.

AIS Runner 0.5.42

Added

  • connections.json is snapshotted before a local run and restored when func stops. The Logic Apps runtime reads that file and only that file, so the patched version has to land there — but it no longer stays there, and the working tree is dirty only while func is running.

AIS Runner 0.5.41

Changed

  • The update check sends a versioned User-Agent, so per-version adoption is visible in the download logs — the number that says how many people are still on a build with a bug that is already fixed.

AIS Runner 0.5.40

Added

  • Ports held by a leftover process are reclaimed automatically. Starting Azurite or func after a previous session was killed no longer fails with a bind error that names no owner.

AIS Runner 0.5.39

Added

  • Port conflicts name the process holding the port, instead of reporting "address already in use" and leaving you to find it.

AIS Runner 0.5.38

Added

  • KPI chips on scenario groups: pass rate and verdict on the group header, with a running scenario held out of the count until it settles.

AIS Runner 0.5.37

Changed

  • Packaging only — no user-visible change.

AIS Runner 0.5.36

Fixed

  • Every process the app spawned — Azurite, the Service Bus emulator, func, mvn — is terminated when the app exits. They used to survive it and hold their ports.

AIS Runner 0.5.35

Fixed

  • macOS notifications are initialised at startup, so the first notification no longer raises the system's "Where is use_default?" dialog.

AIS Runner 0.5.34

Fixed

  • Installer permissions on Windows, and port handling for scenario runs.

AIS Runner 0.5.33

Added

  • A scenario run or a full sweep can be cancelled. Cancellation is cooperative: the step in flight finishes, nothing further starts, and the teardown still runs.

AIS Runner 0.5.32

Added

  • function_apps/local.settings.json is seeded with the keys a Java function app needs, so mvn azure-functions:run starts on a fresh clone instead of failing on a missing setting.

AIS Runner 0.5.31

Changed

  • Internal: the Azure integration was split into azure::auth and azure::servicebus, and moved under a single azure module. No behaviour change.

Le même historique, en JSON

Cette page est générée à partir d’un flux publié à côté des builds — le fichier que AIS Runner lit lui-même pour vérifier les mises à jour. Branchez-y un script si vous suivez les versions à l’échelle d’une équipe.

https://mayorana.ch/downloads/ais-runner/latest/releases.json

Besoin d'une version adaptée à votre stack ?

Ces outils sont nés de vrais projets d'intégration Azure. Si le vôtre demande une variante — une autre source de données, vos propres conventions, un build on-premise — c'est exactement le type de mission que nous prenons.

Nous contacter