Update RELEASE.MD by Ipstenu · Pull Request #458 · fairpm/fair-plugin

Ipstenu · 2026-02-25T23:17:27Z

Update release directions based on lessons from Release 1.3.0

Update release directions based on lessons from Release 1.3.0 Signed-off-by: Ipstenu (Mika Epstein) <Ipstenu@users.noreply.github.com>

github-actions · 2026-02-25T23:17:36Z

🧪 Test this PR on Playground

… streamline package registration Signed-off-by: Mika <ipstenu@halfelf.org> Signed-off-by: Mika Ipstenu Epstein <ipstenu@halfelf.org>

…r display for plugins. Introduced methods to register hooks for plugin update errors and display relevant messages in the admin interface. Signed-off-by: Mika Ipstenu Epstein <ipstenu@halfelf.org>

Signed-off-by: Mika Epstein <ipstenu@halfelf.org> Signed-off-by: Mika Ipstenu Epstein <ipstenu@halfelf.org>

cdils

A couple of minor suggestions on RELEASE.MD.

Are the other files in this PR intended?

cdils · 2026-02-25T23:50:58Z

RELEASE.MD

+3. Repeat steps 2-6 for the next RC (e.g., `1.2.0-rc2`)
+
+### If the RC is validated and ready for production:
+Proceed to the **Production Release** workflow below to merge `development` → `main` for the final release.


Shouldn't this be merge release/X.Y.Z → main ?

Or even just full stop here:

Proceed to the Production Release workflow below.

Ipstenu · 2026-02-26T14:37:29Z

Are the other files in this PR intended?

Yes. It won’t pass checks otherwise. The gitignore is because I used vim, and git kept trying to add swp files.

afragen · 2026-03-05T19:23:03Z

RELEASE.MD

+
+### Release Candidate (RC)
+A release candidate is a pre-release version intended for testing and validation before the final production release. Multiple RCs may be created and tested before the final release.
+- **Version format:** `MAJOR.MINOR.PATCH-rcN` (e.g., `1.2.0-rc1`, `1.2.0-rc2`)


I believe the usual manner is to use capital RC.

afragen · 2026-03-05T19:24:13Z

RELEASE.MD

+
+### Release Candidate (RC)
+A release candidate is a pre-release version intended for testing and validation before the final production release. Multiple RCs may be created and tested before the final release.
+- **Version format:** `MAJOR.MINOR.PATCH-rcN` (e.g., `1.2.0-rc1`, `1.2.0-rc2`)


Suggested change

- **Version format:** `MAJOR.MINOR.PATCH-rcN` (e.g., `1.2.0-rc1`, `1.2.0-rc2`)

- **Version format:** `MAJOR.MINOR.PATCH-RC#` (e.g., `1.2.0-RC1`, `1.2.0-RC2`)

I used # here instead of N as I thought it would be more readable.

afragen · 2026-03-05T19:25:10Z

RELEASE.MD

+2. Complete the following fields:
+
+    - **Use workflow from:** Select **Branch: release/X.Y.Z**
+    - **New version being released:** Enter the RC version using the format `X.Y.Z-rcN` (e.g., `1.2.0-rc1`, `1.2.0-rc2`)


Suggested change

- **New version being released:** Enter the RC version using the format `X.Y.Z-rcN` (e.g., `1.2.0-rc1`, `1.2.0-rc2`)

- **New version being released:** Enter the RC version using the format `X.Y.Z-RC#` (e.g., `1.2.0-RC1`, `1.2.0-RC2`)

afragen · 2026-03-05T19:25:39Z

RELEASE.MD

+2. Click the **Draft a new release** button.
+
+3. In the **Select tag** field:
+    - Select the tag that matches the version you just bumped to (e.g., `1.2.0-rc1`).


Suggested change

- Select the tag that matches the version you just bumped to (e.g., `1.2.0-rc1`).

- Select the tag that matches the version you just bumped to (e.g., `1.2.0-RC1`).

afragen · 2026-03-05T19:25:51Z

RELEASE.MD

+    - Create a new tag if it does not appear in the dropdown.
+    - **Target branch:** Select `development`
+
+4. In the **Release title** field, enter a title for the release (e.g., `1.2.0-rc1`).


Suggested change

4. In the **Release title** field, enter a title for the release (e.g., `1.2.0-rc1`).

4. In the **Release title** field, enter a title for the release (e.g., `1.2.0-RC1`).

afragen · 2026-03-05T19:26:14Z

RELEASE.MD

+### If additional testing iterations are needed:
+1. Continue making fixes on the `release/X.Y.Z` branch
+2. Merge fixes back to `development`
+3. Repeat steps 2-6 for the next RC (e.g., `1.2.0-rc2`)


