Skip to content

Sync .distignore fix to main ahead of 0.11.0 deploy retry#154

Merged
GaryJones merged 2 commits into
mainfrom
develop
Apr 25, 2026
Merged

Sync .distignore fix to main ahead of 0.11.0 deploy retry#154
GaryJones merged 2 commits into
mainfrom
develop

Conversation

@GaryJones
Copy link
Copy Markdown
Contributor

Summary

Fast-forwards main to include #153, the small .distignore cleanup that landed on develop immediately after the 0.11.0 release. The deploy to WordPress.org was about to publish .claude/, AGENTS.md, and rector.php because none of them were excluded from packaging. SVN credentials have now been refreshed; getting this commit onto main first means the upcoming workflow_dispatch of the deploy workflow against main will package the correct file set.

The git tag 0.11.0 is intentionally not being moved. The change here is build-only — it affects what's bundled, not the running plugin code — so the slight divergence between the git tag commit and the SVN tag contents is just .distignore and is invisible to plugin users.

Test plan

  • Confirm only .distignore changes in this PR.
  • After merging, gh workflow run deploy.yml --ref main and confirm the run staging output no longer mentions .claude/, AGENTS.md, or rector.php.

The 0.11.0 SVN deploy was about to publish .claude/, AGENTS.md, and
rector.php to plugin users because none of them were listed in
.distignore. They are all developer- or assistant-side configuration
that has no place in an installed plugin and would only confuse users
poking around their plugins directory. Add them so the next deploy
ships only the plugin code itself.
@GaryJones GaryJones requested a review from a team as a code owner April 25, 2026 16:58
@GaryJones GaryJones merged commit e5465f7 into main Apr 25, 2026
7 checks passed
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.

1 participant