Skip to content

Bump version string to stable v4.x (drop beta) #60

@lewisgoddard

Description

@lewisgoddard

Maintenance item for 4.0 Stable. The version string still advertises a beta.

src/phoenix.php:27:

$settings['phoenix_version'] = 'Phoenix Procedural v4.0beta2 2026-05-09 17:23:00Z eustasy';

This is the one explicit "not stable yet" marker in the code, and it is surfaced publicly — the admin panel (src/views/html.admin.php) and the stats views (src/views/json.stats.php, html.stats.php, xml.stats.php, which emit it in $Id: … $ form) all echo $settings['phoenix_version'].

Tasks

  • Bump phoenix_version to the stable string (drop beta2) and refresh the timestamp, e.g. Phoenix Procedural v4.0 <date> eustasy.
  • Grep for any other beta/4.0beta references and update them (grep -rn beta . --include=*.php).
  • Keep the string in sync with the release tag v4.0.0.

Tagging convention

  • Going forward the project uses vMAJOR.MINOR.PATCH (v4.x.x) — so 4.0 ships as v4.0.0.
  • The most recent prior release has been renamed v.3.2.03.2.0 (release re-pointed, body preserved). Earlier history (v.3.1, 3.1.5, v.3.0, …) is left as-is — do not retag it.

Acceptance

  • No beta remains in the version string or codebase.
  • The version shown in the admin panel and stats output reads as stable v4.0 and matches the release tag v4.0.0.

Metadata

Metadata

Assignees

No one assigned

    Priority

    💚 Low

    Effort

    🍀 Bytesize

    Stage

    🚧 Blocked

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions