lute-connect 1.5.1 #356
Merged
lute-connect 1.5.1 #356
+48
−72
Conversation
This file contains 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
|
Sorry I merged some Renovate PRs ahead of this one and it introduced merge conflicts. Since I introduced them I didn't want to make you have to resolve them. Hope you don't mind the commits on your branch! It looks good to me now, but would you like to give it one more look before I merge? |
drichar
approved these changes
Apr 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
lute-connectversion 1.5.1 grabs the document title rather than requiring the integration to pass in the site name.siteNamecan still be passed optionally, so the change is non-breaking.