feat(cli): use manifest_read.php in client-release workflow Step 1 #76

New Issue

2026-05-24T08:26:53Z

jmiller commented

2026-05-24 08:26:53 +00:00

Summary

Replace inline sed parsing of extension name in client-release.yml Step 1 with manifest_read.php --field name.

Current (inline)

NAME=$(sed -n 's/.*<name>\([^<]*\)<\/name>.*//p' "$MANIFEST" | head -1)

Proposed

NAME=$(php /tmp/moko-platform/cli/manifest_read.php --path . --field name)

Impact

~3 lines replaced. Keeps all manifest parsing in one CLI tool.

Affected workflows

client-release.yml (Template-Client-WaaS, client-waas-clarksvillefurs)

## Summary Replace inline `sed` parsing of extension name in `client-release.yml` Step 1 with `manifest_read.php --field name`. ## Current (inline) ```bash NAME=$(sed -n 's/.*<name>$[^<]*$<\/name>.*//p' "$MANIFEST" | head -1) ``` ## Proposed ```bash NAME=$(php /tmp/moko-platform/cli/manifest_read.php --path . --field name) ``` ## Impact ~3 lines replaced. Keeps all manifest parsing in one CLI tool. ## Affected workflows - `client-release.yml` (Template-Client-WaaS, client-waas-clarksvillefurs)

jmiller commented

2026-05-24 09:16:13 +00:00

Test Proof

Run: #10354
Result: All steps passed

Step 1 now uses ext_name/ext_element from updates_xml_build.php --github-output instead of inline sed.

Implemented in client-waas-clarksvillefurs and Template-Client-WaaS.

## Test Proof **Run:** [#10354](https://git.mokoconsulting.tech/ClarksvilleFurs/client-waas-clarksvillefurs/actions/runs/10354) **Result:** All steps passed Step 1 now uses ext_name/ext_element from updates_xml_build.php --github-output instead of inline sed. Implemented in client-waas-clarksvillefurs and Template-Client-WaaS.

jmiller closed this issue

2026-05-24 09:16:13 +00:00

Sign in to join this conversation.

Priority Medium

Type Feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/mokoplatform#76