release: 1.0.10 (re-ship of botched 1.0.9)#27
Merged
Merged
Conversation
1.0.9 is a docs-only release that ships the listing-copy accuracy pass from #25 plus a CI fix: - Deploy workflow now reads 'Stable tag:' from readme.txt and passes it to the 10up action as VERSION. The action's default derivation uses GITHUB_REF, which under workflow_dispatch resolves to refs/heads/main and made the action try to write to tags/refs/heads/... — that's why the previous manual sync failed before committing to trunk. Reading from readme.txt works for both tag pushes and manual dispatches. Plugin code is unchanged from 1.0.8.
1.0.9 was tagged but never properly shipped: PR #26 (version bump + workflow fix) was stacked on PR #25's branch and merged into that branch instead of main. When #25's branch was auto-deleted after merge, #26's merge commit was orphaned and never reached main. The v1.0.9 tag was then cut against #25's merge commit, so trunk and tags/1.0.9 both shipped with 'Stable tag: 1.0.8' inside — which is why the listing page never updated. This release cherry-picks the orphaned #26 commit onto main and bumps to 1.0.10 so the readme polish + workflow fix actually go out. The 1.0.9 SVN tag stays in the directory as inert cruft; tag deletion is non-trivial and pointless once Stable tag points away from it. No code changes vs 1.0.8 — this is docs + CI only.
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.
Why this exists
Yesterday's 1.0.9 release didn't actually ship. Here's the post-mortem:
What this PR does
Why bump to 1.0.10 instead of fixing 1.0.9
The `tags/1.0.9/` directory in WP.org SVN already exists with the wrong content. SVN tag deletion is discouraged in the WP.org culture and provides no value once `Stable tag` points elsewhere — the bad tag becomes inert cruft. Cleaner to ship 1.0.10 and move on.
Deploy plan
After merge:
```bash
git checkout main && git pull
git tag v1.0.10 && git push origin v1.0.10
```
Both `release.yml` and `deploy-to-wp-org.yml` fire. The deploy workflow (with the fix from this PR) reads `Stable tag:` from `readme.txt` directly, so it doesn't matter whether the trigger is a tag push or a `workflow_dispatch` — version derivation goes through one code path.
Test plan