MokoConsulting/MokoGalleryCalendar
1
0
Fork 0
Code Issues 4 Pull Requests Releases 3 Wiki Activity

fix(release): resolve release naming and body issues #6

Merged
jmiller merged 1 commits from dev into main 2026-05-09 23:46:39 +00:00
Conversation 0 Commits 1 Files Changed 1
+46 -19
jmiller commented 2026-05-09 23:44:39 +00:00
Owner
Copy Link
Copy Source

Summary

  • Fix empty pretty name in release title (now reuses .ini-resolved name from Step 5)
  • Fix duplicate ## VERSION header in release description (strip changelog header before embedding)
  • Fix SHA-256 checksum missing (Step 8b now builds ZIP_NAME with TYPE_PREFIX to find the actual file)
  • Fix updates.xml download URL to include type prefix in filename

Expected release output after merge

  • Name: Moko Gallery Calendar 01.03.00 (plg_system_mokojgdpc-01.03.00)
  • Assets: plg_system_mokojgdpc-01.03.00.zip, plg_system_mokojgdpc-01.03.00.tar.gz
  • Body: Single ## VERSION header + changelog entries + SHA table
## Summary - Fix empty pretty name in release title (now reuses .ini-resolved name from Step 5) - Fix duplicate `## VERSION` header in release description (strip changelog header before embedding) - Fix SHA-256 checksum missing (Step 8b now builds ZIP_NAME with TYPE_PREFIX to find the actual file) - Fix updates.xml download URL to include type prefix in filename ## Expected release output after merge - **Name**: `Moko Gallery Calendar 01.03.00 (plg_system_mokojgdpc-01.03.00)` - **Assets**: `plg_system_mokojgdpc-01.03.00.zip`, `plg_system_mokojgdpc-01.03.00.tar.gz` - **Body**: Single `## VERSION` header + changelog entries + SHA table
jmiller added 1 commit 2026-05-09 23:44:39 +00:00
fix(release): resolve duplicate header, missing TYPE_PREFIX, and empty pretty name
Repo Health / Access control (push) Successful in 0s
Details
Repo Health / Release configuration (push) Failing after 3s
Details
Repo Health / Scripts governance (push) Successful in 3s
Details
Repo Health / Repository health (push) Failing after 3s
Details
Joomla Extension CI / Lint & Validate (pull_request) Failing after 4s
Details
Joomla Extension CI / Tests (PHP 8.2) (pull_request) Has been skipped
Details
Joomla Extension CI / Tests (PHP 8.3) (pull_request) Has been skipped
Details
Joomla Extension CI / Release Readiness Check (pull_request) Successful in 2s
Details
Repo Health / Access control (pull_request) Successful in 0s
Details
Secret Scanning / Gitleaks Secret Scan (pull_request) Successful in 4s
Details
PR Check / Validate PR (pull_request) Failing after 3s
Details
Repo Health / Release configuration (pull_request) Failing after 2s
Details
Repo Health / Scripts governance (pull_request) Successful in 2s
Details
Repo Health / Repository health (pull_request) Failing after 3s
Details
Build & Release / Build & Release Pipeline (pull_request) Successful in 1m1s
Details
c3e4fb7ad8 
- Output ext_name, ext_type, ext_folder from Step 5 for downstream reuse
- Step 7 now uses Step 5 outputs (includes .ini-resolved pretty name)
- Step 8b builds ZIP_NAME with TYPE_PREFIX so SHA calculation finds the file
- Strip changelog ## header before embedding to prevent duplicate version line
- updates.xml DOWNLOAD_URL now includes TYPE_PREFIX in filename

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jmiller merged commit 8906aaa3c0 into main 2026-05-09 23:46:39 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 html
HTML/template changes
 joomla
Joomla extension
 major-release
Major version release
 minor-release
Minor version release
 mokostandards
Related to MokoStandards framework
 patch-release
Patch version release
 php
PHP code
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 push-failure
Git push operation failed
 release-candidate
Release candidate build
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 type: bug
Something isn't working
 type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 version-drift
Version mismatch across files
 work-in-progress
Draft or incomplete work
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGalleryCalendar#6
Delete Branch "dev"

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?