chore: reset to 1.0.0 for the initial release#11
Conversation
Nothing has ever been tagged or released, so the prior 1.0.0/1.1.0 history is a phantom. Collapse everything currently in main into a single 1.0.0 initial release: - Version set to 1.0.0 in the plugin header, MAGICAUTH_VERSION, and the readme stable tag. - Remove the readme Changelog section — there is no shipped history to document on a debut release; a changelog returns when 1.1.0 is cut.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR downgrades the magicauth plugin version from 1.1.0 to 1.0.0 by updating the version constant in the main plugin file and synchronizing the version identifier in readme.txt. The changelog section documenting versions 1.1.0 and 1.0.0 is removed. ChangesVersion Downgrade
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Why
Nothing has ever been tagged or released (
git tagis empty, no GitHub releases), so the prior1.0.0→1.1.0version history was a phantom — the salt-fix work bumped to1.1.0against a1.0.0baseline that never actually shipped. For a debut, the first public version should simply be1.0.0.What
1.0.0in all three places the version-consistency CI checks: plugin header,MAGICAUTH_VERSION, readme stable tag.== Changelog ==section. There's no shipped history to document on an initial release; a changelog comes back when the first post-release version (1.1.0) is cut.No functional code changes — everything currently in
main(incl. the salt-fix wizard) is simply folded into the1.0.0initial release.Note
Still on the pre-release radar (out of scope for this PR):
Tested up to: 7.0in readme.txt is not a real WP version and should be corrected before submission; a live end-to-end smoke test + full Plugin Check in a real install; and a decision on PR #4. After this merges, the first release tag would bev1.0.0.Summary by CodeRabbit