Skip to content

v0.4.1

Choose a tag to compare

View all tags
@justin-stanley justin-stanley released this 04 Oct 20:57
· 36 commits to main since this release
v0.4.1
955c607
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

FeatherReader 0.4.1 is a follow-up to 0.4.0. The public pages now explain standard.site publications. The subscribe form can now submit the DID form of a publication URI, which browsers refused in 0.4.0.

Full engineering detail is in CHANGELOG.md.

Upgrade notes

  • No schema change and no new settings. Upgrading from 0.4.0 is a deploy, and rolling back to 0.4.0 is a redeploy. Both were rehearsed on a fork of a production volume: 0.4.1 booted with db: ok, then 0.4.0 booted on the result, also with db: ok.
  • What changes depends on FEATHERREADER_STANDARD_SITE:
    • Off: the subscribe input is the same as in 0.4.0. The landing and about pages describe publications and say this instance isn't accepting new publication subscriptions.
    • On: the pages and the subscribe form explain how to subscribe, and the input accepts at://did:….

Added

  • The website says what 0.4.0 does (#234). The landing page and /about describe standard.site publications alongside RSS feeds:

    • what a publication is;
    • what FeatherReader shows from it: title, date, link and a plain-text summary;
    • that the subscription is the same portable record as an RSS one;
    • how to subscribe.

    The subscribe form on /manage shows both accepted spellings: at://did:plc:…/site.standard.publication/… and the handle form.

Fixed

  • The DID form of a publication URI could not be submitted from a browser (#234). The subscribe input was type="url", and browsers' URL parser rejects at://did:plc:…/…: the colons in the DID are read as a port. With the flag on, the input is now type="text". A pattern still requires the address to start with http(s):// or at://, in any case and with surrounding whitespace allowed. Without it, example.com/blog would reach the server and come back as "Couldn't find a feed".

CI

  • The crate publish is now started by release-image, not by a workflow_run trigger (#233). crates.io trusted publishing refuses workflow_run, so v0.4.0's automatic crate publish failed and was finished by hand. The order is unchanged: if the upgrade-boot gate fails, no image is pushed and no crate is published.
Assets 2
Loading