v0.4.0

No source changes since v0.3.5; re-released for updated upstream pins.

No source changes since v0.3.4; re-released for updated upstream pins.

No source changes since v0.3.3; re-released for updated upstream pins.

Changed

• JavaFX 27 (2026-10-18), from 25.0.4, with the rest of the platform. JavaFX 27 needs Java 25.

Added

• The Modules tab says whether each newest tag built on JitPack. A Tag on JitPack column (built, never
  built, not built yet; hover a broken one for JitPack's message), and a red banner over the table when a tag
  never built, naming each one and the ./release.sh flags that cut their next patch. Studio's and the
  dashboard's tags count as broken when they pin a tag that is.
• The Changelog tab's Never built asks JitPack about the module's newest tag and, when it never built, adds
  the repair release's entry under ### Fixed in the editor. Nothing is saved until Save.

v0.3.5

No source changes since v0.3.4; re-released for updated upstream pins.

No source changes since v0.3.3; re-released for updated upstream pins.

Added

• The Modules tab says whether each newest tag built on JitPack. A Tag on JitPack column (built, never
  built, not built yet; hover a broken one for JitPack's message), and a red banner over the table when a tag
  never built, naming each one and the ./release.sh flags that cut their next patch. Studio's and the
  dashboard's tags count as broken when they pin a tag that is.
• The Changelog tab's Never built asks JitPack about the module's newest tag and, when it never built, adds
  the repair release's entry under ### Fixed in the editor. Nothing is saved until Save.

v0.3.4

No source changes since v0.3.3; re-released for updated upstream pins.

Added

• The Modules tab says whether each newest tag built on JitPack. A Tag on JitPack column (built, never
  built, not built yet; hover a broken one for JitPack's message), and a red banner over the table when a tag
  never built, naming each one and the ./release.sh flags that cut their next patch. Studio's and the
  dashboard's tags count as broken when they pin a tag that is.
• The Changelog tab's Never built asks JitPack about the module's newest tag and, when it never built, adds
  the repair release's entry under ### Fixed in the editor. Nothing is saved until Save.

v0.3.3

Added

• The Modules tab says whether each newest tag built on JitPack. A Tag on JitPack column (built, never
  built, not built yet; hover a broken one for JitPack's message), and a red banner over the table when a tag
  never built, naming each one and the ./release.sh flags that cut their next patch. Studio's and the
  dashboard's tags count as broken when they pin a tag that is.
• The Changelog tab's Never built asks JitPack about the module's newest tag and, when it never built, adds
  the repair release's entry under ### Fixed in the editor. Nothing is saved until Save.

v0.3.2

Fixed

• 0.3.1 never packaged. It pinned botmaker-shared v0.2.4, a tag JitPack never built (Maven Central's 429), so
  its rpm and deb jobs could not resolve it. This release pins shared 0.2.5 and is 0.3.1 otherwise.

v0.3.0

Changed

• A release lane (the Release and Releases tabs) links every stepper page: Commit ↗ (the tag's commit) and
  JitPack ↗ (the tag's build, for a module JitPack builds) beside the tag and Actions ↗.
• The pom carries a real version and names its upstreams' versions instead of 0.0.0-SNAPSHOT, and the
  module's .deps.env is gone (umbrella docs/refactor/43-real-versions.md).
• A tagged build resolves shared and the cli its pom pins from JitPack instead of building them from source.
  The installed app learns which cli it carries from the pom's pin, baked in at package time.
• The Modules tab shows each module's pom version on HEAD, and the pins read from its latest tag's pom (Tag's
  pins, was .deps.env pins). The release's own back-to-snapshot and pin commits no longer count as
  commits since the tag, there or when drafting a changelog.

No source changes since v0.1.3; re-released for updated upstream pins.

Changed

• JitPack links open jitpack.io/#BotMakerDev/…, the coordinate owner since the move from LiQiyeDev.

Added

• The Release tab has a Stop button while a release runs. The release ends before its next module, or at
  once in a JitPack wait, and never cuts a git command short; it writes its log and commits the tagged
  pointers locally, as a failed module does. A board lane shows a JitPack build that failed as failed.

Fixed

• A release that succeeded no longer reads as Failed ("jitpack: unknown (interrupted) · actions: no run on …")
  in the Releases tab. Refresh relisted the history, the relist reselected the release, and the reselect's
  poll interrupted the Refresh's own poll mid-request; the interrupted answers were then cached and outranked
  the log. A poll that a running one already covers no longer cancels it, an interrupted answer is never
  cached, and a cached non-answer gives way to a green cell in the release log, which also heals a cache that
  already holds one.
• The Catalog's JitPack link for one of our plugins opens the coordinate owner's page
  (jitpack.io/#LiQiyeDev/<module>), where JitPack builds it, instead of the repository owner's.

Removed

• Update template… in the Catalog tab, with its dialog. A template is released like any other module, with
  --gamebot in the Release tab or release.sh.

v0.2.0

No source changes since v0.1.4; re-released for updated upstream pins.

No source changes since v0.1.3; re-released for updated upstream pins.

Fixed

• A release that succeeded no longer reads as Failed ("jitpack: unknown (interrupted) · actions: no run on …")
  in the Releases tab. Refresh relisted the history, the relist reselected the release, and the reselect's
  poll interrupted the Refresh's own poll mid-request; the interrupted answers were then cached and outranked
  the log. A poll that a running one already covers no longer cancels it, an interrupted answer is never
  cached, and a cached non-answer gives way to a green cell in the release log, which also heals a cache that
  already holds one.
• The Catalog's JitPack link for one of our plugins opens the coordinate owner's page
  (jitpack.io/#LiQiyeDev/<module>), where JitPack builds it, instead of the repository owner's.

Removed

• Update template… in the Catalog tab, with its dialog. A template is released like any other module, with
  --gamebot in the Release tab or release.sh.

v0.1.4

No source changes since v0.1.3; re-released for updated upstream pins.

Fixed

• A release that succeeded no longer reads as Failed ("jitpack: unknown (interrupted) · actions: no run on …")
  in the Releases tab. Refresh relisted the history, the relist reselected the release, and the reselect's
  poll interrupted the Refresh's own poll mid-request; the interrupted answers were then cached and outranked
  the log. A poll that a running one already covers no longer cancels it, an interrupted answer is never
  cached, and a cached non-answer gives way to a green cell in the release log, which also heals a cache that
  already holds one.
• The Catalog's JitPack link for one of our plugins opens the coordinate owner's page
  (jitpack.io/#LiQiyeDev/<module>), where JitPack builds it, instead of the repository owner's.

Removed

• Update template… in the Catalog tab, with its dialog. A template is released like any other module, with
  --gamebot in the Release tab or release.sh.

v0.1.3

Fixed

• A release that succeeded no longer reads as Failed ("jitpack: unknown (interrupted) · actions: no run on …")
  in the Releases tab. Refresh relisted the history, the relist reselected the release, and the reselect's
  poll interrupted the Refresh's own poll mid-request; the interrupted answers were then cached and outranked
  the log. A poll that a running one already covers no longer cancels it, an interrupted answer is never
  cached, and a cached non-answer gives way to a green cell in the release log, which also heals a cache that
  already holds one.
• The Catalog's JitPack link for one of our plugins opens the coordinate owner's page
  (jitpack.io/#LiQiyeDev/<module>), where JitPack builds it, instead of the repository owner's.

Removed

• Update template… in the Catalog tab, with its dialog. A template is released like any other module, with
  --gamebot in the Release tab or release.sh.

v0.1.2

Changed

• Built against botmaker-cli 0.1.2, so its Release tab runs the release library that cut this set. No change
  of its own.