v1.0.6

v1.0.6 Release

Not too many flashy changes in this release, but quite a few behind the scenes.

For the visible changes, the registration process has been converted to allow user activity even if they have not verified their email. This means that after registration, users are immediately signed in and can use core functionality. The only caveat is that there will be a perpetual banner above the header that requests them to verify their email. There is also a button to resend verification emails attached to this banner.

This was motivated due to our email ratelimiting that occurred when we last posted on Hacker News. Some users encountered issues with their accounts getting locked, essentially, as their account was created, but the verification email failed to send. This new workflow mitigates that.

Avatars are now available to be set by users under the account dropdown in the top right of the header. After being set, this is shown in the header and on the profile page of users. A link to a user's profile now appears in this dropdown, as well.

There is now a image of the homepage that appears on the landing page.

--

On the backend side, the Docker image size has been significantly reduced thanks to #34

The validation of the environment file is now less strict. This should some issues that have been encountered with this new safety measure.

ApiResponseOptions is now enforced in all routes, and the enum is now used for the frontend response validation.

--

As always, if there's any issues, don't hesitate to reach out by opening an issue or joining our discord server.

Full Changelog: v1.0.5...v1.0.6

Upgrade Instructions

There are no changes to the file structure or environment file in this release - no action is required on your part other than downloading the new image.

Pull changes.

git pull

Pull the new image.

docker compose pull

Restart the service.

docker compose up -d --remove-orphans