Skip to content

Release history

reitti releases

Reitti is a comprehensive personal location tracking and analysis application that helps you understand your movement patterns and significant places. The name "Reitti" comes from Finnish, meaning "route" or "path".

Back to tool Latest release

All releases

12 shown

v4.0.5 Breaking risk
Notable features
  • Improved Geocoder test handling and error reporting
Full changelog

Hey reitti community! Daniel here with another bugfix release: reitti 4.0.5! 👋

This release focuses on ironing out a few more kinks, including an important fix for our "magic link" feature and some crucial improvements to geocoder testability. Your continued reports and feedback are invaluable in making reitti more reliable with each update.

Just a friendly reminder, especially if you're upgrading from v3: reitti 4.0 introduced significant breaking changes. Please ensure you've reviewed the breaking changes section in the 4.0.0 release notes and followed the upgrade guide to ensure everything runs smoothly.

What's Changed in 4.0.5 – Fixing Magic Links and Improving Geocoding!

This update brings stability enhancements and addresses a visibility issue.

Other Changes

  • Improved Geocoder Test Handling and Error Reporting
    • A fix (issue 926) has been implemented to improve how geocoder tests are handled, and crucially, to provide better error reporting. This means that if there are issues with geocoding, reitti will now be more informative about what went wrong, helping with troubleshooting and ensuring more reliable location data.
    • [See the fix by @dgraf-gh in https://github.com/dedicatedcode/reitti/pull/938]
  • Fixed: Magic Link for Latest Location Not Loading Tiles Properly
    • I've resolved a critical bug (issue 951) where "magic links" designed to show only your latest location were failing to load map tiles correctly. This meant that while the link worked, the map itself would appear blank. This issue has now been addressed, bringing full functionality back to this convenient sharing feature.
    • [See the fix by @dgraf-gh in https://github.com/dedicatedcode/reitti/pull/955]

Thank you all for your continuous support and for helping me make reitti the best it can be!

Support & Community

I genuinely value your feedback and continued support! Here are a few ways you can connect with me and the reitti community:

  • ☕ Support My Work: If you find this project useful, you can help fuel future development by buying me a coffee on Ko-fi. Every bit helps!
  • 🐛 Report Issues: Encountered a bug or have a brilliant feature suggestion? Please don't hesitate to open an issue on GitHub Issues.
  • 🗣️ Discuss on Lemmy: Join the conversation or reach out on Lemmy. I love hearing from you there!
  • 💬 Connect on Reddit: Find me and discuss related topics, or just hang out, on Reddit.
  • #️ Join us on IRC: Come chat with us live in my IRC channel #reitti on libera.chat.

Happy tracking!
Daniel

Full Changelog: https://github.com/dedicatedcode/reitti/compare/v4.0.4...v4.0.5

View release on GitHub
v4.0.4 Breaking risk

Fixes visit detection preview functionality.

Full changelog

Hey reitti community! Daniel here with another quick bugfix release: reitti 4.0.4! 👋

This release tackles an important bug that's been lurking since the major 4.0.0 update, specifically affecting the visit detection preview settings. Thanks to your feedback, we're chipping away at these issues to make reitti even more robust.

Just a friendly reminder, especially if you're upgrading from v3: reitti 4.0 introduced significant breaking changes. Please ensure you've reviewed the breaking changes section in the 4.0.0 release notes and followed the upgrade guide to ensure everything runs smoothly.

What's Changed in 4.0.4 – Getting Sensitive with Previews!

This update addresses a issue within the visit detection configuration.

Other Changes

  • Fixed: Visit Sensitivity Preview Not Working
    • I've resolved a significant bug (issue 927) where the preview functionality within the VisitDetection settings was not working correctly. This feature, which helps you fine-tune how reitti detects your visits, had unfortunately been broken since the reitti 4.0 release. With this fix, you can now reliably use the preview to adjust your visit sensitivity settings to your liking!
    • [See the fix by @dgraf-gh in https://github.com/dedicatedcode/reitti/pull/928]

Thank you all for your continued vigilance and for helping make reitti better with each update!

Support & Community

I genuinely value your feedback and continued support! Here are a few ways you can connect with me and the reitti community:

  • ☕ Support My Work: If you find this project useful, you can help fuel future development by buying me a coffee on Ko-fi. Every bit helps!
  • 🐛 Report Issues: Encountered a bug or have a brilliant feature suggestion? Please don't hesitate to open an issue on GitHub Issues.
  • 🗣️ Discuss on Lemmy: Join the conversation or reach out on Lemmy. I love hearing from you there!
  • 💬 Connect on Reddit: Find me and discuss related topics, or just hang out, on Reddit.
  • #️ Join us on IRC: Come chat with us live in my IRC channel #reitti on libera.chat.

Happy tracking!
Daniel

Full Changelog: https://github.com/dedicatedcode/reitti/compare/v4.0.3...v4.0.4

View release on GitHub
v4.0.3 Breaking risk

Minor fixes and improvements.

Full changelog

Hey reitti community! Daniel here with another quick bugfix release: reitti 4.0.3! 👋

It seems the "memories" feature has been playing a little hard to get, especially when encountering places without names. Thanks, as always, for your reports and patience as I fix these issues.

Just a friendly reminder, especially if you're upgrading from v3: reitti 4.0 introduced significant breaking changes. Please ensure you've reviewed the breaking changes section in the 4.0.0 release notes and followed the upgrade guide to ensure everything runs smoothly.

What's Changed in 4.0.3 – Further Refining Memories!

This release primarily tackles another area concerning memory generation.

Other Changes

  • Fixed: Adding Visit or Trip Blocks in Memories
    • I've resolved a bug (issue 920) that prevented users from adding visit or trip blocks within the memories feature, especially when dealing with places that didn't have names assigned to them. My apologies for the repeated oversight in this area, but I believe this fix should make the memory creation process much more robust now!
    • [See the fix by @dgraf-gh in https://github.com/dedicatedcode/reitti/pull/922]
  • Latest Translations Update
    • A big shout-out to our fantastic community translators! All the most recent language updates from Hosted Weblate are now integrated, ensuring reitti remains accessible and friendly in various languages around the world.
    • [See the update by @weblate in https://github.com/dedicatedcode/reitti/pull/907]

Thank you again for your incredible support and for helping me iron out these wrinkles to make reitti the best it can be!

Support & Community

I genuinely value your feedback and continued support! Here are a few ways you can connect with me and the reitti community:

  • ☕ Support My Work: If you find this project useful, you can help fuel future development by buying me a coffee on Ko-fi. Every bit helps!
  • 🐛 Report Issues: Encountered a bug or have a brilliant feature suggestion? Please don't hesitate to open an issue on GitHub Issues.
  • 🗣️ Discuss on Lemmy: Join the conversation or reach out on Lemmy. I love hearing from you there!
  • 💬 Connect on Reddit: Find me and discuss related topics, or just hang out, on Reddit.
  • #️ Join us on IRC: Come chat with us live in my IRC channel #reitti on libera.chat.

Happy tracking!
Daniel

Full Changelog: https://github.com/dedicatedcode/reitti/compare/v4.0.2...v4.0.3

View release on GitHub
v4.0.2 Breaking risk

Fixed memory generation failing for unnamed visits.

Full changelog

Hey reitti community! Daniel back again with another small, but important, bugfix release: reitti 4.0.2!

It's been great to see the reitti 4.0 series working so well, and as always, thank you for your ongoing feedback which helps pinpoint these smaller issues. This release addresses a specific problem that might have popped up for some of you.

Just a friendly reminder, especially if you're upgrading from v3: reitti 4.0 introduced significant breaking changes. Please ensure you've reviewed the breaking changes section in the 4.0.0 release notes and followed the upgrade guide to ensure everything runs smoothly.

What's Changed in 4.0.2 – Addressing a Memory Lane Blip!

This release focuses on resolving an issue that could affect how your memories are generated.

Other Changes

  • Fixed: Memory Creation with Unnamed Visits
    • I've resolved a bug (issue 915) where memory generation would fail if it tried to contain a visit that did not have an associated name (e.g., a non-geocoded place). This was an oversight on my part; I had addressed a similar issue in the past, but a crucial step was missed, allowing this particular edge case to slip through. Now, your memory lane should be smooth sailing, regardless of whether every visit has a formal name! by @dgraf-gh in https://github.com/dedicatedcode/reitti/pull/916

Thanks again for your continued support and for helping make reitti more robust with every release!

Support & Community

I genuinely value your feedback and continued support! Here are a few ways you can connect with me and the reitti community:

  • ☕ Support My Work: If you find this project useful, you can help fuel future development by buying me a coffee on Ko-fi. Every bit helps!
  • 🐛 Report Issues: Encountered a bug or have a brilliant feature suggestion? Please don't hesitate to open an issue on GitHub Issues.
  • 🗣️ Discuss on Lemmy: Join the conversation or reach out on Lemmy. I love hearing from you there!
  • 💬 Connect on Reddit: Find me and discuss related topics, or just hang out, on Reddit.
  • #️ Join us on IRC: Come chat with us live in my IRC channel #reitti on libera.chat.

Happy tracking!
Daniel

Full Changelog: https://github.com/dedicatedcode/reitti/compare/v4.0.1...v4.0.2

View release on GitHub
v4.0.1 Breaking risk
Notable features
  • Configurable Photon reverse geocoding radius
Full changelog

Hey reitti friends! Daniel here with a quick, but important, update! 👋

I'm releasing reitti 4.0.1, a bugfix update to address a few minor issues discovered since the major 4.0.0 release. It's great to see reitti 4.0.0 proving to be stable, and thanks to everyone's feedback, I've been able to iron out these small bumps quickly.

For those of you just joining us, or if you're upgrading from v3, please remember that reitti 4.0 introduced significant breaking changes. Don't forget to review the breaking changes section and, most critically, follow the upgrade guide to ensure a smooth transition.

What's Changed in 4.0.1 – Squashing Bugs and Subtle Improvements!

Here's what's included in this quick follow-up release:

Bugfixes

  • Fixed: Attribution Visibility on the Main Map
  • Feature: Configurable Photon Reverse Geocoding Radius
    • For those still utilizing Photon (which is still fully supported!), I've added the ability to configure the radius for reverse geocoding requests. This allows for more precise control over your geocoding results.
    • by @dgraf-gh in https://github.com/dedicatedcode/reitti/pull/905
  • Latest Translations Update
  • Fixed: Timeline Scrolling and Clicking Issues
    • I've resolved an issue where scrolling out and clicking on the month or year in the timeline wasn't behaving as expected. The timeline should now feel much smoother! Also included now, is a overlay to show the dates which would be selected if you press the element in the datepicker. Making it more easy to understand what is going on.
    • by @dgraf-gh in https://github.com/dedicatedcode/reitti/pull/910

A huge thank you to everyone who reported these issues and helped make reitti even better. Your vigilance is invaluable!

Support & Community

I genuinely value your feedback and continued support! Here are a few ways you can connect with me and the reitti community:

  • ☕ Support My Work: If you find this project useful, you can help fuel future development by buying me a coffee on Ko-fi. Every bit helps!
  • 🐛 Report Issues: Encountered a bug or have a brilliant feature suggestion? Please don't hesitate to open an issue on GitHub Issues.
  • 🗣️ Discuss on Lemmy: Join the conversation or reach out on Lemmy. I love hearing from you there!
  • 💬 Connect on Reddit: Find me and discuss related topics, or just hang out, on Reddit.
  • #️ Join us on IRC: Come chat with us live in my IRC channel #reitti on libera.chat.

Happy tracking!
Daniel

Full Changelog: https://github.com/dedicatedcode/reitti/compare/v4.0.0...v4.0.1

View release on GitHub
v4.0.0 Breaking risk
Breaking changes
  • rabbitmq fully removed
  • photon removed from default docker-compose configuration
Notable features
  • Map rebuild with MapLibre GL JS and deck.gl
  • Rewind and replay journeys
  • Aggregate view for movement patterns
View release on GitHub
v3.4.1 Maintenance

Improves Japanese font display with proper language attribute and font fallbacks, and includes translation updates from Weblate community contributors.

View release on GitHub
v3.3.0 New feature
Notable features
  • MQTT broker integration for OwnTracks
  • Dedicated GPSLogger endpoint
  • Editable memory start/end times
View release on GitHub
v3.2.1 Bug fix

Fixes statistics translation for unknown/ungeocodeded places and resolves Photon download resumption for interrupted connections in v1.3.0+. Updates default docker-compose to use Photon v1.3.0.

View release on GitHub
v3.2.0 New feature
Notable features
  • Redis cache key prefix
  • GHCR image publishing
  • BASE_PATH subdirectory support
View release on GitHub
v3.1.0 New feature
Notable features
  • Custom polygon boundaries for places
  • OwnTracks friend data support
  • Paginated data export
View release on GitHub

Beta — feedback welcome: [email protected]