{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidxs7otnb5hzz45rsfocajhoooynvu2ib5nmhcxhw6u2ivofq76rm",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mm3f7f3wgjn2"
  },
  "path": "/viewtopic.php?t=33453&p=274232#p274232",
  "publishedAt": "2026-05-17T20:50:05.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Thanks for the new 2.2.1 update. Any release notes or a hint of what _may_ break?\n>\n> Did a quick test and everything looks fine.\n\nI've never known how to do release notes, my brain is not that organized. LOL. I'm actually expecting that everything should be fine, but this is the first release I've done with my new Python 3 build system, and anything that's \"off\" would likely be very subtle. Also, I have a lot of stuff from the UXP master branch which has never been used in a Pale Moon release before (they're currently releasing security updates from a special release branch I didn't feel like using for Epyrus), so I have no firm of idea of what will happen.\n\nFrom what I can tell, everything is working as it did in the previous release, but the way I did this was... well, not the safest. The issue is that I wasn't planning to do another release for a few months, and was expecting that to be 2.3.0, and likely on the newer Python 3 branch. I wasn't really setup for another release between now and then, so what I created wound up being pretty much what I could throw together last-minute, because I figured that was better than having no binaries at all. At least people can report bugs and I can fix them this way. And since automatic updates aren't working anyway, no one will get auto-updated to this release, so that's a bonus.\n\nTruth be told, release engineering is not my strong suit. What I'm good at is building master and testing new features until they're stable enough to ship, not picking the right place to cut off a release so that stability is ideal for end users.\n\n* * *",
  "title": "Epyrus • Re: "Update failed" prompt appeared on its own",
  "updatedAt": "2026-05-17T20:50:05.000Z"
}