Skip to content

Releases: DSAV-Dodeka/dodeka

v2.2.1

10 Jan 22:46
358b759
Compare
Choose a tag to compare

See v2.2.0 for more details on this release. This rebuilds production to match the latest commit.

v2.2.0

10 Jan 22:27
05d1e66
Compare
Choose a tag to compare

See also the changelog.

Added (backend)

  • <server>/admin/class/get_meta/{recent_number}/ (this returns the most recent classifications of each type, recent_number/2 for each type)
  • <server>/admin/class/new/ (creates a new points and training classification)
  • <server>/admin/class/modify/ (modifies a classification)
  • <server>/admin/class/remove/{class_id} (removes classification with id class_id)
  • <server>/member/get_with_info/{rank_type}/ (Will replace <server>/members/class/get/{rank_type}/, but added with different name to avoid breaking change, this also returns last_updated and whether the classification is frozen)
  • The last_updated column is now updated when new events are added.
  • (Senne) <server>/admin/update/training has been added (not yet in use by frontend) as the start of the training registration update.
  • New update_by_unique store method for updating an entire row based on a simple where condition.

Internal (backend)

  • The backend and deployment repository have been merged together, making deployment and versioning a lot easier. We now use a bunch of Nu scripts instead of shell scripts and the deployment will now use tidploy. This done in a series of commits from 4602abd to around 414bc23.
  • Logging has been much improved throughout the backend, so errors can now be properly seen. Error handling has also been improved (especially for the store module). Some common startup errors now have better messages that indicate what's wrong. Documentation has been improved and all database queries now properly catch some specific errors. See #31.

v2.2.0-rc.1

10 Jan 14:07
26dd5f2
Compare
Choose a tag to compare
v2.2.0-rc.1 Pre-release
Pre-release

This is Release Candidate 1 for v2.2.0.

v2.1.1

05 Dec 15:59
46da84a
Compare
Choose a tag to compare

See v2.1.0 on the backend for more details on the changelog and v2.2.1 for the small fix included in this release.

For a a full overview, see the CHANGELOG in the book.

v2.1.1-rc.1

05 Dec 15:28
5d0f6de
Compare
Choose a tag to compare
v2.1.1-rc.1 Pre-release
Pre-release

v2.1.0 is unreleased. v2.1.1 contains a small fix from the backend.

This is Release Candidate 1 for v2.1.1.

Only changes are related to deployment.

v2.1.0-rc.3

05 Dec 13:58
db73b7c
Compare
Choose a tag to compare
v2.1.0-rc.3 Pre-release
Pre-release

This is Release Candidate 3 for v2.1.0.

Only changes are related to deployment.

v2.1.0-rc.2

05 Dec 13:43
Compare
Choose a tag to compare
v2.1.0-rc.2 Pre-release
Pre-release

This is Release Candidate 2 for v2.1.0.

Only changes are related to deployment.

v2.1.0-rc.1

05 Dec 11:13
35800ff
Compare
Choose a tag to compare
v2.1.0-rc.1 Pre-release
Pre-release

This is Release Candidate 1 for v2.1.0.

See v2.1.0 on the backend for more details on the changelog.

For a a full overview, see the CHANGELOG in the book.

v2.0.1

25 Oct 14:23
ce55a95
Compare
Choose a tag to compare

Backend

  • Minor cleanup and fixes for the backend (including making it impossible to update email twice for same old email)

Deployment

  • It is now possible to extract the schema from the backend project to migrate the production database

v2.0.0

16 Oct 22:23
d120122
Compare
Choose a tag to compare
  • Major refactor of backend code (first DSAV-Dodeka/backend#56 and then DSAV-Dodeka/backend#59). The first got rid of the whole DbOperations and the unnecessary extra layer and was only about the database. The second completely refactored how the code was organized, separating out all the important functions relating to auth. It partially re-introduced some extra layer for database access to allow the actual application to decide on the schema. The new version is much more easily testable and does not rely on fragile mocks. Another major upside to this is that it allows for the package to be completely separated or removed in the future, without impacting the application-specific code.
  • Introduction of roles through the scope mechanism (contributions for delete role by @lalamiko7), so now someone can have a "Bestuur" role or ".ComCom" role. There are no uses for it, yet.
  • Klassementen! Instead of just loading a .json, you can now add events and update points, and even have them be hidden by a certain date (major contributions by @lalamiko7). This requires quite a few complex queries.
  • A number of dependencies have been upgraded. The most major one is v2 of Pydantic (which we use to validate all our data models), which now has a Rust core and should mean some performance boost.
  • We now do some linting on our code (using ruff)
  • Some minor tests and other general codebase improvements
  • Redis has been updated from version 6.2 to 7.2 and Postgres from 14 to 16.