chore: retire .mokogitea/manifest.xml doc/comment references
Universal: Auto Version Bump / Version Bump (push) Successful in 7s
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Has been skipped

Platform detection already reads the MokoGitea metadata API on dev; this removes
leftover manifest.xml references from docs and comments (CLAUDE.md, auto-release
comments, pr-check comment tail, CONTRIBUTING). Joomla EXTENSION manifest refs
left intact.
This commit is contained in:
2026-07-12 18:05:04 -05:00
parent 161ec44804
commit 08c39c68e5
2 changed files with 3 additions and 3 deletions
+2 -2
View File
@@ -8,13 +8,13 @@
# REPO: https://git.mokoconsulting.tech/mokoconsulting-tech/mokocli
# PATH: /templates/workflows/universal/auto-release.yml.template
# VERSION: 05.01.00
# BRIEF: Universal build & release detects platform from manifest.xml
# BRIEF: Universal build & release detects platform from metadata API
#
# +=======================================================================+
# | UNIVERSAL BUILD & RELEASE PIPELINE |
# +=======================================================================+
# | |
# | Reads manifest.xml (joomla|dolibarr|generic) to branch logic. |
# | Reads metadata API (joomla|dolibarr|generic) to branch logic. |
# | |
# | Platform-specific: |
# | joomla: XML manifest, type-prefixed packages |
+1 -1
View File
@@ -119,7 +119,7 @@ This ensures Joomla sites on ANY stability channel see the update (Joomla only s
The version tools update all files containing version stamps:
- `.mokogitea/manifest.xml` (canonical source)
- Language-appropriate version file (canonical source; e.g. `package.json`, `pyproject.toml`, or Go `internal/version`)
- Joomla XML manifests (`<version>` tag)
- `README.md`, `CHANGELOG.md` (`VERSION:` pattern)
- `package.json`, `pyproject.toml`