The “Showing changes since” has been a great feature. I’m sharing it in a post-upgrade email, and I had the thought that being able to cap the endpoint might also be helpful to focus on a specific range of updates (i.e. 2.10.0 to 2.16.1).
Thanks Nick! Glad they’ve been useful.
We don’t encourage (or support, really) folks to upgrade to not-the-latest-release version, so I don’t see us adding that to the main page UI, but you can use &end_date= to noodle on that kind of this-to-that version data if you’re interested: https://www.livewhale.com/releases/all/?date=4/28/2023&end_date=9/1/2024
Ah, I should have thought to try that…
Again, my use case would be a link, post-upgrade. "Hey campus, we finished, LiveWhale is now 2.16.0, see all the updates we just got since 2.10.0. Then, say if an active faculty editor returns to campus a few months later, they aren’t seeing details about versions 2.16.1, 2.17.0, etc.
Understood about not making it a UI element. Hopefully anyone curious might see this, with full context.