Suggested change

3. Repeat steps 2-6 for the next RC (e.g., `1.2.0-rc2`)

3. Repeat steps 2-6 for the next RC (e.g., `1.2.0-RC2`)

afragen · 2026-03-05T19:27:22Z

RELEASE.MD

+1. Log in to Fastly and go to the Fair.pm page: https://manage.fastly.com/configure/services/0EAkUOqF5q35zrk6oobCP4
+2. From the Purge menu option, select **Purge URL**
+3. Leave subdomain blank and put in the path `/wp-json/git-updater/v1/update-api/`
+4. When prompted, purse another URL


Suggested change

4. When prompted, purse another URL

4. When prompted, purge another URL

afragen · 2026-03-05T19:30:53Z

RELEASE.MD

-4. In a new browser tab, go to the repository’s **Actions** tab and confirm all workflows have completed.
+## 9. Verify the release:
+- Visit the [Releases page](https://github.com/fairpm/fair-plugin/releases) to confirm latest release.
+- Go to `https://api.fair.pm/git-updater/v1/update-api/?slug=fair-plugin` and check 


Suggested change

- Go to `https://api.fair.pm/git-updater/v1/update-api/?slug=fair-plugin` and check

- Go to `https://api.fair.pm/git-updater/v1/update-api/?slug=fair-plugin` and check

- For development releases, go to `https://api.fair.pm/git-updater/v1/update-api/?slug=fair-plugin&channel=development` and check

Update RELEASE.MD

4afcb75

Update release directions based on lessons from Release 1.3.0 Signed-off-by: Ipstenu (Mika Epstein) <Ipstenu@users.noreply.github.com>

Ipstenu changed the base branch from main to release_1.4.0 February 25, 2026 23:17

Ipstenu self-assigned this Feb 25, 2026

Ipstenu added the documentation Improvements or additions to documentation label Feb 25, 2026

Ipstenu requested a review from cdils February 25, 2026 23:17

Ipstenu marked this pull request as ready for review February 25, 2026 23:18

Ipstenu added 4 commits February 25, 2026 15:22

Merge branch 'release_1.4.0' into docs/update-release.md

f4a1d80

Update .gitignore to exclude swap files and refactor updater logic to…

89208be

… streamline package registration Signed-off-by: Mika <ipstenu@halfelf.org> Signed-off-by: Mika Ipstenu Epstein <ipstenu@halfelf.org>

Enhance updater functionality by adding package registration and erro…

07f39f0

…r display for plugins. Introduced methods to register hooks for plugin update errors and display relevant messages in the admin interface. Signed-off-by: Mika Ipstenu Epstein <ipstenu@halfelf.org>

Github decided duplicating methods was a smart thing?

d93674f

Signed-off-by: Mika Epstein <ipstenu@halfelf.org> Signed-off-by: Mika Ipstenu Epstein <ipstenu@halfelf.org>

Ipstenu added this to the 1.4.0 milestone Feb 25, 2026

cdils requested changes Feb 25, 2026

View reviewed changes

cdils mentioned this pull request Feb 27, 2026

Update release.md for release candidate releases #450

Closed

afragen reviewed Mar 5, 2026

View reviewed changes

afragen requested changes Mar 5, 2026

View reviewed changes

	- Version format: `MAJOR.MINOR.PATCH-rcN` (e.g., `1.2.0-rc1`, `1.2.0-rc2`)
	- Version format: `MAJOR.MINOR.PATCH-RC#` (e.g., `1.2.0-RC1`, `1.2.0-RC2`)

	- New version being released: Enter the RC version using the format `X.Y.Z-rcN` (e.g., `1.2.0-rc1`, `1.2.0-rc2`)
	- New version being released: Enter the RC version using the format `X.Y.Z-RC#` (e.g., `1.2.0-RC1`, `1.2.0-RC2`)

	- Select the tag that matches the version you just bumped to (e.g., `1.2.0-rc1`).
	- Select the tag that matches the version you just bumped to (e.g., `1.2.0-RC1`).

	4. In the Release title field, enter a title for the release (e.g., `1.2.0-rc1`).
	4. In the Release title field, enter a title for the release (e.g., `1.2.0-RC1`).

	3. Repeat steps 2-6 for the next RC (e.g., `1.2.0-rc2`)
	3. Repeat steps 2-6 for the next RC (e.g., `1.2.0-RC2`)

	4. When prompted, purse another URL
	4. When prompted, purge another URL

Conversation

Ipstenu commented Feb 25, 2026

Uh oh!

github-actions bot commented Feb 25, 2026

Uh oh!

cdils left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Ipstenu commented Feb 26, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants