Merged
Conversation
|
Review changes with Changed Files
|
Contributor
|
deltork
approved these changes
Jul 21, 2025
Collaborator
deltork
left a comment
deltork
left a comment
There was a problem hiding this comment.
Yeah this is the right time to publish 1.5.3
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
PR Goal?
We have done lots of improvements to the app, mostly stability and dependency updates, including a lot of bug fixes and migrating to Angular 19.
I think all this warrants an (overdue) patch release, so this PR creates 1.5.3.
With the CSS feature in #391, that would warrant a minor bump to 1.6.0, but I'd like to hag a tag back to the fully patched app before that new feature is in.
Feedback sought?
Agreement that this is the right time for a patch.
Priority?
high
Confidence?
high
Version change?
that's what it's all about! :)