release

A command for releasing an approved WordPress plugin to WordPress.org. It validates the plugin, synchronizes files with WordPress.org’s SVN system, creates a version tag, and asks for confirmation before committing.

In plain words
What is it for?
Use it to publish a plugin release, including validation, trunk and tag synchronization, optional directory assets, status review, and commit.
Why use it?
It packages the approved-plugin release process into checks and explicit steps, reducing mistakes in validation, versioning, and SVN publishing. SVN is the version-control system used for approved WordPress.org plugin releases.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/automattic/pressship/release
Clone the repo
git clone --depth 1 https://github.com/Automattic/pressship
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 574 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00574
Opus 5 $0.00000 $0.00287
Sonnet 5 $0.00000 $0.00115
Haiku 4.5 $0.00000 $0.00057

Measured 2d ago against content hash c1a4798d7fbb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

website/docs/commands/release.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release

pressship release ./my-plugin --slug my-plugin

WordPress.org initial review uses a zip upload. Approved plugin releases use SVN. release keeps the approved-plugin workflow explicit and is equivalent to publish --release.

If svn is missing, Pressship detects your operating system and package manager, then asks before installing Subversion. Use --no-install-svn when you want it to fail with manual install instructions instead.

release will:

  1. verify the plugin with readme validation and Plugin Check;
  2. checkout or update https://plugins.svn.wordpress.org/<slug>;
  3. confirm the local version has not already been released as tags/<version>;
  4. sync packaged plugin files into trunk/;
  5. sync .wordpress-org/ into SVN assets/ when the folder exists;
  6. create tags/<version> from trunk;
  7. show svn status;
  8. ask for confirmation;
  9. commit the release with a generated WordPress.org SVN password.

Use --no-verify only when you intentionally want to skip readme validation and Plugin Check before committing to SVN.

If the SVN tag already exists, Pressship stops with a “No version change detected” message. Bump the plugin version before publishing again.

When running from a working copy created by pressship get, Pressship uses trunk/ as the plugin directory and the checkout root as the SVN working copy:

pressship get my-plugin ./my-plugin
cd ./my-plugin
pressship version patch
pressship publish

SVN Password

Pressship infers the SVN username from the saved WordPress.org login when possible. If no SVN password has been saved yet, it will direct you to:

https://profiles.wordpress.org/<username>/profile/edit/group/3/?screen=svn-password

Generate the password there, paste it into Pressship once, and it will be saved locally at ~/.config/pressship/svn-credentials.json for future release commits.

Options

pressship release ./my-plugin --slug my-plugin
pressship release ./my-plugin --version 1.2.3
pressship release ./my-plugin --username WpOrgUser
pressship release ./my-plugin --message "Release 1.2.3"
pressship release ./my-plugin --wp-path /path/to/wordpress
pressship release ./my-plugin --ignore "assets/**/*.mp4"
pressship release ./my-plugin --dry-run
pressship release ./my-plugin --no-verify
pressship release ./my-plugin --yes
pressship release ./my-plugin --no-install-svn

Read the full file on GitHub · 64 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 64 lines · 0 tokens per session scan A c1a4798d7fbb

Subscribe to this mod's changes

release is a command published in the GitHub repository Automattic/pressship (51 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 574 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.