Upgrade micropub-helper to 1.3.3, fixes support for sites with <base> tags #51
Conversation
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
|
Thanks! I’ve got a number of changes I want to make before I cut the next version, so it might be a bit before this makes it into the Chrome/Firefox extensions stores |
|
Cool! I'm naturally just running the unpacked version from the repository right now anyway, so no hurry. 😉 |
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.
I fixed micropub-helper itself but Omnibear's still not working for my site since it hasn't got the update yet. So, yeah! 😉
I tried to update package-lock.json as well, but it made a colossal amount of unrelated changes - I think because I'm on MacOS and can install
fsevents- and I noticed that package-lock.json wasn't updated in 3ca18c8 so I figured it'd be fine to do the same thing.