MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 85 Pull Requests 1 Actions Packages Projects Releases 4 Wiki Activity

fix: backport upstream v1.26.2 critical fixes #139

Merged
jmiller merged 2 commits from fix/upstream-v1.26.2-backports into main 2026-05-24 04:30:37 +00:00
Conversation 0 Commits 2 Files Changed 9
+98 -78
jmiller commented 2026-05-24 04:30:30 +00:00
Owner
Copy Link
Copy Source

Backport 2 upstream Gitea v1.26.2 fixes:

  1. Fix scheduled action panic with null event payload (upstream #37459)
  2. Fix email addresses not treated case-insensitively (upstream #37600)

Already present in our fork (no-op cherry-picks): #37516 merge autodetect, #37513 branch protection order, #37554 workflow param validation, #37570 null jobs panic, #37692 deadlock (our UpdateRepoRunsNumbers already has transaction guard).

Dev tested: v1.26.1-moko.3-dev - PR creation via API, health checks pass.

Backport 2 upstream Gitea v1.26.2 fixes: 1. Fix scheduled action panic with null event payload (upstream #37459) 2. Fix email addresses not treated case-insensitively (upstream #37600) Already present in our fork (no-op cherry-picks): #37516 merge autodetect, #37513 branch protection order, #37554 workflow param validation, #37570 null jobs panic, #37692 deadlock (our UpdateRepoRunsNumbers already has transaction guard). Dev tested: v1.26.1-moko.3-dev - PR creation via API, health checks pass.
jmiller added 2 commits 2026-05-24 04:30:31 +00:00
Fix scheduled action panic with null event payload (#37459) (#37466) f639940608 
Backport #37459 by cyphercodes

This fixes the scheduled action panic when an event payload is JSON
`null` by initializing the payload map before adding `schedule`. It also
adds regression coverage for the null-payload case.

Fixes #37447.

Co-authored-by: Rayan Salhab <r.salhab@aiyexpertsolutions.com>
Co-authored-by: cyphercodes <cyphercodes@users.noreply.github.com>
Co-authored-by: Hermes Agent (GPT-5.5) <hermes-agent@users.noreply.github.com>
Co-authored-by: Nicolas <bircni@icloud.com>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Claude (Opus 4.7) <noreply@anthropic.com>
fix: treat email addresses case-insensitively (#37600) (#37611)
Branch Policy Check / Verify merge target (pull_request) Failing after 1s
Details
ec02fb9cf8
jmiller merged commit 0f543903fb into main 2026-05-24 04:30:37 +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
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 pending: testing
Feature implemented but not yet tested with documented proof
 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
 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: bug
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
 upstream
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
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea#139
Delete Branch "fix/upstream-v1.26.2-backports"

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?