feat: generate changelog.xml in update stream from release descriptions #655
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description\n\nThe Joomla update stream (
updates.xml) should include changelog entries derived from Gitea release descriptions. Currently release descriptions are written as markdown in Gitea releases, but the Joomla update server expects achangelog.xmlor inline changelog data in the update stream configuration.\n\n## Requirements\n\n- Parse the release description (markdown) from Gitea releases\n- Convert to Joomla-compatible changelog XML format\n- Include in the update stream so Joomla's updater can display changelogs to users\n- Should be generated automatically as part of the auto-release workflow\n\n## Context\n\n-updates.xmlis currently generated dynamically by the MokoGitea license server\n- Release descriptions are written as conventional changelog markdown in Gitea\n- The changelog should appear in Joomla's extension update UI\n\n## References\n\n- Joomla changelog XML format:<changelogs>element in update stream\n- Current auto-release workflow:.mokogitea/workflows/auto-release.yml\n- Current update stream checks:.mokogitea/workflows/pr-check.ymlBranch created:
feature/655-feat-generate-changelog-xml-in-update-stResolved. Changes shipped:
/{owner}/{repo}/changelog.xml, parses release descriptions into Joomla<changelogs>XML format[Unreleased]→[version]in CHANGELOG.md on stable release, plus release notes update for RC releases[Unreleased]entries on every PR[Unreleased]to release descriptions for dev/fix/rc pushesmoko-platformtomokocliacross all 41 org reposbulk_workflow_push.phpandworkflow_sync.phpupdated with branch+PR fallback for protected repos