Internal: Add deploy scripts - #234
Open
KingYes wants to merge 4 commits into
Open
Conversation
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio. |
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
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.
✨ PR Description
1. Problem & Context
Adds automated release workflow to handle version bumping, validation, GitHub releases, and WordPress.org deployments. Enables controlled releases from master branch by authorized actors.
2. What Changed (Where)
scripts/.github/workflows/release.yml.github/workflows/*.ymlworkflow_calltrigger to PHP linting/testingpackage.json.build-rsync-excludescripts/from production build3. How It Works
Release workflow (triggered manually with patch/minor/major bump): computes next version → validates readme changelog entry exists → bumps package.json → syncs version to plugin files → builds package → validates artifacts → creates git commit/tag → generates changelog from commits → conditionally pushes and deploys to GitHub Releases + WordPress.org SVN. Dry-run mode skips all git/deploy operations.
Helper scripts:
next-version.js(semver calculation),sync-version.js(writes version to PHP/readme),validate-readme-changelog.js(ensures changelog section + bullet points exist),validate-build-files.sh(verifies plugin files, version tags, excludes list).4. Risks
Actor whitelist (
KingYes,bainternet,arielk) requires maintenance if team changes. WordPress.org deployment uses hardcoded SVN credentials—ensureSVN_USERNAME/SVN_PASSWORDsecrets are properly scoped. Dry-run validation logic could diverge from actual deploy if scripts aren't kept in sync.Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how