Feature version tag

[benderl]

No description provided.

[Copilot]

🟡 Changes recommended

Production updates are disabled by default, and detached tag checkouts break branch tracking and subsequent updates.

4 open findings

• Preserve virtual train identity after tag checkout · New
• Default test mode off for production updates · New
• Require SELECTED_TAG to reference a valid tag · New
• Accept matching remote branches during validation · New

What changed in this PR

Adds tag-based virtual Release/Beta update channels and restructures update handling.

Changes:

• Builds Release/Beta version options from repository tags.
• Supports tag checkout and fallback selection.
• Adds dry-run wrappers and validation helpers.

File	Description
runs/​update_self.sh	Implements tag-based checkout and update flow.
runs/​update_available_versions.sh	Publishes tag-derived virtual version channels.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🔵 Needs a closer look

Dry-run mode currently disables production updates, and tag fetching/filtering has correctness gaps.

1 open finding

• Default test mode off for production updates

3 resolved since last review

• Preserve virtual train identity after tag checkout
• Accept matching remote branches during validation
• Require SELECTED_TAG to reference a valid tag

Previously missed (2)

In code that hasn't changed since last review

Version filter rejects valid multi-digit major versions

runs/​update_available_versions.sh:102

[2-9]+ is not a numeric “major version >= 2” check: it rejects valid future majors containing 0 or 1, such as 10.0.0 and 20.0.0. The helper still selects those tags, so the advertised train commit can come from a tag that is missing from the corresponding tag list. Match one digit from 2–9 or any multi-digit positive major in both train filters.

Fetch all tags to support standalone release and beta tags

runs/​update_self.sh:77

This fetch does not request all tags, yet the new Release/Beta paths select tags and explicitly support tag commits that may not be reachable from a fetched branch. Git's default auto-follow only obtains tags pointing into fetched histories, so a newly published standalone train tag can remain absent locally; fallback selection then chooses an old tag and an explicitly selected new tag fails validation. Fetch/prune tags here just as the versions script does.

🧠 Review effort: Balanced

[Copilot]

🟡 Changes recommended

Production updates are disabled by default, and virtual trains accept incompatible tags.

2 open findings

• Default test mode off for production updates
• Validate tags against the selected release train · New

🧠 Review effort: Balanced

[Copilot]

🟡 Changes recommended

Production updates are disabled by dry-run mode, and failure paths can leave system control paused indefinitely.

2 open findings

• Clear update_in_progress flag on update script failures · New
• Default test mode off for production updates

1 resolved since last review

• Validate tags against the selected release train

🧠 Review effort: Balanced