Skip to content

Releases: tjcsl/tin

v2024.05.03

03 May 22:36
db0beb2

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2024.05.02...v2024.05.03


This release upgrades almost every Tin dependency, including Django, followed by many bug- and CI- fixes. Support for Django 3.2 ended last month, so this release is crucial for keeping Tin secure and up-to-date.

- Krishnan Shankar (@krishnans2006)

v2024.05.02

02 May 22:41
1b119f4

Choose a tag to compare

Full Changelog: v2024.04.23...v2024.05.02

This release adds support for Django Debug Toolbar (when in debug mode and accessed at an internal IP).

- Krishnan Shankar (@krishnans2006)

v2024.04.23

23 Apr 19:35
afb5fcd

Choose a tag to compare

Full Changelog: v2024.04.05...v2024.04.23

This release fixes and improves the submission header.

- Krishnan Shankar (@krishnans2006)

v2024.04.05

06 Apr 03:57
868d784

Choose a tag to compare

Full Changelog: v2024.04.03-3...v2024.04.05

Besides some code refactoring, this release fixes a bug with JSON responses from quiz reports.

- Krishnan Shankar (@krishnans2006)

v2024.04.03-3

04 Apr 00:18
9cf961c

Choose a tag to compare

Full Changelog: v2024.04.03-2...v2024.04.03-3

This release adds support for "maskable" icons, as defined here and here. This should improve Tin's PWA icon on a variety of systems, including Android, macOS, and ChromeOS.

- Krishnan Shankar (@krishnans2006)

v2024.04.03-2

03 Apr 17:05
9c04210

Choose a tag to compare

Full Changelog: v2024.04.03...v2024.04.03-2

This release fixes a typo in Tin's web app manifest, changing it to point to the right icons in static.

- Krishnan Shankar (@krishnans2006)

v2024.04.03

03 Apr 04:27
bac311a

Choose a tag to compare

Tin's first GitHub release 🎉

Future releases will be created when new code is ready to be deployed to production. They will be tagged in the format vYYYY.MM.DD.

This new release/tagging system is intended to help with debugging Tin deployments. Having a clear list of commits/PRs that were included in every deployment will help speed up the bug identification process in case major bugs are found in production.

However, the intention is to keep Tin in a "rolling release" schedule, which is why tags will use deployment dates and not semantic versioning.

These conventions are subject to change as Tin evolves as a project, but are expected to continue in the near future.

- Krishnan Shankar (@krishnans2006)