4 Commits

Author	SHA1	Message	Date
Jonathan Miller	a88e3f8787	feat(updates): org-level default streams with per-repo override ... Add configurable update streams at org and repo level: - UpdateStreamConfig model: stores stream mode (joomla/custom) and custom stream definitions (name, suffix, description) - Resolution chain: repo override → org default → Joomla defaults - MatchStreamFromTag: matches release tags to streams using configured suffixes (longest match wins) - Both Joomla XML and Dolibarr JSON generators use effective streams - DB migration v336 creates update_stream_config table - Default Joomla streams: stable, release-candidate, beta, alpha, development - Custom streams support any tag suffix (e.g. -lts, -nightly, -security) Ref #265 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-30 20:49:46 -05:00
Jonathan Miller	50454db3fb	feat(updates): use full Joomla channel names in update feeds ... Use the full Joomla convention for update stream tag names: - dev → development - rc → release-candidate - alpha, beta, stable unchanged Add NormalizeChannel() helper that maps shorthand names (dev, rc) to full names so license key allowed_channels work with either format. Applied in XML generation, JSON generation, and key validation. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-30 20:31:43 -05:00
Jonathan Miller	627a22ee53	feat(updates): license key system and Dolibarr endpoint (Phase 2-3) ... Add license key data model and Dolibarr update feed endpoint: License key system: - license_package table: subscription tiers with duration, max sites, repo scope (org-wide or specific repos), and allowed update channels - license_key table: individual keys with SHA-256 hashed storage, domain restriction, custom start/end dates, internal/master key flag - license_key_usage table: tracks update check activity per key - DB migration v335 creates all three tables Update server enhancements: - Dolibarr JSON endpoint at /{owner}/{repo}/updates/dolibarr.json - License key validation on update endpoints via ?key=MOKO-XXXX param - Channel filtering: packages restrict which update streams keys access - Invalid keys get empty XML response (Joomla-compatible "no updates") - Usage tracking records domain, IP, user agent, version on each check Key design decisions: - Org-level master keys: IsInternal=true, package RepoScope="all" - Keys stored as SHA-256 hashes, raw key only shown at creation - Packages define allowed channels (e.g. ["stable","rc"] for Pro tier) - MOKO-XXXX-XXXX-XXXX-XXXX format for license keys Ref #239 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-30 13:09:47 -05:00
Jonathan Miller	6c06384966	feat(updates): built-in Joomla update server endpoint ... Add GET /{owner}/{repo}/updates.xml that dynamically generates a Joomla-compatible updates.xml from the repository's releases. Features: - Automatically maps release tags to channels (stable/rc/beta/alpha/dev) - Finds .zip attachments for download URLs, falls back to archive URL - Emits one entry per channel (latest release wins) - Extracts version from tag names, strips common prefixes - Publicly accessible (no auth required) for Joomla update clients This is Phase 1 of #239 — the core dynamic update feed generation. Future phases will add license key gating, Dolibarr support, and repo settings UI. Ref #239 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-30 12:54:31 -05:00