MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 142 Pull Requests Releases 90 Wiki Activity

fix(licenses): add missing database migration v340 for license system columns #389

New Issue
Closed
opened 2026-06-01 09:20:46 +00:00 by jmiller · 2 comments
jmiller commented 2026-06-01 09:20:46 +00:00
Owner
Copy Link
Copy Source

Summary

Multiple columns added to license models lack corresponding migrations. Need a single migration to sync all missing columns.

license_key table

  • key_raw TEXT (renamed from key_plain in v337)
  • payment_ref VARCHAR(255) UNIQUE
  • last_heartbeat_unix BIGINT NOT NULL DEFAULT 0

update_stream_config table

  • licensing_enabled BOOL NOT NULL DEFAULT false
  • extension_name TEXT
  • display_name TEXT
  • description TEXT
  • extension_type VARCHAR(50)
  • maintainer TEXT
  • maintainer_url TEXT
  • info_url TEXT
  • target_version TEXT
  • php_minimum VARCHAR(20)

Test Plan

  • Run migration on existing database
  • Verify all columns exist after migration
  • Verify no data loss on existing records

🤖 Generated with Claude Code

## Summary Multiple columns added to license models lack corresponding migrations. Need a single migration to sync all missing columns. ### license_key table - `key_raw TEXT` (renamed from key_plain in v337) - `payment_ref VARCHAR(255) UNIQUE` - `last_heartbeat_unix BIGINT NOT NULL DEFAULT 0` ### update_stream_config table - `licensing_enabled BOOL NOT NULL DEFAULT false` - `extension_name TEXT` - `display_name TEXT` - `description TEXT` - `extension_type VARCHAR(50)` - `maintainer TEXT` - `maintainer_url TEXT` - `info_url TEXT` - `target_version TEXT` - `php_minimum VARCHAR(20)` ## Test Plan - [ ] Run migration on existing database - [ ] Verify all columns exist after migration - [ ] Verify no data loss on existing records 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jmiller commented 2026-06-01 10:11:01 +00:00
Author
Owner
Copy Link
Copy Source

Testing Plan — Migration v340

API / DB

  • Fresh install creates all tables with all columns
  • Existing install runs migration without errors
  • license_key: key_raw, payment_ref (UNIQUE), last_heartbeat_unix, first_used_unix columns exist
  • license_package: is_archived, domain_lock_hours columns exist
  • update_stream_config: licensing_enabled, download_gating, support_url, and all extension metadata columns exist
  • Verify no data loss on existing records
  • PaymentRef UNIQUE constraint enforced (duplicate insert fails)

🤖 Generated with Claude Code

## Testing Plan — Migration v340 ### API / DB - [ ] Fresh install creates all tables with all columns - [ ] Existing install runs migration without errors - [ ] license_key: key_raw, payment_ref (UNIQUE), last_heartbeat_unix, first_used_unix columns exist - [ ] license_package: is_archived, domain_lock_hours columns exist - [ ] update_stream_config: licensing_enabled, download_gating, support_url, and all extension metadata columns exist - [ ] Verify no data loss on existing records - [ ] PaymentRef UNIQUE constraint enforced (duplicate insert fails) 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jmiller added the pending: testing label 2026-06-01 10:13:53 +00:00
jmiller reopened this issue 2026-06-02 11:21:42 +00:00
jmiller commented 2026-06-03 00:39:45 +00:00
Author
Owner
Copy Link
Copy Source

Tested and verified in production on MokoWaaS. All three download gating modes (none/prerelease/all), feed visibility, XML metadata, download URLs, and access control confirmed working.

Tested and verified in production on MokoWaaS. All three download gating modes (none/prerelease/all), feed visibility, XML metadata, download URLs, and access control confirmed working.
Sign in to join this conversation.
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
 tech-debt
Technical debt and TODO/FIXME items
 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
upstream
Inherited from upstream Gitea
 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 pending: testing
Milestone
No items
No Milestone
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#389
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?