MokoConsulting/MokoOnyx
1
0
Fork 0
Code Issues 10 Pull Requests Releases 5 Wiki Activity

fix(ci): new version bump protocol � release as-is, bump dev after #34

Merged
jmiller merged 3 commits from dev into main 2026-05-16 17:39:28 +00:00
Conversation 0 Commits 3 Files Changed 3
+63 -53
jmiller commented 2026-05-16 17:39:13 +00:00
Owner
Copy Link
Copy Source
No description provided.
jmiller added 3 commits 2026-05-16 17:39:13 +00:00
Merge pull request 'chore: cascade main → dev (f0c0730) [skip ci]' (#33) from main into dev 29cc7a66da
chore(version): bump 02.02.00 → 02.03.00 (minor) [skip ci] 3f3be17600 
Post-release dev bump per protocol.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
fix(ci): change version bump protocol — release as-is, bump dev after
Joomla: Repo Health / Access control (push) Successful in 1s
Details
Joomla: Repo Health / Release configuration (push) Failing after 3s
Details
Joomla: Repo Health / Scripts governance (push) Successful in 2s
Details
Joomla: Repo Health / Repository health (push) Failing after 3s
Details
Joomla: Extension CI / Release Readiness Check (pull_request) Failing after 3s
Details
Universal: Secret Scanning / Gitleaks Secret Scan (pull_request) Successful in 4s
Details
Universal: PR Check / Branch Policy (pull_request) Successful in 2s
Details
Joomla: Repo Health / Access control (pull_request) Successful in 0s
Details
Joomla: Repo Health / Release configuration (pull_request) Failing after 3s
Details
Joomla: Repo Health / Scripts governance (pull_request) Successful in 3s
Details
Joomla: Repo Health / Repository health (pull_request) Failing after 3s
Details
Universal: PR Check / Validate PR (pull_request) Successful in 20s
Details
Joomla: Extension CI / Lint & Validate (pull_request) Failing after 52s
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 / PHPStan Analysis (pull_request) Has been skipped
Details
Universal: Build & Release / Build & Release Pipeline (pull_request) Successful in 15s
Details
a784d871df 
- Step 1b no longer bumps main before release; it only promotes the
  CHANGELOG [Unreleased] section to the release version
- Step 11 now bumps dev to next minor AFTER recreating from main
- Releases use the version already on main (set during dev cycle)

Protocol: dev gets bumped AFTER merge to main, not before.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jmiller merged commit 48f1cc5e24 into main 2026-05-16 17:39:28 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention needed
 html
HTML template changes
 javascript
JavaScript code changes
 joomla
Joomla extension or component
 major-release
Major version release
 minor-release
Minor version release
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 patch-release
Patch version release
 php
PHP code changes
 push-failure
File push failure requiring attention
 python
Python code changes
 release-candidate
Release candidate build
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
No labels
Priority -
Type -
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/MokoOnyx#34
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?