Skip to content

Indigo 0.6.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 06 Oct 13:48
v0.6.0
2b56ed6

What has and has not been run, plainly: everything here passes the host tests
(3957 checks under AddressSanitizer and UBSan) and builds for the 3DS in CI.
None of it has been run on an emulator or a real 3DS, including the new icon,
who liked or reposted a post, and the start-up update recovery.

Added

  • Who liked a post and who reposted it, from the post menu, as paged lists of
    people with avatars, the same as followers. This was the one thing on
    Cobalt's list that Indigo lacked.
    (#12)
  • The draft of an unsent post survives closing Indigo, or the battery running
    out. (#12)
  • A logo and a Homebrew Menu icon: an indigo bunting on a twig, in pixel art.
    tools/gen_logo.py draws them all from one set of shapes, and draws the
    24x24 small icon at its own size rather than letting it be averaged down from
    the 48x48 one. (#28,
    #29)
  • The groundwork for updating from inside Indigo (docs/UPDATE.md). Each release
    now carries update.json, a versioned indigo-<version>.3dsx and its
    .sha256. At start-up Indigo finishes or undoes an update that was
    interrupted, and keeps the old build until the new one has started. The
    screen that offers an update is not in yet; it waits on Wolfram's shared
    update module. (#27)
  • docs/PARITY.md, saying what Indigo does next to Cobalt and where each thing
    has been checked, with app-password and browser sign-in as separate rows.
    (#21)
  • Everything a Universal-DB listing needs, generated: the entry, a 256x128
    banner, and screenshots rendered from the layout code, plus
    scripts/udb-submit.sh to open the pull request in my name.
    (docs/UNIVERSAL-DB.md, #36)

Changed

  • The text-size setting now applies to post bodies.
    (#12)
  • The settings screen says reduce motion is reserved. Indigo draws no
    animation yet, so the toggle changes nothing, and the screen no longer
    implies otherwise. (#16)
  • Releases are built and published by CI from the tag, against a pinned
    Wolfram release (wolfram.ref, currently v0.26.0). scripts/release.sh only
    checks and tags, so nothing is uploaded from my machine any more.
    (#32)
  • Changes go through pull requests checked by the flow shared with the other
    four projects, and are merged by rebase.
    (#17,
    #27,
    #29)
Assets 6
Loading