Skip to content

Releases

v0.7.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 19:41

Full Changelog: v0.6.0...v0.7.0

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 01:48

Full Changelog: v0.5.1...v0.6.0

v0.5.1

Choose a tag to compare

@github-actions github-actions released this 01 Nov 09:56

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 30 Oct 01:58

Full Changelog: v3.20...v0.5.0

v0.4.1

Choose a tag to compare

@github-actions github-actions released this 27 Oct 20:07

Full Changelog: v0.4.0...v0.4.1

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 16:11

Full Changelog: v0.3.0...v0.4.0

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 19 Oct 18:32

Full Changelog: v0.2.7...v0.3.0

v0.2.7

Choose a tag to compare

@github-actions github-actions released this 02 Sep 12:33

The bundled FujiNet runtime moves back onto upstream master (fujinet-firmware 13465cdd).

The pin was on a branch that never merged. force-mbedtls-3 (07e1bed3) was never an ancestor of master, so the runtime had been standing still while upstream moved on. The Mbed TLS 3.x requirement it was branched for landed as #1595, which makes the branch unnecessary.

From the firmware

  • The new DaisyChain class, centralising device-chain management across buses (#1594).
  • The DriveWire .cas media format (#1596).

Not a change here: calendar compose/edit and Gmail composition arrived in 0.2.6 and are unaffected.

Full Changelog: v0.2.6...v0.2.7

🤖 Generated with Claude Code

https://claude.ai/code/session_01KXV26TS81xzQwC7wwGzjMQ

v0.2.6

Choose a tag to compare

@github-actions github-actions released this 01 Sep 19:40

The bundled FujiNet runtime moves up to fujinet-firmware 07e1bed3.

The runtime no longer builds against Mbed TLS 4.x. That release removed the low-level crypto headers the runtime's TLS backend needs and split the rest into a separate library, so a machine whose system Mbed TLS had moved on to 4.x could produce a build with quietly broken TLS instead of a clear failure. The build now finds a 3.x install, or stops and says so.

From the firmware

  • Gmail message composition.
  • The CALENDAR, GCAL and ICAL protocols can now create and edit events, not only read them.

Full Changelog: v0.2.5...v0.2.6

🤖 Generated with Claude Code

https://claude.ai/code/session_01NaoP5g59a2xKc9iuGPrFGd

v0.2.5

Choose a tag to compare

@github-actions github-actions released this 29 Aug 18:20

Calendar protocols in the bundled FujiNet.

  • The bundled FujiNet runtime moves from b9a27cf to cd7c0eb, the head of fujinet-firmware's add-google-calendar branch, which adds the CALENDAR, GCAL and ICAL network protocols. A program running on the emulated CoCo can open CALENDAR:, GCAL: and ICAL: URLs on the N: device and read a Google Calendar or iCalendar feed straight off the network device.

No emulator or frontend changes. The pin moved in all three places that have to agree — cmake/Dependencies.cmake for a source build and both flatpak manifests for a bundle build — so a source build, a flatpak and these downloads all ship the same runtime.

Built on XRoar 1.11 (GPLv3). System ROMs are not bundled (see COMPLIANCE.md); the macOS bundle is unsigned.