Skip to content

Releases: superseriousbusiness/gotosocial

v0.14.0-rc3 Spoiled Sloth

04 Mar 11:00
f487fc5
Compare
Choose a tag to compare
Pre-release

Hi hi! Here's the third release candidate for 0.14.0 :) Please see the previous release candidate for update and migration notes, but replace rc2 with rc3 throughout. Thanks!

Detailed Changelog

  • f487fc5 [bugfix] Sanitize incoming PropertyValue fields (#2722)
  • 0b35257 [docs] Update HTTP signature docs a bit (#2721)
  • 66d9297 [bugfix/tracing] fix broken tracing due to conflicting schema url (#2712)
  • c7845c7 [chore]: Bump golang.org/x/crypto from 0.19.0 to 0.20.0 (#2716)
  • adb4cdc [chore]: Bump modernc.org/sqlite from 1.28.0 to 1.29.2 (#2718)
  • ea0efb8 [bugfix] update postgresqlstmt to correctly use postgres err hook (#2711)
  • 40ba936 [docs] Use human sizes for size limitations (#2706)
  • fcecd0c [bugfix] unwrap boosts when checking in-reply-to status (#2702)
  • c2a691f [chore] Disable the syslog long message over Unix datagram socket test on macOS (#2700)

v0.14.0-rc2 Spoiled Sloth

28 Feb 12:21
504c4f2
Compare
Choose a tag to compare
Pre-release

Look at that! This sloth is spoiled rotten! 🦥 👀

Here's the second release candidate for GoToSocial version 0.14.0 Spoiled Sloth!

What happened to the first release candidate, you say? Well, it didn't work properly. But this one does.

Release highlights

  • Account aliasing. You can now set the alsoKnownAs field on your account via the settings panel, to indicate other accounts you own. This doesn't do much now, but it's the first step towards the Move implementation for account migration coming in v0.15.0. We originally wanted to include Move in this release but it needs more testing so we pushed it back. Hang in there :)
  • Much better thread sorting. Conversation threads on both the web view and client API use a new sorting mechanism which makes them way more readable. No longer will replies in a thread be scattered all over the place.
  • Better HTTP signature support. We fixed a longstanding issue with including vs not including query parameters in signed GET requests. We now try (and accept) both methods of constructing signatures. Which leads to...
  • Improved thread fetching. You'll see far fewer "orphaned" statuses in your timeline now, and you'll see more replies on statuses from other instances.
  • Syntax highlighting for code blocks on the web UI. When you include a code block in your markdown now, and correctly indicate the language the code is written in, it will be syntax highlighted when rendered on your profile in the web UI. This requires javascript, but it's a progressive enhancement feature. Visitors to your profile with javascript turned off will just see the code block without syntax highlighting :)
  • Improved "about this instance" page, with a link to the page in the nav bar. Previously the "about this instance" page was more or less hidden. We've now surfaced it better, so you can write all your terms and conditions and instance description stuff there. Relatedly....
  • Parse instance descriptions and terms and conditions as markdown. Previously it was very difficult to properly edit these fields, because you had to read + write HTML to do so. Now they're parsed as markdown. This means you can more easily include things like blockquotes, lists, etc.
  • Big refactor of HTML templates + CSS. We did a serious rework of HTML templates to fix indentation. Previously if you did "view source" on a GoToSocial profile page, you'd see a mess of sloppily-indented HTML. With this refactor, the HTML is now nicely indented and much more readable. We also did an accessibility pass and tested our HTML with various screen readers to try to make the web view a bit less annoying to navigate.
  • First pass at a basic spam filtering system. In light of spam waves happening on the fediverse recently we took a crack at implementing a filter to drop messages identified as spam. This is still in the experimental stage, but it's included in this release so you can try it out already. See the docs for details.

Migration notes

Upgrading

To upgrade to 0.14.0-rc2 from a previous release:

Binary/tar

  1. Stop GoToSocial
  2. Untar the new release, including the web assets and html templates.
  3. Edit your config.yaml file as necessary (see below).
  4. Start GoToSocial

Docker

  1. Stop GoToSocial.
  2. Pull the new docker container (superseriousbusiness/gotosocial:0.14.0-rc2 or superseriousbusiness/gotosocial:latest)
  3. Start GoToSocial.

config.yaml

The configuration file has changed since the previous release. You can see a diff of the config file here: v0.13.0...v0.14.0-rc2#diff-c071e03510b2c57e193a44503fd9528a785f0f411497cc75841a9f8d0b1ac622

Database Migrations

⚠️ This release contains several database migrations which will run the first time you start up this new version. Be sure not to interrupt this migration process. This will take anywhere between a couple seconds and ten minutes (on slower hardware). Please be patient! ⚠️

Instance description, short description, and terms

Because we changed the way instance description, short description, and terms are parsed and stored, you will need to re-enter these in the admin settings panel. After you've updated to this version, you can just copy-paste your existing descriptions and ToC from the index and about web pages of your instance, and paste them in to the appropriate fields in the settings panel.

(Custom) CSS and HTML

The big refactor of CSS and HTML means that custom CSS from 0.13.x versions of GoToSocial will likely not work as expected on versions >= 0.14.0. The HTML structure changed a bunch, and some of the class names and whatnot have changed as well. Sorry about that! But it needed to be done. For an example of custom css using the new class names and HTML structure, see the following:

/* Theme colors */
:root {
  --acid-green: rgb(63, 255, 0);
  --magenta: rgb(153, 50, 204);
  
  /* Override */
  --orange2: var(--acid-green);
}

html, body {  
  /* Funky scroll bar */
  scrollbar-color: var(--acid-green) var(--gray1);
}

/* Instance display name */
.page-header {
  grid-column: 2;
  align-self: start;
  margin: 1rem 0 1rem 0;
  background-color: var(--gray1);
  border: 0.25rem solid var(--magenta);
  border-radius: var(--br);
}

/* Header card */
.profile .profile-header {
  background-color: var(--gray1);
  border: 0.25rem solid var(--magenta);
}

/* About + Pinned posts headers */
.profile .col-header {
  background: var(--gray1);
  border: 0.25rem solid var(--magenta);
}

.profile .about-user .col-header {
  border-bottom: none;
  margin-bottom: 0;
}

/* Change about sections */
.profile .about-user .fields, .profile .about-user .bio, .profile .about-user .accountstats {
  background: var(--gray1);
  border-left: 0.25rem solid var(--magenta);
  border-right: 0.25rem solid var(--magenta);
}

/* Fiddle around with borders on about sections */
.profile .about-user .fields .field:first-child {
  border-top: 0.25rem dashed var(--magenta);
}
.profile .about-user .fields .field {
  border-bottom: 0.25rem dashed var(--magenta);
}
.profile .about-user .accountstats {
  border-top: 0.25rem dashed var(--magenta);
  border-bottom: 0.25rem solid var(--magenta);
}

/* Statuses + threads */

/* Thread column header */
.thread .col-header {
  background: var(--gray1);
  border: 0.25rem solid var(--magenta);
}

/* Main status body */
.status, .status.expanded {
  background: var(--gray1);
  border: 0.25rem solid var(--magenta);
}

/* Code snippets */
.status .text .content pre, .status .text .content code {
  background: black;
  color: var(--white2);
}

/* Block quotes */
.status .text .content blockquote {
  background-color: black;
}

/* Media wrapper for attachments */
.status .media .media-wrapper {
  background: var(--bg-nearly-opaque);
}
.status .media .media-wrapper details .unknown-attachment .placeholder {
  border: 0.2rem dashed var(--magenta);
}

/* Polls */
.status .text .poll {
  background-color: black;
  border: 0.25rem solid var(--magenta);
}

.status .text .poll .poll-info {
  background-color: black;
}

/* Status info bars */
.status .status-info, .status.expanded .status-info {
  background: black;
}

/* Back + next links */
.backnextlinks {
  background: var(--gray1);
  padding: 0.5rem;
  border: 0.25rem solid var(--magenta);
  border-radius: var(--br);
}

.page-footer {
  margin-top: 2rem;
  background-color: var(--gray1);
  border-top: 0.25rem solid var(--magenta);
}

Detailed changelog

Changelog for 0.13.0 vs 0.14.0-rc2. Some changes mentioned below may have already been included in 0.13.x releases.

Features / Performance

Read more

v0.14.0-rc1 Spoiled Sloth

28 Feb 10:25
f29d429
Compare
Choose a tag to compare
Pre-release

Whoops! We borked this release candidate. You should use v0.14.0-rc2 instead!

v0.13.3 Spideriest Sloth 2: The re-slothening

15 Feb 13:18
Compare
Choose a tag to compare

Hi everyone! This here's a security + bugfix release for GoToSocial!

Similar to the v0.13.2 release, this one closes a couple gaps with regard to ensuring that models of remote Activities or Objects can't be modified by Actors who don't own the Activity or Object.

It also fixes a couple different bugs with regard to your instance trying to dereference accounts who've blocked you, or whose instances have blocked you, leading to less weird-looking behavior from the user's side :)

Based on the changes included, Bookwyrm federation should hopefully work a little better now as well, but we haven't tested this.

If you're running on v0.13.2 or below, you should update to this release as soon as you have the time. There are no database migrations or frontend file changes, so this should be fairly easy!

Thanks!

Migration notes

Upgrading

See the release notes for 0.13.0 but replace 0.13.0 with 0.13.3 throughout.

config.yaml

No changes since 0.13.2, see 0.13.0 for migration notes from versions < 0.13.0.

Database Migrations

No changes since 0.13.2, see 0.13.0 for migration notes from versions < 0.13.0.

Detailed Changelog

  • fb3e3ca [chore] also allow text/xml in place of application/xml (#2640)
  • b9013a8 [bugfix] add stricter checks during all stages of dereferencing remote AS objects (#2639)
  • a3aa604 [bugfix] Don't return Account or Status if new and dereferencing failed, other small fixes (#2563)
  • ad6f756 [bugfix] Don't return Internal Server Error when searching for URIs that don't return AP JSON (#2550)
  • 1188971 [feature] Allow "charset=utf8" in incoming AP POST requests (#2564)
  • 5d44ad7 [chore] chore rationalise http return codes for activitypub handlers (#2540)

v0.13.2 Spideriest Sloth

06 Feb 12:12
Compare
Choose a tag to compare

Release highlights

Fixes some issues where remote accounts could potentially imitate other accounts in order to deliver a subset of activities to a GtS inbox as those accounts. See post https://gts.superseriousbusiness.org/@gotosocial/statuses/01HNZ5GF2EM5M899B7RKXYNMH9 for more details.

This is a recommended security update over anything 0.13.1 and below. You should update your instance when time permits.

Migration notes

Upgrading

See the release notes for 0.13.0 but replace 0.13.0 with 0.13.2 throughout.

config.yaml

No changes since 0.13.1, see 0.13.0 for migration notes from versions < 0.13.0.

Database Migrations

No changes since 0.13.1, see 0.13.0 for migration notes from versions < 0.13.0.

Detailed Changelog

  • f5314c0 [bugfix] Ensure activities sender always = activities actor (#2608)

v0.13.1 Spiderier Sloth

10 Jan 13:21
Compare
Choose a tag to compare

Release highlights

Fixes a couple small issues with poll vote counts and poll expiry, and an issue where domain blocks were sometimes not being properly enforced when deeper- and higher-level domain blocks were used in combination (eg., when combining blocks for say example.org, bad.example.org, also-bad.example.org).

Migration notes

Upgrading

See the release notes for 0.13.0 but replace 0.13.0 with 0.13.1 throughout. Easy peasy!

config.yaml

No changes since 0.13.0, see 0.13.0 for migration notes from versions < 0.13.0.

Database Migrations

No changes since 0.13.0, see 0.13.0 for migration notes from versions < 0.13.0.

Detailed Changelog

  • ccecf5a [bugfix] fix higher-level explicit domain rules causing issues with lower-level domain blocking (#2513)
  • d5c305d [bugfix] misc dereferencer fixes (#2475)
  • 1c56192 [feature] Log pubKeyID for http-signed requests (#2501)
  • f33d05c [bugfix] fix check for closed poll to account for non-zero closed time but in the future (#2486)
  • b141500 [bugfix] fix poll total vote double count (#2464)

v0.13.0 Spider Sloth 🕷️

15 Dec 14:50
f4fcffc
Compare
Choose a tag to compare

Spider Sloth, Spider Sloth, does whatever a .... sloth does?

Release highlights

  • Create, view, and vote in polls. It's been a while in the making but GoToSocial now has support for polls, aka Question activity types. You can create, view, and vote in polls using your client of choice.
  • Show unsupported media placeholders in incoming posts, where media could not be downloaded (temporarily or otherwise). No more dropped media on posts! You'll instead now get a link to the media on the originating instance, that you can click through in your (mobile) browser.
  • Mute threads that you're being overwhelmed by. Notifications for replies, likes, and boosts in that thread will no longer be generated.
  • Media cleanup scheduling. Previously media scheduling took place every night at 12am. With the new media scheduling settings in the config, you can customize the schedule to run it at different times and frequencies. https://docs.gotosocial.org/en/latest/admin/media_caching/#cleanup
  • Support for setting instance language . You can use the new instance-languages setting to indicate one or more primary languages for your instance. https://docs.gotosocial.org/en/latest/configuration/instance/
  • Support for language tags on posts. Language of posts is now correctly federated in and out of your instance. The language of posts is also shown on the web view of statuses and threads.
  • Gather and expose prometheus format metrics. You can now expose a /metrics endpoint to allow a Prometheus instance to scrape metrics about Go runtime memory usage, http request and database metrics, and more. https://docs.gotosocial.org/en/latest/advanced/metrics/

Migration notes

Error #01: authentication NOT PASSED for public key

You will see lots of errors in your logs now that look like this. This is normal, and not a new bug! Previously, we were not surfacing these authentication errors, and now we are. They are caused by #894, which we will fix some time in the new year. Again, not a new bug. This will not effect normal running of your instance.

Upgrading

To upgrade to 0.13.0 from a previous release:

Binary/tar

  1. Stop GoToSocial
  2. Untar the new release, including the web assets and html templates.
  3. Edit your config.yaml file as necessary (see below).
  4. Start GoToSocial

Docker

  1. Stop GoToSocial.
  2. Pull the new docker container (superseriousbusiness/gotosocial:0.13.0 or superseriousbusiness/gotosocial:latest)
  3. Start GoToSocial.

config.yaml

The configuration file has changed since the previous release. You can see a diff of the config file here: v0.12.2...v0.13.0#diff-c071e03510b2c57e193a44503fd9528a785f0f411497cc75841a9f8d0b1ac622

Database Migrations

This release contains several database migrations which will run the first time you start up this new version. Be sure not to interrupt this migration process. This will take anywhere between a couple seconds and ten minutes (on slower hardware). Please be patient!

Detailed Changelog

Features + performance

Bugfixes

  • [bugfix] serialize instance terms via API by @tsmethurst in #2293
  • [bugfix/frontend] Export/import CSV correctly by @tsmethurst in #2294
  • [bugfix] allow store smaller PNG image than 261 bytes (#2263) by @KEINOS in #2298
  • [bugfix/frontend] Add nosubmit option to form fields; use it when instance custom CSS disabled by @tsmethurst in #2290
  • [bugfix] Extract description as summary first, fall back to name by @tsmethurst in #2303
  • [bugfix] Allow blocked accounts to show in precise search by @tsmethurst in #2321
  • [bugfix] Relax Mention parsing, allowing either href or name by @tsmethurst in #2320
  • Remove account_suspended_at_idx to resolve slow query issues by @Sentynel in #2310
  • [bugfix] fix poll vote count responses on client and fedi API vote creation by @NyaaaWhatsUpDoc in #2343
  • [bugfix] actually decrement votes during poll vote delete ... by @NyaaaWhatsUpDoc in #2344
  • [bugfix/docs] Poll api fixups + swagger docs by @tsmethurst in #2345
  • [bugfix] Don't try to update suspended accounts by @tsmethurst in #2348
  • [chore/bugfix/horror] Allow expires_in and poll choices to be parsed from strings by @tsmethurst in #2346
  • [bugfix] support endless polls, and misskey's' method of inferring expiry in closed polls by @NyaaaWhatsUpDoc in #2349
  • [bugfix] Update poll delete/update db queries by @tsmethurst in #2361
  • [bugfix] process account delete side effects in serial, not in parallel by @tsmethurst in #2360
  • [bugfix] self-referencing collection pages for status replies by @NyaaaWhatsUpDoc in #2364
  • [bugfix] Add Actor to outgoing poll vote Create; other fixes by @tsmethurst in #2384
  • [bugfix] Don't copy ptr fields in caches by @tsmethurst in #2386
  • [bugfix] Correctly handle range > content-length by @Jadeiin in #2395
  • [bugfix] Update exif-terminator (fix png issue) by @tsmethurst in #2391
  • [bugfix] always go through status parent dereferencing on isNew, even on data-race by @NyaaaWhatsUpDoc in #2402
  • [bugfix] return 400 Bad Request on more cases of malformed AS data by @NyaaaWhatsUpDoc in #2399
  • [bugfix] in fedi API CreateStatus(), handle case of data-race and return early by @NyaaaWhatsUpDoc in #2403
  • [bugfix/chore] Announce reliability updates by @tsmethurst in #2405
  • [bug] Fix an import statement in the gen template by @daenney in #2426
  • [bugfix] Fix wrong notification type sent for poll end by @tsmethurst in #2429
  • [bugfix] Fix web media not showing as sensitive by @tsmethurst in #2433
  • [bugfix] Ensure pre renders as expected, fix orderedCollectionPage by @tsmethurst in #2434
  • [bugfix] Narrow search scope for accounts starting with '@'; don't LOWER SQLite text searches by @tsmethurst in #2435
  • [bugfix] Make screenreaders read out Language of posts properly by @tsmethurst in #2436
  • [bugfix] ensure the 'Closing' flag doesn't get cached by @NyaaaWhatsUpDoc in #2443
  • [bugfix] pol...
Read more

v0.13.0-rc2

12 Dec 15:02
d0bb8f0
Compare
Choose a tag to compare
v0.13.0-rc2 Pre-release
Pre-release

Hiya! Here's the second release candidate for 0.13.0!

For installation / migration instructions, please see the release notes for the RC1, but replace rc1 with rc2 throughout:

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.13.0-rc1

Happy bug hunting!

Detailed Changelog

Bugfixes

  • d0bb8f0 [bugfix] Let templates deref pointers, as a treat (#2448)
  • ac48192 [bugfix] poll vote count fixes (#2444)
  • 2191c7d [bugfix] ensure the 'Closing' flag doesn't get cached (#2443)
  • bca9b2c [bugfix] Make screenreaders read out Language of posts properly (#2436)
  • 3f070a4 [bugfix] Narrow search scope for accounts starting with '@'; don't LOWER SQLite text searches (#2435)
  • d60edf7 [bugfix] Ensure pre renders as expected, fix orderedCollectionPage (#2434)
  • cc91ea0 [bugfix] Fix web media not showing as sensitive (#2433)
  • c6d6fec [bugfix] Fix wrong notification type sent for poll end (#2429)
  • 455064f [bug] Fix an import statement in the gen template (#2426)

Chores / version bumps

  • cd16113 [chore]: Bump github.com/KimMachineGun/automemlimit from 0.3.0 to 0.4.0 (#2440)
  • 9b03840 [chore]: Bump github.com/miekg/dns from 1.1.56 to 1.1.57 (#2439)
  • cdeba94 [chore]: Bump golang.org/x/oauth2 from 0.13.0 to 0.15.0 (#2438)
  • a968a03 [chore]: Bump github.com/coreos/go-oidc/v3 from 3.7.0 to 3.9.0 (#2442)
  • 4779aec [chore] Run ANALYZE for SQLite after latest migrations (#2427)
  • dacfd41 [chore/frontend] Refactor status templates slightly, put polls behind CWs if present (#2419)
  • 18d850e [chore]: Bump go.opentelemetry.io/otel/exporters/prometheus (#2412)
  • ca1a581 [chore]: Bump github.com/tdewolff/minify/v2 from 2.20.7 to 2.20.9 (#2416)
  • bdc43a9 [chore]: Bump github.com/minio/minio-go/v7 from 7.0.63 to 7.0.65 (#2415)
  • b576fbb [chore]: Bump golang.org/x/crypto from 0.15.0 to 0.16.0 (#2413)
  • bffc67d [chore]: Bump github.com/gorilla/feeds from 1.1.1 to 1.1.2 (#2414)

Docs

  • 5556767 [docs] Change configuration creation instructions (#2408)

v0.13.0-rc1

01 Dec 15:00
0e2c342
Compare
Choose a tag to compare
v0.13.0-rc1 Pre-release
Pre-release

Well well well, look what the sloth dragged in... the first release candidate for v0.13.0, Spider Sloth.

Release highlights

  • Create, view, and vote in polls. It's been a while in the making but GoToSocial now has support for polls, aka Question activity types. You can create, view, and vote in polls using your client of choice.
  • Show unsupported media placeholders in incoming posts, where media could not be downloaded (temporarily or otherwise). No more dropped media on posts! You'll instead now get a link to the media on the originating instance, that you can click through in your (mobile) browser.
  • Mute threads that you're being overwhelmed by. Notifications for replies, likes, and boosts in that thread will no longer be generated.
  • Media cleanup scheduling. Previously media scheduling took place every night at 12am. With the new media scheduling settings in the config, you can customize the schedule to run it at different times and frequencies. https://docs.gotosocial.org/en/latest/admin/media_caching/#cleanup
  • Support for setting instance language . You can use the new instance-languages setting to indicate one or more primary languages for your instance. https://docs.gotosocial.org/en/latest/configuration/instance/
  • Support for language tags on posts. Language of posts is now correctly federated in and out of your instance. The language of posts is also shown on the web view of statuses and threads.
  • Gather and expose prometheus format metrics. You can now expose a /metrics endpoint to allow a Prometheus instance to scrape metrics about Go runtime memory usage, http request and database metrics, and more. https://docs.gotosocial.org/en/latest/advanced/metrics/

Migration notes

Upgrading

To upgrade to 0.13.0-rc1 from a previous release:

Binary/tar

  1. Stop GoToSocial
  2. Untar the new release, including the web assets and html templates.
  3. Edit your config.yaml file as necessary (see below).
  4. Start GoToSocial

Docker

  1. Stop GoToSocial.
  2. Pull the new docker container (superseriousbusiness/gotosocial:0.13.0-rc1 or superseriousbusiness/gotosocial:latest)
  3. Start GoToSocial.

config.yaml

The configuration file has changed since the previous release. You can see a diff of the config file here: v0.12.2...v0.13.0-rc1#diff-c071e03510b2c57e193a44503fd9528a785f0f411497cc75841a9f8d0b1ac622

Database Migrations

This release contains several database migrations which will run the first time you start up this new version. Be sure not to interrupt this migration process. This will take anywhere between a couple seconds and ten minutes (on slower hardware). Please be patient!

Detailed Changelog

Feature / performance

Bugfixes

  • [bugfix/frontend] Add nosubmit option to form fields; use it when instance custom CSS disabled by @tsmethurst in #2290
  • [bugfix] serialize instance terms via API by @tsmethurst in #2293
  • [bugfix/frontend] Export/import CSV correctly by @tsmethurst in #2294
  • [bugfix] allow store smaller PNG image than 261 bytes (#2263) by @KEINOS in #2298
  • [bugfix] Extract description as summary first, fall back to name by @tsmethurst in #2303
  • [bugfix] Allow blocked accounts to show in precise search by @tsmethurst in #2321
  • [bugfix] Relax Mention parsing, allowing either href or name by @tsmethurst in #2320
  • [bugfix] fix poll vote count responses on client and fedi API vote creation by @NyaaaWhatsUpDoc in #2343
  • [bugfix] actually decrement votes during poll vote delete ... by @NyaaaWhatsUpDoc in #2344
  • [bugfix/docs] Poll api fixups + swagger docs by @tsmethurst in #2345
  • [bugfix] Don't try to update suspended accounts by @tsmethurst in #2348
  • [chore/bugfix/horror] Allow expires_in and poll choices to be parsed from strings by @tsmethurst in #2346
  • [bugfix] support incoming endless polls, and misskey's' method of inferring expiry in closed polls by @NyaaaWhatsUpDoc in #2349
  • [bugfix] Update poll delete/update db queries by @tsmethurst in #2361
  • [bugfix] process account delete side effects in serial, not in parallel by @tsmethurst in #2360
  • [bugfix] self-referencing collection pages for status replies by @NyaaaWhatsUpDoc in #2364
  • [bugfix] Add Actor to outgoing poll vote Create; other fixes by @tsmethurst in #2384
  • [bugfix] Don't copy ptr fields in caches by @tsmethurst in #2386
  • [bugfix] Correctly handle range > content-length by @Jadeiin in #2395
  • [bugfix] Update exif-terminator (fix png issue) by @tsmethurst in #2391
  • [bugfix] always go through status parent dereferencing on isNew, even on data-race by @NyaaaWhatsUpDoc in #2402
  • [bugfix] return 400 Bad Request on more cases of malformed AS data by @NyaaaWhatsUpDoc in #2399
  • [bugfix] in fedi API CreateStatus(), handle case of data-race and return early by @NyaaaWhatsUpDoc in #2403
  • [bugfix/chore] Announce reliability updates by @tsmethurst in #2405

Chores and version bumps

Read more

v0.12.2 Spaghettiest Sloth

10 Nov 16:49
Compare
Choose a tag to compare

'Ey up! Another 0.12 series bugfix release!

We fixed an issue where remote accounts that were suspended via targeted suspensions in the admin API could be later marked as unsuspended. This means that the suspended account had all their relationships / media / statuses etc deleted, as normal, but these might end up being repopulated later on if you interacted with the account again.

If you suspended any remote accounts from your instance via a targeted suspension in the admin settings panel, since 0.12.0, you may need to suspend these accounts again after updating to this release.

Note: This issue only affects remote accounts that were suspended in that particular way (targeted via the admin API). Domain blocks (and accounts suspended as part of a domain block) are not affected by the bug, nor are local accounts suspended via the admin API.

So there you go!

For detailed release notes, instructions, and warnings, please follow the 0.12.0 release notes and just replace 0.12.0 with 0.12.2 throughout. Thanks! Enjoy!

Changelog

  • 096c517 [bugfix] Don't try to update suspended accounts (#2348)