Skip to content

Releases: philomena-dev/philomena

Philomena 1.2.2

04 Oct 17:40
2bf8d2e

Choose a tag to compare

What's Changed

  • Bump dependencies (particularly canary)
  • Add Phoenix.CodeReloader to listeners (fixes warning)

Full Changelog: 1.2.1-final...1.2.2

Philomena 1.2.1

20 Sep 17:45
d8da7ad

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.2.0...1.2.1-final

Philomena 1.2.0

04 Jun 10:32
1.2.0
e7cc819

Choose a tag to compare

What's Changed

  • Changed "hide" to "delete" and "unhide" to "restore" in UI for a more consistent deletion terminology (by @mdashlw in #512)
  • Automatically trigger a reindex of a tag's images when updating its category (by @mdashlw in #530)
  • Changed "Uploads" link to true_uploader_id on profile pages for mods (by @mdashlw in #531)
  • Reverted to manual formatting of tag suggestion image counts fixing flaky tests in some environments (by @MareStare in #535)
  • Fixed auto-closing reports overriding admin_id of already closed reports (by @mdashlw in #524)
  • Added a link to the user profile from user's avatar image (by @MareStare in #456)
  • Apply pending migrations and reindex if needed in the run-development script (by @MareStare in #547)
  • Auto approve images when deleting from the approval queue (by @mdashlw in #550)
    • New DB migration: approve all already deleted unapproved images
  • Added more mod logs for various mod actions (by @mdashlw in #475)
  • Fixed sorting in image navigator defaulting to id instead of first_seen_at (by @mdashlw in #473)
    • Search no longer considers first_seen_at a custom ordering, thus no longer appending sort[] params to image links
  • Introduced a new user display setting "Delay Home Images" (by @mdashlw in #479)
    • If enabled, the homepage will filter out images younger than 3 minutes and images without generated thumbnails (old behavior)
    • Defaults to true for regular users, false for staff users (backed by separate fields)
    • New DB migration: add delay_home_images and staff_delay_home_images fields to users
  • Search page now always renders the image list even if no images found in order to expose "Show Hidden" and "Show Deleted" buttons (by @mdashlw in #506)
  • Fixed Canada checks if user has multiple roles of the same resource type (by @mdashlw in #427)
    • This issue arose when granting Batch Tagging to staff users, which would override mod permissions
  • Fixed approving comments incrementing comments_posted stat twice for users (by @mdashlw in #544)
  • Fixed query params not being retained on /admin/artist_links page (by @mdashlw in #538)
  • Fixed query params not being retained on /images page (by @mdashlw in #536)
  • Visual and layout improvements to tags (by @Meow in #545)
    • Introduced two new user display settings to control the border and corner rounding of the tags
    • New DB migration: add borderless_tags and rounded_tags fields to users
  • Added icons to tag dropdowns (by @MareStare in #552)
  • Introduced a new parser field type numeric that does not allow range queries, primarily used for id fields (by @mdashlw in #525)
  • Related page now links back to the image (by @mdashlw in #557)
  • Fixed global index button on images sending you to a random place due to not specifying the id sort (by @mdashlw in #556)
  • Fixed throwing an error when clicking on the user profile image SVG (by @MareStare in #555)
  • Added robust keyboard keys normalization, replacing hardcoded magic keyCode values (by @MareStare in #546)
  • Moved commission searching to context (by @liamwhite in #408)
  • Fixed batch tag updates and mass tag reverts missing reindexes for tags and comments (by @mdashlw in #534)
  • Replaced JS code for dynamic resizing of images in media lists with CSS rules (by @Meow in #565)
  • Fixed the tag updates atomicity and deadlocks for more stable tag image counts (by @MareStare in #483)
  • Introduced a new query field filter_id that allows running filters inside image queries (by @mdashlw in #429)
  • Removed unnecessary space handling from field parsers (by @mdashlw in #543)
  • Cleanup the eslint config and use strict and stylistic lints (by @MareStare in #566)
  • Improved logging and introduced PHILOMENA_LOG env var (by @MareStare in #495)
  • Batched tag changes (by @Meow in #573)
    • Revamps the tag_changes table to represent batches of tag changes
    • Added a new table tag_change_tags to join batches with actual tag changes
    • New UI for tag changes to accomodate the new data structure
    • New DB migration: create new tables, archive the old table under tag_changes_legacy, migrate all tag changes into the new format
  • Fixed "Currently banned" status on Aliases page not respecting ban's enabled status (by @mdashlw in #581)
  • Added a confirm prompt when rejecting an artist link on profile pages (by @mdashlw in #583)
  • Fixed philomena clean script (by @MareStare in #588)
  • Better logging for S3 operations (by @MareStare in #570)
  • Fixed multiple sources not displaying properly on Safari 17 (by @stsyn in #590)
  • Added --drop-cache, compose and exec commands to philomena.sh (by @MareStare in #589)
  • Display Philomena version in footer (by @Meow)
  • Improved DNP display on tags (by @Meow)
  • Bumped OpenSearch to 3.0.0 (by @Meow)

Full Changelog: 1.1.0...1.2.0

Philomena 1.1.2

18 May 12:49
c91797a

Choose a tag to compare

  • Fixed an authorization oversight in /profiles/:id/scratchpad/edit route (thanks @mdashlw)

Philomena 1.1.1

07 May 16:09
1.1.1
47b7b2d

Choose a tag to compare

  • Bumped Caddy version to 2.10.0
  • Locked caddy-fs-s3 package to a specific version to avoid future incompatibilities

Philomena 1.1.0

07 May 15:58
1.1.0

Choose a tag to compare

From this point on, Philomena will be subject to versioning. We have historically simply kept shoving stuff to "master" branch and deploying as needed. This has caused the booru operators certain headaches when it came to booru upkeep and merging things. In many cases, to merge a booru, an operator would have to hunt for specific commits, merge them first, read migration instructions, and gradually migrate their installation through multiple steps, if they missed a month or a year of updates. No more.

This is the initial release based on the current code deployed to Derpibooru, the main user of the Philomena software. Yes I am aware that CI does not pass, that's because the current code deployed to Derpibooru didn't pin a Caddy package version and thus cannot compile the webserver container.

This shall act as the starting point for the release versioning. Releases are considered stable versions of Philomena which are safe to deploy to production.

Our versioning follows the following format: x.y.z-aaa

  • x = major release
  • y = minor release
  • z = patch release
  • aaa = optional suffix, like -beta1 or -rc1

In the future, we will also provide scripts for semi-automated version updates, under the following rules:

  • Any minor and patch release version may be updated to any newer version within the same major version
  • The last minor version of a given major version may be updated to any version within the next major release
  • Patch versions may not contain any changes to database or search indices, and may not require any migration or update scripts
  • It should be possible to roll back to any patch version within the same minor version

For example:

Okay:

  • 1.1.0 to 1.1.69
  • 1.1.0 to 1.4.1
  • 1.X.0 to 2.0.0 (where X is the last minor version of 1.x series)
  • 1.X.0 to 2.4.20 (where X is the last minor version of 1.x series)
  • 1.1.69 to 1.1.68

Not Okay:

  • 1.1.0 to 2.0.0 (if 1.1.0 is not the last minor version of 1.x series)
  • 1.X to 3.0.0
  • 2.0.0 to 1.1.0
  • 1.2.0 to 1.1.0