david/Oregon-Farmers-Market
1
0
Fork 0
Code Issues Pull requests Projects Releases 42 Packages Wiki Activity Actions
Page: Release-Process
Pages
CSV-Import-and-Export Configuration Frontend-Map-and-Filters Home Installation-and-Upgrade Market-Data-Model Market-Health Release-Process Security-and-Maintenance Shortcodes-and-Builder Troubleshooting WPML-and-Spanish-Maps
1 Release-Process
david edited this page 2026-06-16 08:47:42 -07:00
Table of Contents

Release Process

Active development happens on main.

Version Bump

Before release, bump:

  • Plugin header version in oregon-farmers-market-locator.php
  • OFML_VERSION
  • readme.txt Stable tag
  • CHANGELOG.md
  • RELEASE-NOTES.md

Verification

Run:

scripts/check-release.sh

This verifies version consistency, PHP syntax, static analysis, package contents, packaged PHP syntax, nonce/capability patterns, and focused security checks.

Packaging

Release ZIPs are generated under dist/ and should not be committed.

Forgejo Release

The release flow is:

  1. Commit release changes.
  2. Create annotated tag vX.Y.Z.
  3. Push main.
  4. Push the tag.
  5. Create a Forgejo release object.
  6. Upload dist/oregon-farmers-market-locator-vX.Y.Z.zip.
  7. Verify the release author is david and the ZIP asset is present.

Pushing a tag alone does not create a visible Forgejo Release entry on this instance.