Skip to content

Releases: johanohly/AirTrail

v2.1.1

06 Feb 13:50
Compare
Choose a tag to compare

What's Changed

🐛 Bug fixes

  • fix: stop converting flight date timezone if no time has been set by @johanohly in #174

Full Changelog: v2.1.0...v2.1.1

v2.1.0

04 Feb 15:11
Compare
Choose a tag to compare

What's Changed

🚀 Features

🐛 Bug fixes

Full Changelog: v2.0.0...v2.1.0

v2.0.0

29 Jan 16:15
bdea3d6
Compare
Choose a tag to compare

What's Changed

🚨 Custom Airports (Breaking)

In the past, AirTrail used a big static file to store all the airports available in the application. This had multiple issues; the obvious one is the size of the file, which not only needed to be embedded in the docker image, but was also sent to every visitor of the website (sounds bad, but browsers are pretty good at caching). It also made updates to the list harder, as it required a new version for each update.

It also limited you to airports that were "official", as there wasn't a way to add your own "custom" airports in the application.

This version uses a new data source for the internal airport list, which can be updated from within AirTrail. If even the new data source doesn't list the airport you want, you can now also add custom airports to the application.

The reason this release is marked as breaking, is that a very small handful (~100/~21000) of airports that were in the old list, are either absent or have changed identifier in the new (updated) source. This means that any flights to or from those few, will break the application. Please open an issue if this affected you.

The biggest ones are:

  • Kuwait International Airport
  • Jorge Chávez International Airport
  • Manas International Airport
  • Dabolim Airport
  • Hazrat Shahjalal International Airport

🚀 Features

🌟 Enhancements

🐛 Bug fixes

New Contributors

Full Changelog: v1.1.2...v2.0.0

v1.1.2

18 Nov 13:52
Compare
Choose a tag to compare

What's Changed

🐛 Bug fixes

  • fix: remove unused airport field "wiki" (saves ~1mb) by @johanohly in #143
  • fix: prevent timezone conversion for non-sensitive date value by @johanohly in #146

Full Changelog: v1.1.1...v1.1.2

v1.1.1

15 Nov 07:46
Compare
Choose a tag to compare

What's Changed

🐛 Bug fixes

  • fix: import from AirTrail JSON files by @johanohly in #132
  • fix: first weekday in datepicker is in accordance with browser by @johanohly in #141
  • fix: ignore duration provided by JetLog export by @johanohly in #124

Full Changelog: v1.1.0...v1.1.1

v1.1.0

11 Nov 12:16
Compare
Choose a tag to compare

What's Changed

🚀 Features

  • feat: respect filters across map and statistics page by @ubelhj in #104
  • feat: configuration through .env variables by @johanohly in #102

🌟 Enhancements

🐛 Bug fixes

  • fix: remove debug form on setup page by @johanohly in #106
  • fix: prevent possible date mismatches due to timezone conversions by @johanohly in #107

New Contributors

Full Changelog: v1.0.1...v1.1.0

v1.0.1

04 Nov 11:23
Compare
Choose a tag to compare

What's Changed

🐛 Bug fixes

  • fix: allow entering flight times between 00:00 and 00:59 by @johanohly in #98
  • fix: change IATA code of Chisinau International Airport by @johanohly in #97

Full Changelog: v1.0.0...v1.0.1

v1.0.0

02 Nov 19:57
Compare
Choose a tag to compare

What's Changed

🚨 Breaking Change: Improved Timezone Handling

Before v1.0.0, AirTrail converted entered local times and dates to UTC using a fixed offset for each airport. This approach often led to inaccurate timestamps because it did not account for Daylight Saving Time (DST) changes and was inaccurate for certain regions, such as much of India.

With this release, each airport now uses a timezone identifier (e.g., Europe/Copenhagen) instead of a fixed UTC offset. This shift allows AirTrail to leverage your browser’s built-in timezone database, ensuring accurate conversions that consider DST and regional differences automatically. While this update improves precision, it may cause some previously stored times to be slightly offset. For example, timestamps saved in an earlier version may now differ by an hour or more if DST wasn’t previously accounted for correctly.

Solution: If you’ve been using the import function to manage your flights, you can correct any discrepancies by reimporting your flight data. However, to do this, you’ll need to delete the previously imported flights first. This will allow the new timezone logic to be applied correctly during reimport, ensuring accurate timestamps.

Additional Import Feature: The App in the Air and JetLog importers have also been updated to include the airline for each flight, if available. This enhancement helps ensure that your flight records are more complete and accurate during import.

TL;DR: AirTrail now uses timezone identifiers for airports, fixing DST issues and improving accuracy. Previously stored times might be slightly off due to this update. To correct existing data, delete any imported flights and reimport them (if they were initially imported). Additionally, the App in the Air and JetLog importers now import the airline for each flight, if possible.

🚀 Features

  • feat: improve timezone handling by @johanohly in #85
  • feat: flight list toolbar (pagination, filters and multi-delete) by @johanohly in #88

🌟 Enhancements

🐛 Bug fixes

  • fix: handle csv cells that span multiple lines by @johanohly in #83
  • fix: page freezing when trying to search for a second flight by @johanohly in #90

Full Changelog: v0.3.2...v1.0.0

v0.3.2

19 Oct 19:36
Compare
Choose a tag to compare

What's Changed

🌟 Enhancements

  • fix: show popup when creating a new user on mobile by @johanohly in #78

🐛 Bug fixes

Full Changelog: v0.3.1...v0.3.2

v0.3.1

09 Oct 19:12
Compare
Choose a tag to compare

What's Changed

🌟 Enhancements

Full Changelog: v0.3.0...v0.3.1