# WordPress.org release steps for Lockspire

Current plugin version: `1.1.0`
Current stable tag: `1.1.0`
Plugin slug: `lockspire`

## 1. Confirm version numbers

These two values must always match before release:

- `lockspire-smart-access-protection.php` -> `Version: 1.1.0`
- `readme.txt` -> `Stable tag: 1.1.0`

## 2. Commit trunk changes first

Use your WordPress.org SVN working copy or remote SVN URL and commit `trunk` first.

Example:

```bash
svn commit -m "Update Lockspire trunk for version 1.1.0"
```

## 3. Create the missing tag

The warning on WordPress.org appears because `Stable tag: 1.1.0` exists in `readme.txt`, but `/tags/1.1.0/` does not exist yet.

Create it with:

```bash
svn cp https://plugins.svn.wordpress.org/lockspire/trunk https://plugins.svn.wordpress.org/lockspire/tags/1.1.0 -m "Tagging version 1.1.0"
```

## 4. If you use a local SVN checkout instead

Copy `trunk` to `tags/1.1.0`, then commit:

```bash
svn copy trunk tags/1.1.0
svn commit -m "Tagging version 1.1.0"
```

## 5. Verify on WordPress.org

After the import refreshes:

- the red `Stable Tag` warning should disappear
- the yellow compatibility warning should disappear once WordPress.org reads `Tested up to: 6.9`

## 6. Future releases

For the next version, always do this order:

1. Update plugin header `Version`
2. Update `readme.txt` `Stable tag`
3. Update `readme.txt` `Tested up to` if needed
4. Commit `trunk`
5. Create matching `/tags/x.y.z/`

If `Stable tag` says `1.2.0`, then `/tags/1.2.0/` must exist in SVN.