Updating properly to 3.0. Failed to follow my own instuctions.

keyring.php

@@ -3,7 +3,7 @@
 Plugin Name: Keyring
 Plugin URI: http://dentedreality.com.au/projects/wp-keyring/
 Description: Keyring helps you manage your keys. It provides a generic, very hookable framework for connecting to remote systems and managing your access tokens, username/password combos etc for those services. On its own it doesn't do much, but it enables other plugins to do things that require authorization to act on your behalf.
-Version: 2.0
+Version: 3.0
 Author: Beau Lebens
 Author URI: http://dentedreality.com.au
 License: GPL v2 or newer <https://www.gnu.org/licenses/gpl.txt>

readme.txt

@@ -105,6 +105,9 @@ Add files to includes/services/extended/ that either implement one of the includ
 
 == Changelog ==
 
+=  =
+*
+
 = 3.0 =
 * CHANGE: Default branch has been renamed to `trunk` to match WordPress projects. [Update your refs](https://docs.github.com/en/github/administering-a-repository/renaming-a-branch).
 * Enhancement: BREAKING: Removed delicious service (they have shut down completely). Props @sanmai.

release.md

@@ -3,7 +3,7 @@ This is a WordPress plugin, hosted primarily on GitHub. To ship a release to the
 1. Make sure the changelog in `readme.txt` is fully up to date (review commit history since last release if needed, there's a link on GitHub's releases page to do that, next to each release; https://github.com/beaulebens/keyring/releases)
 2. Update version numbers;
     - `readme.txt` (`Stable Tag:`, Chanegelog latest entry)
-    - `keyring.php` (`Version:`, `KEYRING__VERSION`)
+    - `keyring.php` (`Version:` header, `KEYRING__VERSION` constant)
 3. Update the `Tested up to:` header in `readme.txt` to the latest version of WordPress.
 4. Stage, commit, push everything up to GitHub.
 5. Create a new release at https://github.com/beaulebens/keyring/releases/new