chore: Bump version to 2.1.4#21
Merged
Merged
Conversation
Also fixes a bug found while preparing this release: the SHIFTER_FUTURE_PUBLISH_VERSION constant used for asset cache-busting was hardcoded to 2.0.5 and never followed the plugin's actual version, so browsers/CDNs could not detect changes to the enqueued JS files across releases.
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.
Summary
Version bump for the next zip package release, plus one bug found while preparing it.
readme.txt(Stable tag), and changelog/upgrade notice sections ofreadme.txt/README.md.SHIFTER_FUTURE_PUBLISH_VERSION: this constant is passed as the$versionargument towp_enqueue_script()for cache-busting, but it was hardcoded to2.0.5regardless of the actual plugin version (confirmed still present onmainafter the Fix fatal error and no-op hook removal, harden security and safety #20 merge). Browsers/CDNs could not detect changes toeditor.js/classic-editor.jsacross any release since 2.0.5. Now set to2.1.4and should be bumped alongside the headerVersion:field going forward.Why 2.1.4 (not 2.2.0 or 3.0.0)
This release only contains the #20 audit fixes already merged to
main(no-opremove_action,uninstall.php, docs) plus this version-constant fix. No new features and no breaking changes to existing behavior — a patch release per semver.Checks run
php -l shifter-future-publish.php: pass_tests/vendor/bin/phpcs(repo's_tests/phpcs.xml): pass_tests/vendor/bin/phpstan analyse(repo's_tests/phpstan.neon, level max): no errors