chore: bump plugin.json to 2.4.14 (match PLUGIN-CHANGELOG)#182
Merged
Conversation
PR #181 reverted PR #180 and added a PLUGIN-CHANGELOG v2.4.14 entry, but the plugin.json bump from 2.4.13 → 2.4.14 was missed during the amend pass (Edit tool blocked on a Read-required precondition that got dismissed in the noise). Result: PLUGIN-CHANGELOG advertises v2.4.14 while plugin.json still reports v2.4.13. This was caught when running /update against a vault on plugin v2.4.13 — the version-check step (read upstream plugin.json + compare) returned 'Already up to date' instead of triggering the v2.4.14 sync. One-line bump to restore consistency. No code or config change beyond the version field.
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
1 participant
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.
Follow-up to #181 — PLUGIN-CHANGELOG was bumped to v2.4.14 but plugin.json stayed at 2.4.13, so any vault on 2.4.13 hits 'Already up to date' instead of syncing the revert.
One-line bump in plugin.json. No other changes.