MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 158 Pull Requests 5 Releases 96 Wiki Activity

fix(licenses): add database migration for new license_key columns (KeyRaw, PaymentRef, LastHeartbeatUnix) #386

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

Summary

The license_key model has three columns that were added to the Go struct but have no corresponding database migration:

  • KeyRaw (TEXT) — plaintext key for admin viewing
  • PaymentRef (UNIQUE) — idempotency key for payment webhooks
  • LastHeartbeatUnix (DEFAULT 0) — last successful validation timestamp

The v337 migration only adds KeyPlain which was renamed to KeyRaw in the model. Need a new migration to sync.

Also need migration for update_stream_config new columns:

  • LicensingEnabled (DEFAULT false)
  • ExtensionName, DisplayName, Description, ExtensionType
  • Maintainer, MaintainerURL, InfoURL, TargetVersion, PHPMinimum

Test Plan

  • Fresh install creates tables with all columns
  • Existing install runs migration without errors
  • Verify KeyRaw column exists and stores plaintext
  • Verify PaymentRef UNIQUE constraint works
  • Verify LastHeartbeatUnix updates on validation
  • Verify all UpdateStreamConfig metadata columns exist

🤖 Generated with Claude Code

## Summary The `license_key` model has three columns that were added to the Go struct but have no corresponding database migration: - `KeyRaw` (TEXT) — plaintext key for admin viewing - `PaymentRef` (UNIQUE) — idempotency key for payment webhooks - `LastHeartbeatUnix` (DEFAULT 0) — last successful validation timestamp The v337 migration only adds `KeyPlain` which was renamed to `KeyRaw` in the model. Need a new migration to sync. Also need migration for `update_stream_config` new columns: - `LicensingEnabled` (DEFAULT false) - `ExtensionName`, `DisplayName`, `Description`, `ExtensionType` - `Maintainer`, `MaintainerURL`, `InfoURL`, `TargetVersion`, `PHPMinimum` ## Test Plan - [ ] Fresh install creates tables with all columns - [ ] Existing install runs migration without errors - [ ] Verify KeyRaw column exists and stores plaintext - [ ] Verify PaymentRef UNIQUE constraint works - [ ] Verify LastHeartbeatUnix updates on validation - [ ] Verify all UpdateStreamConfig metadata columns exist 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jmiller commented 2026-06-01 10:13:11 +00:00
Author
Owner
Copy Link
Copy Source

Testing Plan — Database Migration

Superseded by #389 (migration v340). Same test plan applies.

DB

  • Fresh install creates all license tables with all columns
  • Upgrade from pre-v340 runs migration successfully
  • All new columns have correct defaults (false, 0, empty)
  • UNIQUE constraint on payment_ref enforced
  • No data loss on existing license_key/license_package records

🤖 Generated with Claude Code

## Testing Plan — Database Migration Superseded by #389 (migration v340). Same test plan applies. ### DB - [ ] Fresh install creates all license tables with all columns - [ ] Upgrade from pre-v340 runs migration successfully - [ ] All new columns have correct defaults (false, 0, empty) - [ ] UNIQUE constraint on payment_ref enforced - [ ] No data loss on existing license_key/license_package records 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jmiller commented 2026-06-01 10:24:45 +00:00
Author
Owner
Copy Link
Copy Source

Superseded by #389 (migration v340) which covers all columns.

?? Generated with Claude Code

Superseded by #389 (migration v340) which covers all columns. ?? Generated with [Claude Code](https://claude.com/claude-code)
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
 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
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels
Priority High
Type Bug
Status —
Priority —
Type —
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-APP#386
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?