Nexus 1.10.0
Released 31 August 2026. The current release is 1.24.0. Download it · Every version
Added
-
Field Day club sync — every position's contacts in one club log, live over the site LAN, no third-party logger.
One PC at the club site turns on Settings ▸ Contesting ▸ Field Day Club Sync ▸ Host a club event (the one time Nexus listens beyond the local computer, and the toggle says so); every other position joins it — Find club events discovers the host on the network, or type its address — and from then on each logged contact streams to the host the moment it lands. Every position sees the club's score, QSO and section totals, a live band board (who is on which band/mode, with rate, stale- marked the moment a position goes quiet), and a club dupe warning while typing: if another tent already worked that call on this band and mode you are told before you call — a warning, never a lock, exactly as N3FJP treats it (your own log's dupes still refuse). Everything keeps working through failures: a position that loses the network logs on paperlessly and re-syncs by itself when the cable comes back; if the host PC dies, turn on hosting at any other position and everyone re-joins with nothing lost. The host exports the merged club log as Cabrillo or ADIF, deduplicated the way the rules score it. A sync chip on the Field Day view always tells the truth — Synced, Behind (with the count), or Offline — and positions with clocks off by more than 30 seconds are told to fix them. The N3FJP/N1MM interop pushes are untouched and keep running alongside.
-
The club band board is its own window, one click from anywhere.
A Club Board button sits in the left rail under Field Day and opens the board — position, band, mode, operator, QSOs, rate — as a standalone window for a second monitor, in larger type than the dashboard copy because it is watched from the operating position rather than read at the keyboard. This is the display a multi-station club keeps up all event to see where everyone is before moving to another band. The button is there whenever Field Day is on, before club sync is switched on: opened with sync off, the window says so and names the route that starts it (Settings ▸ Contesting ▸ Field Day Club Sync ▸ Host a club event) instead of showing an empty board; with sync on and nobody else logging yet, it says it is waiting. Previously the board existed only as a block inside the Field Day dashboard that appeared once sync was already running, so an operator who had not found the setting had no way to learn the board was there.
-
Field Day spectator scoreboard — the club's score on the TV, from a web page the host serves itself.
Turn on Settings ▸ Contesting ▸ Field Day Club Sync ▸ Spectator scoreboard at the host position and any browser on the site network — a smart TV, a projector's laptop, a visitor's phone — can open the address the Settings row shows (port 7373 by default; nothing to install on the TV). One dark big-screen page shows the live score, contact count and rate, all 83 ARRL/RAC sections lighting up as they are worked, contacts by band and mode, a per-tent leaderboard, the bonus checklist, and each new contact as it lands — plus one plain-language line so non-ham visitors know what they are watching. The page is read-only by construction (viewers can only look; nothing on it can reach the radio), works with zero internet, keeps itself updated, and rides out Wi-Fi blips on its own. Scores are event-honest: ARRL FD shows the powered math, Winter Field Day shows raw QSO points with the at-submission multiplier clearly labelled as projected — never ARRL power math applied to an event that has none.
-
Field Day rules can now be refreshed as data — and the countdown finally knows how long the events really run.
The numbers behind Field Day — points per mode, power tiers, the bonus menu, the section list, event weekends, Winter Field Day's banned-mode list — now ship as a rules file the app can update, instead of being frozen into each release. A Check for rules updates button in Settings ▸ Contesting ▸ Field Day Setup fetches the current file before the event (validated before it is trusted, applied at the next launch, with the built-in copy as the floor — the country-file discipline). The Field Day banner shows which rules year is scoring your log and the Cabrillo export records it (
X-NEXUS-RULES-YEAR:), so a submission is traceable to the parameters that scored it. In the same change the banner and countdown stop pretending both events are 24 hours: ARRL Field Day is 27 (1800Z Saturday → 2100Z Sunday) and Winter Field Day 30 (1600Z Saturday → 21:59Z Sunday) — previously the app declared WFD over with six hours still on the clock and started counting down to next year. -
Your country file can finally be updated — and Nexus tells you how old it is.
The DXCC country data that drives the Needed board, award credit and entity labels was frozen into each release; every install has been running a file from January 2025. Settings ▸ Logging ▸ Country file (DXCC) now shows the file's actual date and fetches the current one — the full big-CTY edition, same as the big loggers use — checked weekly for freshness the way the callsign database already is. A downloaded file is validated before it is ever trusted and takes effect at the next launch; the built-in copy remains the floor, so a bad download can never make things worse. Works the N3FJP way: update at home before Field Day, operate all weekend offline.
-
The rotator picker stops steering Easy-Rotor-Control owners wrong.
DF9GR's ERC V4 board speaks three protocols, chosen in its own Service Tool — and configured the way its manual recommends (GS-232B at 9600), the picker entry with the board's name on it was the one that could never work: that entry is the DCU-1 flavour at a fixed 4800. Both labels now say which mode they are, and the manual says which entry matches which Service-Tool setting. If you run an ERC V4 as the vendor ships it, pick Yaesu GS-232B at 9600.
-
The POTA/SOTA board tears off into its own window.
The hunter board's filters were already saved per-window — the code was written for this and the window never came. A pop-out button now opens it beside your operating screen (or one per program: a POTA board next to a SOTA board), and HUNT works from the pop-out exactly as it does docked — click a spot and the radio QSYs, mode and all.
-
Nexus speaks Japanese.
日本語に対応しました。 The whole application — all 4,765 phrases, every screen, the same coverage the other languages have — picked up automatically from your system language or chosen in Settings. Written to Japanese amateur-radio convention (ゼロイン for zero-beat, Eスポ for sporadic-E, コンファーム for confirmations), with polite sentence forms for messages and terse labels for controls. Frequencies, callsigns, reports, band and mode names are never translated — 14.074 is 14.074 in every language.
-
Your amplifier can follow the radio's band.
Switch it on under Settings ▸ Radio ▸ Amplifier and the amp steps to whatever band you tune to, without being asked. It is off until you turn it on, which is deliberate — this is the one amplifier control that acts on its own, and you should choose it rather than discover it. It never moves the amplifier while you are transmitting, and it steps one band at a time, checking where the amplifier actually is after each step rather than assuming it arrived. If your radio is on a band the amplifier does not have, it does nothing at all instead of picking the nearest. ⚠️ If your amplifier already follows the radio through its own band-data cable — which is how most SPE installations are wired — leave this off. The hardware is doing the same job, and two things steering one band is worse than either alone.
Changed
-
Click a previous contact to see that station's log.
The callsign card lists every earlier contact with the station in front of you. Those rows are now clickable: one takes you to the Logbook with that callsign filtered, so you get the whole history instead of the few lines that fit on the card. Works from every operating screen.
-
The club TV says who is on what band.
The spectator scoreboard — the page a club puts on a screen facing the room — listed each operating position with its operator, QSOs and points, but not the one thing a multi-station club actually walks over to ask: which band that tent is on. Every position row now carries its current band and mode, coloured by band the same way the globe and the band grid are. It is presence, not history, so it expires: when a position's link has been quiet longer than the sync layer's own timeout the reading goes dim rather than claiming, for the rest of the event, that somebody is still on 20 metres.
-
The club band board pops out onto its own screen.
The board that shows every position's band, mode, operator and rate now has a Pop out board button beside the club exports, so a multi-station club can park it on a second monitor or a corner of the big one and keep it in view all event instead of scrolling the dashboard back to it. The torn-off window is for watching: it carries no operator field and no export buttons, both of which stay on the dashboard where they can tell you what they did.
-
The Field Day dashboard is a Field Day screen now, not the digital operating screen with a scoreboard in the middle.
It used to be drawn inside the FT8 workspace, so it came with a waterfall, a band-activity list and the stations rail either side of it — none of which a score, log and setup screen has anything to do with, and all of which squeezed it into a narrow middle column that left its top row of buttons crowded. It now gets the window to itself: one column, no rails, and up to 1600 px of width instead of about 1180. The waterfall and band activity have not gone anywhere — they are where they belong, in Operate, which is where digital Field Day contacts are made.
-
The operator button is there before anyone has been named.
The OP button in the top bar swaps who is at the key from any mode, but it only appeared once an operator had already been set — which is backwards for a club station, where the first person to sit down is the one who needs it. With Field Day switched on it is now always there, reading Set operator until somebody claims the seat; pick anyone the log has seen in one click. On a single-operator station with Field Day off, nothing changes and the button stays out of the way.
-
Field Day: the club call, the position and the operator are explained side by side.
A club site answers "who are you?" three different ways — the club callsign that goes on the air, the position you are sitting at ("CW tent", "comms trailer"), and whoever is at the key right now — and Nexus had all three, on three different screens, with nothing saying how they relate. The position name in particular read as a mystery box. Settings ▸ Contesting now opens with Who's who at this event: the three of them together, each with one plain line saying what it is and how it differs from the other two. They are the same settings as before, not copies — change one here and it changes everywhere, including the Station tab and the OPERATOR box on the Field Day dashboard. The position name moved into that group from the club-sync section below it.
-
The Windows download installs about 32 MB less.
Turning on link-time optimisation took
Nexus.exefrom 87 MB to 55 MB, which is most of what the audio-library upgrade in 1.9.2 cost. Nothing about the app changes; it is the same build, compiled more tightly. The installer itself only shrinks a little because it was already compressed — the saving is disk space on your machine, not download size.
Fixed
-
A ClubLog catch-up no longer looks like a flood.
Saving your ClubLog password makes Nexus send any contacts that never uploaded. It was sending them all at once, back to back, which ClubLog reads as abusing the live-upload endpoint. One operator was warned his address would be blocked. Contacts you just worked still upload immediately, as they should. A catch-up now goes out one every 15 seconds, and if ClubLog is busy and the retries stack up, they stay spaced out rather than arriving in one burst when it recovers. Worth knowing if you import an old log: the imported contacts count as never uploaded, so the next time you save your password Nexus offers them to ClubLog. It says so in the connection log while it works through them.
-
RTTY on a radio that has no RTTY mode.
On a FlexRadio over SmartSDR CAT there is no RTTY mode to select, so Nexus asked for one, was refused, and gave up silently — leaving the radio in whatever the last mode was, usually the wide data mode FT8 had set. It now falls back to the data sideband the radio does accept, which is what AFSK RTTY needs anyway.
-
Your own transmissions no longer follow you to another band.
Nexus keeps a short record of the overs you have sent so your calls do not vanish when the app changes band under you, but that record never noted which band each one went out on. Change from 20 to 40 and your 20 m calls came back, carrying the times they were originally sent.
-
Tune could interrupt itself: a blip and a brief power drop while the carrier was up.
Reported by an operator running an FTDX-101D who saw the power fall 10–15 W for about a second, on the waterfall and on an analogue wattmeter, and only in Nexus — never in WSJT-X on the same station. Nexus was writing the VFO frequency to the radio while it was transmitting: a tune deliberately cancels any pending transmission, and the code that puts the dial back after a Split Operation offset read that as "nothing is on the air" and went ahead. A Yaesu re-locks its synthesiser when the frequency changes, which is precisely a blip and a momentary power drop. The dial now waits for the carrier to stop, which is what the rest of the transmit path already did. Most likely to have bitten anyone who tunes up straight after an FT8 over with Split Operation on. Power changes Nexus commands are also written to the diagnostic log now, so a report like this one can be answered from a log instead of argued.
-
Renaming a Field Day position now shows up on the club board straight away — and a position is never nameless.
The position name was sent to the host once, when the position joined, so naming a tent after the event had started — or renaming it — left the club band board showing the old text, or the internal position id, until the connection happened to be rebuilt, with nothing on screen to explain it. The name now travels with every position update, so a rename reaches the board within seconds and every other position sees it. A position that has no name set uses your callsign instead of the internal id, and if you deliberately clear the name while hosting or joining a club event, Save says so rather than putting a blank row on the board.
-
macOS: a fresh install could not connect to a radio at all.
Every new Mac install failed at the setup wizard's Test CAT with "Nexus could not start its own rigctl", and the only way round it was to install Hamlib separately with Homebrew. Nexus ships Hamlib inside the app — correctly, and correctly signed — but on macOS it was looking for it one folder up from where the build actually puts it, so it never found its own copy and fell back to searching the system, which on a clean Mac has nothing to find. Windows and Linux were never affected. The release build now also opens the shipped .app and runs the bundled rigctld, so this cannot come back quietly. (#190)
-
Band dropdowns no longer offer bands no radio in the shack can reach.
With an HF rig and a 2 m/70 cm radio configured, the band lists still offered 23 cm and everything else your licence allows. The list is now the bands your licence allows and at least one of your enabled radios covers. A radio with no bands listed still means "covers everything", so if you run one radio — or have not set any of this up — nothing changes. Manually tuning somewhere outside the list still works and the picker still shows where you are. (#184)
-
Erase now clears your own transmissions too.
Pressing Erase wiped the pane and the next quarter-second painted every one of your own overs straight back, so the only way to clear them was to restart Nexus. Received decodes cleared properly, which is why it looked like Erase half-worked. Nexus keeps a short record of the overs you have already sent — that is deliberate, and it is what stops your own calls disappearing when the app changes band under you — but the pane was re-reading it after every wipe. Each pane now remembers being erased: everything sent up to that moment stays gone, the next over you send still appears, and erasing Band Activity leaves Rx Frequency alone, the way the two windows have always worked.
-
Your own transmissions no longer vanish from Rx Frequency when the DX call looks like P29YY.
Calling a station whose callsign starts letter-digit-digit (P29YY, T77C, SP2GIF — the #178 sightings) completed the QSO fine, but none of your own overs appeared in the Rx Frequency pane or in ALL.TXT — the own-transmission recorder mistook them for internal chat-wire framing and skipped them. The skip is now scoped to the chat modes, the only place that framing exists. Display and logging only; nothing about what goes on the air changed.
-
Field Day now warns when the rules disagree with what you're doing — and never blocks.
Winter Field Day's ruleset has always known the WSJT modes are not permitted there; nothing ever said so. A chip in the event banner and the Operate header now cites the event and rules year ("FT8 is not permitted at Winter Field Day (2026 rules) — you can still log it, but it will not count"). The same machinery covers spotting-assistance restrictions, citing the rule when a ruleset restricts and the matching feed is live — dormant today for both events, because the 2026 ARRL rules were read and contain no such restriction, and WFD's could not be read; no advisory will ever cite a rule nobody verified. Score Summary exports say which year's rules scored them.
-
A Winter Field Day RTTY contact no longer reaches your club logger labelled FT8.
The FD log has always known the actual on-air mode behind a digital contact, but the push to N3FJP and N1MM re-derived every digital row as FT8 — at WFD, a banned mode. The recorded mode now travels the whole way: RTTY pushes as RTTY, and Cabrillo's RY rows, ADIF and the club logger finally agree. Rows logged before this release keep the old fallback.
-
The Field Day manual told you the event was 24 hours.
ARRL Field Day runs 27 and Winter Field Day 30; the manual now carries the real windows, corrects the claim that class and section have defaults (they must be set before FD mode engages), and documents what shipped undocumented: the pop-out scoreboard, the Operator field, the sections board, WFD's advisory mode restrictions, and all four exports. Two new build-time guards also pin the hand-mirrored sections and bonus tables between Rust and the UI, so the 83-section board and the bonus list can no longer drift apart silently.
-
Spanish and French showed doubled text wherever a count was involved.
Fifty-two messages in each language — import results, sync summaries, alert batches — had both grammatical forms of the sentence glued together, so a French operator importing a log read "3 QSO importé3 QSO importés". Shipped that way since 1.9.0. Every one is repaired, and a guard now fails the build if the shape ever comes back.
-
A band you cannot transmit on is now listed anyway, so you can listen.
The band dropdowns hid any band your licence class holds no transmit privileges for, which applied a transmit rule to a tuning list — nothing restricts receiving, and the radio tunes there regardless. A US General could not select 4 m at all rather than being able to listen on it. Every band your radios can reach is now offered, with the ones you cannot key marked "receive only". Transmitting on them is refused exactly as before — listing a band has never been permission to transmit on it. Reported by akhepcat (#184).
-
Parks on the air now show on the Connect map.
POTA activators appear where they actually are — the feed sends each park's own coordinates, which Nexus had been fetching and discarding in favour of the grid square, so a park that was placed to about 4 km is now placed to the park. They draw as a triangle rather than another dot, because an activator is somewhere you go and work, not one more spot in the firehose: filled for a park you have never logged, hollow for one already in your log. Hover names the activator, the reference, the frequency and the mode. The layer is off until you turn it on, and only then does it fetch anything. Turning on the POTA/SOTA view switches it on for you — that view has promised "park/summit activators" since it shipped and until now enabled nothing of the kind. ⚠️ POTA only. A SOTA spot carries no position at all, and their spot feed is being retired — see below.
-
A three-day space-weather outlook: when do the bands settle down?
Everything in Connect described conditions as they are now; nothing said what was coming. The new Kp outlook pane shows NOAA's planetary-K forecast — the worst period still ahead, when a storm is expected to start, and when it drops back. Measured hours are drawn as solid bars and the forecast as hollow ones, so a prediction can never be misread as a reading. If NOAA has published nothing, it says so instead of drawing a quiet sky.
-
A geomagnetic storm now finds you.
A solar flare already raised an alert anywhere in the app, and so did a band coming alive — but a geomagnetic storm only ever appeared in the Space Weather pane, so you saw it only if you were looking straight at it. That is backwards: a flare is minutes of absorption, a storm is hours or days of degraded HF. Storms now raise the same kind of heads-up, quiet at G1 and prominent with a beep from G2, and they never repeat themselves while the index wobbles around a threshold. With the outlook in hand there is a second, separate note when NOAA expects a storm that has not started yet. Nexus tells you; it never touches the radio.
-
Connect on the shack TV.
Turn on Settings ▸ Appearance ▸ Connect on a TV and Nexus serves your conditions picture as a plain web page to any browser on your network — a TV across the room, a tablet on the bench, a phone. Large type, no controls, refreshes itself: band conditions, space weather, live openings, the plain-language notes and the forecast peak. It is read-only in the strict sense — there is no way to change anything from it, and the page loads nothing from the internet, so it works at a site with no connection. It is off until you turn it on, and the setting says plainly what anyone on your network would see: your callsign, your grid and band conditions. Your log, your needs board and the frequency you are on are never sent.
-
Memories offered every mode and let you pick only one.
Adding a channel by hand showed a mode list with eight entries in it, of which exactly one could be chosen — whichever mode the radio happened to be on, so for most stations "USB is the only mode I can add". The list was the kind that filters itself down to what is already typed in the box, and a new memory starts on the rig's current mode. It is an ordinary dropdown now, with every mode always in it, and an Other… row for a mode we do not list. The tone picker had the same fault — with 103.5 in the box the 38-tone list collapsed to that one tone — and got the same fix. A channel imported from CHIRP carrying a mode or tone Nexus has never heard of keeps it: it appears in the list as its own entry instead of being quietly rewritten the first time you touch the row.
-
The + New button looked dead, and new memories came out as digital modes.
With anything typed in the search box, + New created the channel and then the search filtered it straight back out — a new memory has no name yet — so the row and its editor were invisible and the button appeared to do nothing. + New clears the search now. New memories also defaulted to FT8 regardless of what the radio was doing; they take the rig's current mode.
-
Adding a memory happened somewhere in the list; now it happens in one place.
+ New opened the editor on the new row wherever the sort, the band sections and the filters had put it — in a bank of 200 channels, usually off screen. It opens a panel pinned at the bottom of the pane instead, and the new row is marked in the list and the grid so it can still be found. Pressing Escape in a field reverts that field as it always did, without closing the form around it; opening + New and closing it again no longer leaves an unnamed channel behind each time.
-
Deleting memories: select several, and take it back.
Every row has a tick box, the grid has a select-all in its header, and deleting names how many will go before it does it. Deletion only ever takes rows you can actually see — narrow the list with a search and the rows hidden by it are safe — and the bar says so when part of your selection is out of view. Every delete, including the single ✕ on a row, offers an Undo for eight seconds, and rows come back in the position they were deleted from, so favorite order and the cockpit strip are unchanged. Asked for by KD9TAW.
-
A memory deleted in the popped-out Memories window could not be undone.
Torn-off windows had no way to show a message, so the Undo the confirmation promised was raised and dropped on the floor — the rows went and nothing appeared. Seven of the pop-out windows were in that state; all of them can show messages now.
Every version
- 1.24.0 11 Nov 2026
- 1.23.0 5 Nov 2026
- 1.22.0 1 Nov 2026
- 1.21.0 26 Oct 2026
- 1.20.0 22 Oct 2026
- 1.19.0 16 Oct 2026
- 1.18.0 12 Oct 2026
- 1.17.0 7 Oct 2026
- 1.16.0 3 Oct 2026
- 1.15.0 26 Sept 2026
- 1.14.0 20 Sept 2026
- 1.13.0 16 Sept 2026
- 1.12.0 14 Sept 2026
- 1.11.1 8 Sept 2026
- 1.10.3 4 Sept 2026
- 1.10.2 3 Sept 2026
- 1.10.1 1 Sept 2026
- 1.10.0 31 Aug 2026
- 1.9.2 29 Aug 2026
- 1.9.1 26 Aug 2026
- 1.9.0 25 Aug 2026
- 1.8.1 23 Aug 2026
- 1.8.0 23 Aug 2026
- 1.7.6 21 Aug 2026
- 1.7.5 20 Aug 2026
- 1.7.0 18 Aug 2026
- 1.6.1 17 Aug 2026
- 1.6.0 16 Aug 2026
- 1.5.0 16 Aug 2026
- 1.4.0 15 Aug 2026
- 1.3.0 13 Aug 2026
- 1.2.0 10 Aug 2026
- 1.1.0 10 Aug 2026
- 1.0.5 8 Aug 2026
- 1.0.2 6 Aug 2026
- 1.0.1 5 Aug 2026
- 1.0.0 4 Aug 2026
- 0.28.2 3 Aug 2026
- 0.28.0 3 Aug 2026
- 0.27.0 2 Aug 2026
- 0.25.0 1 Aug 2026
- 0.24.0 31 Jul 2026
- 0.21.5 29 Jul 2026
- 0.21.0 29 Jul 2026
- 0.20.0 28 Jul 2026
- 0.19.7 27 Jul 2026
- 0.19.6 26 Jul 2026
- 0.19.4 26 Jul 2026
- 0.18.0 25 Jul 2026
- 0.17.22 25 Jul 2026
- 0.17.21 25 Jul 2026
- 0.17.20 25 Jul 2026
- 0.17.19 25 Jul 2026
- 0.17.18 25 Jul 2026
- 0.17.17 25 Jul 2026
- 0.17.16 25 Jul 2026
- 0.17.15 25 Jul 2026
- 0.17.14 25 Jul 2026
- 0.17.13 25 Jul 2026
- 0.17.12 25 Jul 2026
- 0.17.11 25 Jul 2026
- 0.17.6 25 Jul 2026
- 0.17.5 25 Jul 2026
- 0.17.4 25 Jul 2026
- 0.17.3 25 Jul 2026
- 0.17.2 24 Jul 2026
- 0.17.1 24 Jul 2026
- 0.16.4 24 Jul 2026
- 0.16.3 24 Jul 2026
- 0.16.2 24 Jul 2026
- 0.16.1 24 Jul 2026
- 0.16.0 24 Jul 2026
- 0.15.24 24 Jul 2026
- 0.15.23 24 Jul 2026
- 0.15.22 24 Jul 2026
- 0.15.21 24 Jul 2026
- 0.15.20 24 Jul 2026
- 0.15.18 24 Jul 2026
- 0.15.17 24 Jul 2026
- 0.15.16 23 Jul 2026
- 0.15.15 23 Jul 2026
- 0.15.14 23 Jul 2026
- 0.15.1 22 Jul 2026
- 0.15.0 21 Jul 2026
- 0.14.0 21 Jul 2026
- 0.13.0 19 Jul 2026
- 0.12.0 18 Jul 2026
- 0.11.1 18 Jul 2026
- 0.11.0 18 Jul 2026
- 0.10.0 17 Jul 2026
- 0.9.7 17 Jul 2026
- 0.9.6 16 Jul 2026
- 0.9.5 16 Jul 2026
- 0.9.4 16 Jul 2026
- 0.9.3 16 Jul 2026
- 0.9.2 15 Jul 2026
- 0.9.1 15 Jul 2026
- 0.9.0 15 Jul 2026
- 0.8.9 15 Jul 2026
- 0.8.8 14 Jul 2026
- 0.8.7 14 Jul 2026
- 0.8.6 14 Jul 2026
- 0.8.5 14 Jul 2026
- 0.8.4 13 Jul 2026
- 0.8.3 13 Jul 2026
- 0.8.2 13 Jul 2026
- 0.8.1 12 Jul 2026
- 0.8.0 12 Jul 2026
- 0.7.1 12 Jul 2026
- 0.7.0 12 Jul 2026
- 0.6.0 11 Jul 2026
- 0.5.2 11 Jul 2026
- 0.5.1 10 Jul 2026
- 0.5.0 10 Jul 2026
- 0.4.1
- 0.4.0
- 0.3.0
- 0.2.0 3 Jun 2026
- 0.1.0