feat(container)!: Update image docker.io/johly/airtrail to v1 #665
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.3.2
->v1.1.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
johanohly/AirTrail (docker.io/johly/airtrail)
v1.1.0
Compare Source
What's Changed
🚀 Features
🌟 Enhancements
🐛 Bug fixes
New Contributors
Full Changelog: johanohly/AirTrail@v1.0.1...v1.1.0
v1.0.1
Compare Source
What's Changed
🐛 Bug fixes
Full Changelog: johanohly/AirTrail@v1.0.0...v1.0.1
v1.0.0
Compare Source
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
🌟 Enhancements
🐛 Bug fixes
Full Changelog: johanohly/AirTrail@v0.3.2...v1.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.