feat(licenses): package repo scope UI — assign packages to specific repos #395

New Issue

2026-06-01T10:01:14Z

jmiller commented

2026-06-01 10:01:14 +00:00

Summary

The RepoScope field on LicensePackage exists (TEXT, default 'all') but is always set to 'all'. Need UI to let admins scope a package to:

All repos in the org
A single specific repo
Multiple selected repos

Requirements

Dropdown/multiselect in create and edit package forms
List org repos for selection
Store as JSON array of repo IDs, or 'all'
ValidateLicenseKey should check if the repo requesting validation is in scope

Test Plan

Create package scoped to single repo → key only works for that repo's update feed
Create package scoped to 'all' → key works for all repos
Create package scoped to 2 repos → key works for both but not others
Edit package scope → changes apply immediately

🤖 Generated with Claude Code

## Summary The `RepoScope` field on LicensePackage exists (TEXT, default 'all') but is always set to 'all'. Need UI to let admins scope a package to: - All repos in the org - A single specific repo - Multiple selected repos ## Requirements - Dropdown/multiselect in create and edit package forms - List org repos for selection - Store as JSON array of repo IDs, or 'all' - ValidateLicenseKey should check if the repo requesting validation is in scope ## Test Plan - [ ] Create package scoped to single repo → key only works for that repo's update feed - [ ] Create package scoped to 'all' → key works for all repos - [ ] Create package scoped to 2 repos → key works for both but not others - [ ] Edit package scope → changes apply immediately 🤖 Generated with [Claude Code](https://claude.com/claude-code)

jmiller commented

2026-06-01 10:12:51 +00:00

Testing Plan — Package Repo Scope

API

Create package with repo_scope="all" → key validates for any repo in org
Create package with repo_scope=[repoID] → key only validates for that repo's update feed
Create package with repo_scope=[id1,id2] → key validates for both repos
Validate key on out-of-scope repo → rejected
Edit package scope → changes apply immediately

GUI

Repo scope selector in create package form (dropdown/multiselect)
Shows org repos for selection
"All repos" option (default)
Edit package form shows current scope selection
Scope displayed in packages table

🤖 Generated with Claude Code

## Testing Plan — Package Repo Scope ### API - [ ] Create package with repo_scope="all" → key validates for any repo in org - [ ] Create package with repo_scope=[repoID] → key only validates for that repo's update feed - [ ] Create package with repo_scope=[id1,id2] → key validates for both repos - [ ] Validate key on out-of-scope repo → rejected - [ ] Edit package scope → changes apply immediately ### GUI - [ ] Repo scope selector in create package form (dropdown/multiselect) - [ ] Shows org repos for selection - [ ] "All repos" option (default) - [ ] Edit package form shows current scope selection - [ ] Scope displayed in packages table 🤖 Generated with [Claude Code](https://claude.com/claude-code)

jmiller closed this issue

2026-06-02 11:21:16 +00:00

jmiller reopened this issue

2026-06-02 11:21:45 +00:00

jmiller referenced this issue from a commit

2026-06-02 11:47:40 +00:00

feat(licenses): API package CRUD, settings API, and repo scope UI

jmiller commented

2026-06-03 00:39:47 +00:00

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.

jmiller closed this issue

2026-06-03 00:39:47 +00:00

Sign in to join this conversation.

Priority Medium

Type Feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#395