Skip to content

chore: reset to 1.0.0 for the initial release#11

Merged
r00bbert merged 1 commit into
mainfrom
chore/reset-to-v1.0.0
May 21, 2026
Merged

chore: reset to 1.0.0 for the initial release#11
r00bbert merged 1 commit into
mainfrom
chore/reset-to-v1.0.0

Conversation

@r00bbert
Copy link
Copy Markdown
Contributor

@r00bbert r00bbert commented May 21, 2026

Why

Nothing has ever been tagged or released (git tag is empty, no GitHub releases), so the prior 1.0.01.1.0 version history was a phantom — the salt-fix work bumped to 1.1.0 against a 1.0.0 baseline that never actually shipped. For a debut, the first public version should simply be 1.0.0.

What

  • Version → 1.0.0 in all three places the version-consistency CI checks: plugin header, MAGICAUTH_VERSION, readme stable tag.
  • Removed the readme == 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 the 1.0.0 initial release.

Note

Still on the pre-release radar (out of scope for this PR): Tested up to: 7.0 in 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 be v1.0.0.

Summary by CodeRabbit

  • Revert
    • Plugin version reverted from 1.1.0 to 1.0.0
    • Changelog documentation updated

Review Change Stack

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.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 21, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 74ae8b05-584e-4afd-80eb-762396e35161

📥 Commits

Reviewing files that changed from the base of the PR and between 192b60c and 7714eba.

📒 Files selected for processing (2)
  • magicauth.php
  • readme.txt

📝 Walkthrough

Walkthrough

The 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.

Changes

Version Downgrade

Layer / File(s) Summary
Version constant and documentation updates
magicauth.php, readme.txt
Plugin header Version value and MAGICAUTH_VERSION constant are downgraded to 1.0.0. Readme stable tag is updated to 1.0.0 and changelog history entries are removed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop and a skip, the version takes flight,
From one-point-one down to one-point-oh bright,
The changelog fades like morning dew,
The plugin's fresh start, version true!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately reflects the main change: resetting the plugin version to 1.0.0 for the initial release, which aligns with the changes made across multiple files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/reset-to-v1.0.0

Comment @coderabbitai help to get the list of available commands and usage tips.

@r00bbert r00bbert merged commit 5b15631 into main May 21, 2026
15 checks passed
@r00bbert r00bbert deleted the chore/reset-to-v1.0.0 branch May 21, 2026 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants