Pressship
https://github.com/f/pressship- Category
- Developer Tools
- Rank
- No. 1481Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- f
- GitHub
- 51 stars
- Latest release
- v0.1.12
- Date
About
Submit and release WordPress.org plugins from the command line, with built-in plugin-check and SVN publishing.
What it does
Pressship coordinates the full WordPress.org plugin delivery workflow. It authenticates through a browser session, validates project metadata, builds installable archives, inspects review state, chooses submission or release flows, manages SVN working copies, and can launch local Playground previews or a browser-based Studio workspace.
Why it's ranked here
Pressship is compelling because it joins several awkward WordPress.org procedures into one coherent workflow without replacing the official review and SVN systems. Automatic routing, dry runs, structured JSON output, managed Plugin Check setup, explicit subcommands, and a local Studio make it useful for both guided and automated publishing.
What's good
Authentication saves browser session state without reading or storing the account password. Verification can run independently from packaging, while dry runs stop before upload or SVN commit. Ignore rules support project files and repeated command-line globs. Approved releases include checkout, trunk synchronization, tag creation, and commit handling. Missing Subversion can trigger an operating-system-aware installer prompt.
Tradeoffs
The convenience carries a substantial runtime footprint. Node.js 20 or newer remains mandatory even through the WP-CLI bridge. Managed checks may also require PHP, internet access, Chromium installation, and local setup work. Approved releases need Subversion. Browser automation depends on WordPress.org page and session behavior, while official review decisions remain outside the tool.
How to use it well
Use Pressship for teams repeatedly shipping plugins through WordPress.org, especially when validation, packaging, status checks, and SVN releases currently live in separate scripts or manual checklists. Start with verification and dry-run publishing, then automate JSON-producing commands where appropriate. It does not replace WordPress.org review approval or general-purpose plugin development tooling.
Technical notes+
package.json defines an ESM Node.js package requiring Node 20+, with Commander, Playwright, Zod, Execa, archive, glob, and terminal UI dependencies. src/cli.ts registers authentication, inspection, verification, packaging, submission, release, SVN checkout, Playground, versioning, and Studio commands behind a shared error wrapper. composer.json defines a PHP 7.4+ WP-CLI package whose documented role is forwarding to the Node implementation. src/auth/login.ts drives interactive WordPress.org login through Playwright and persists browser session state after account verification. src/svn/get.ts chooses checkout or update, parses SVN metadata, and inspects trunk, assets, and tags. src/web/server.ts implements the localhost Studio server, token-checks mutating requests, coordinates plugin operations, and defaults to 127.0.0.1. src/web/jobs.ts provides cancellable in-memory jobs, event subscriptions, and recursive secret redaction.
Observed
- License
- MIT
- Primary language
- TypeScript, with a thin PHP WP-CLI bridge
- Install surfaces
- npm or npx package, plus a Composer-compatible WP-CLI package
- Interfaces
- Command-line interface and localhost browser-based Studio
- Runtime requirements
- Node.js 20+; WP-CLI bridge requires PHP 7.4+ and WP-CLI 2.8-compatible releases
- Publishing platform
- WordPress.org plugin review and SVN repositories
- Authentication
- Interactive browser login with locally saved browser session state
Read from README.md, package.json, composer.json, src/cli.ts, src/ui.ts, src/types.ts, src/svn/get.ts, src/web/jobs.ts, src/web/index.ts, src/web/ports.ts, src/web/server.ts, src/auth/login.ts, src/utils/slug.ts, src/auth/logout.ts, src/auth/whoami.ts.
What it can do
Submit WordPress.org plugins from command line
Plugin files and metadata → Plugin submission to WordPress.org repository
Release WordPress.org plugins from command line
Plugin version and release parameters → Published plugin release on WordPress.org
Perform built-in plugin validation checks
WordPress plugin code and files → Plugin compliance report and error/warning messages
Publish plugins via SVN to WordPress repository
Plugin files and version control data → Plugin files committed to WordPress.org SVN repository
Execute command line plugin deployment workflow
Terminal commands and plugin directory → Automated plugin deployment process completion
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.