airano-ir
43fd2201a0
Settings fixes: - MAX_SITES_PER_USER, USER_RATE_LIMIT_PER_MIN/HR now read from DB settings table (DB > ENV > default), so dashboard/settings changes apply without restart. Sync cache refreshed on every save or delete. - /api/me reports the live DB value for max_sites_per_user. Admin improvements: - Admin users bypass per-user rate limiting entirely (role=admin or ADMIN_EMAILS). - Admin Overview now shows platform stats: registered users, new users (7d), total user sites, available tools. Plugin cleanup: - Appwrite and Directus plugins removed from the active registry (8 plugins now: WordPress, WooCommerce, WordPress Specialist, Gitea, n8n, Supabase, OpenPanel, Coolify). Plugin code is retained for future re-enabling. - Settings page plugin visibility list updated to match. Mobile onboarding: - Stepper steps on narrow viewports stack vertically with correct full border and rounded corners on each step. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
133 lines
3.9 KiB
Markdown
133 lines
3.9 KiB
Markdown
# Releasing v2.10.3 to wordpress.org via SVN — DONE 2026-05-10
|
|
|
|
**Status (2026-05-10):**
|
|
- ✅ trunk committed at `r3527909` (`svn ci`-ed by maintainer)
|
|
- ✅ assets committed at `r3527917` (icon-128/256, banner-772x250 / 1544x500)
|
|
- ✅ tag `2.10.3` committed at `r3527918`
|
|
- ✅ legacy slug `airano-mcp-seo-bridge` updated to v1.3.1 at
|
|
`r3527927/r3527928` with migration notice pointing here
|
|
|
|
Live page: <https://wordpress.org/plugins/airano-mcp-bridge/>
|
|
|
|
The rest of this file is the original runbook, kept as reference for
|
|
future releases.
|
|
|
|
---
|
|
|
|
---
|
|
|
|
## What is already staged for you
|
|
|
|
A working copy is checked out at
|
|
`wordpress-plugin/airano-mcp-bridge-wporg-svn/` (gitignored). The three
|
|
plugin files have been copied into `trunk/` and `svn add`-ed:
|
|
|
|
```
|
|
A trunk/README.md
|
|
A trunk/airano-mcp-bridge.php
|
|
A trunk/readme.txt
|
|
```
|
|
|
|
The files are byte-identical to
|
|
`wordpress-plugin/airano-mcp-bridge-wporg/airano-mcp-bridge/`, which is
|
|
the version that just passed review.
|
|
|
|
---
|
|
|
|
## Step 1 — confirm credentials
|
|
|
|
If the approval email landed less than an hour ago, wait until the hour
|
|
is up. Then verify your SVN password at:
|
|
|
|
https://profiles.wordpress.org/me/profile/edit/group/3/?screen=svn-password
|
|
|
|
The SVN username is your wordpress.org login: `airano` (case-sensitive).
|
|
|
|
---
|
|
|
|
## Step 2 — commit the initial release to trunk
|
|
|
|
```bash
|
|
cd wordpress-plugin/airano-mcp-bridge-wporg-svn
|
|
|
|
svn ci -m "Initial release v2.10.3"
|
|
# → SVN will prompt for username (airano) and password the first time.
|
|
# Tick "store password" if you trust the machine.
|
|
```
|
|
|
|
Wait for the response. A successful commit ends with `Committed revision XXXXXXX.`
|
|
|
|
---
|
|
|
|
## Step 3 — tag the release
|
|
|
|
wp.org expects every released version to also exist as a tag under
|
|
`tags/<version>/`. The Stable Tag in `readme.txt` already points to
|
|
`2.10.3`, so this tag is what `wp.org` actually serves to users.
|
|
|
|
```bash
|
|
# Still inside wordpress-plugin/airano-mcp-bridge-wporg-svn/
|
|
svn cp trunk tags/2.10.3
|
|
svn ci -m "Tag 2.10.3"
|
|
```
|
|
|
|
After this, `https://wordpress.org/plugins/airano-mcp-bridge/` will start
|
|
serving v2.10.3 within a few minutes.
|
|
|
|
---
|
|
|
|
## Step 4 — verify on wp.org
|
|
|
|
- Plugin page: <https://wordpress.org/plugins/airano-mcp-bridge/>
|
|
- Latest tag: <https://plugins.svn.wordpress.org/airano-mcp-bridge/tags/2.10.3/>
|
|
- Trunk: <https://plugins.svn.wordpress.org/airano-mcp-bridge/trunk/>
|
|
|
|
The "Tested up to" badge, version number, and changelog should all show
|
|
2.10.3.
|
|
|
|
---
|
|
|
|
## Optional but recommended — plugin assets
|
|
|
|
Plugin assets (icon, banner, screenshots) live in the SVN `assets/`
|
|
directory at the same level as `trunk/` — NOT inside `trunk/assets/`.
|
|
|
|
Required filenames (any of):
|
|
```
|
|
assets/icon-128x128.png (or .jpg / icon.svg)
|
|
assets/icon-256x256.png (high-DPI)
|
|
assets/banner-772x250.png (header image, listing card)
|
|
assets/banner-1544x500.png (high-DPI header)
|
|
assets/screenshot-1.png (matched by readme.txt "== Screenshots ==" entries)
|
|
assets/screenshot-2.png
|
|
```
|
|
|
|
To upload after creating them locally:
|
|
```bash
|
|
cd wordpress-plugin/airano-mcp-bridge-wporg-svn
|
|
cp /path/to/icon-256x256.png assets/
|
|
cp /path/to/banner-1544x500.png assets/
|
|
svn add assets/icon-256x256.png assets/banner-1544x500.png
|
|
svn ci -m "Add plugin assets — icon + banner"
|
|
```
|
|
|
|
Spec: <https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/>
|
|
|
|
---
|
|
|
|
## Optional — close the old slug
|
|
|
|
The old slug `airano-mcp-seo-bridge` (the SEO-only ancestor) is still
|
|
live. After v2.10.3 of the new slug is on the directory, you have two
|
|
options:
|
|
|
|
**(a) Push a final 1.x release to the old slug** that simply prints an
|
|
admin notice ("This plugin is now Airano MCP Bridge — please install
|
|
that and deactivate this one"). Less disruptive for existing users.
|
|
|
|
**(b) Email `plugins@wordpress.org`** asking to close the old slug as
|
|
"author request — superseded by airano-mcp-bridge". Faster.
|
|
|
|
Either is fine. Do this *after* the new slug is live and you've
|
|
confirmed at least one install path works.
|