Access
You needADMIN_AREA_ACCESS to inspect publications and selection. Changes also require RESOURCE_PACKS_MANAGE and the deployment’s selection-write capability (mutationEnabled). The frontend hides no server-side requirement: Forge enforces both permissions.
The Portal URL is a production web endpoint, but this selector targets only network/stage/resourcepacks/global. There is no environment picker that turns it into a Production PackSet control.
Understand the page
Selecting a release row changes the inspection view and the
?version= URL parameter. It does not change the active selection. The first listed release is initially selected for inspection when the URL has no version.
The table shows the filtered latest GitHub release page (up to 30 upstream releases); it is not a search over all historical publications. Historical entries can be inspected even when incompatible with the current Stage runtime.
Pin a release
1
Refresh the active state
Use Refresh in the Stage selection card. Verify the current mode and document version. A failed refresh shows the last known selection and disables writes.
2
Inspect a compatible release
Select the release row. Check Minecraft 26.3 and resource-pack format 97, provenance, and pack order. The current Stage backend rejects other release compatibility values.
3
Request the change
Use Pin release <version>. Review the dialog’s Stage target and before/after selection.
4
Confirm once
Choose Confirm change. The request carries the version captured when the dialog opened. If another operator changed it, refresh/review and confirm a new change; do not repeatedly submit the old version.
5
Verify delivery
Check the new card state, then switch backend server or reconnect with a Minecraft client. An already-connected player must not receive an immediate pack broadcast. A cached pack may load very quickly.
Roll back or resume a channel
For a rollback, inspect an older compatible release and pin it through the same confirmation flow. Rollback uses an existing immutable release and creates a new Config document version. Choose Use Stable or Use Edge to follow that channel and clear any release pin. Pinning a release preserves the prior channel as its fallback selection for unpinning; explicitly choosing another channel changes it. The card reports Restart required: No and that online players update on their next server connection. This describes delivery behavior; it is not a fleet restart action or proof that all players already have the selected pack.Disabled and error states
Read-query cache freshness is 5 minutes for the releases list, 1 minute for Edge, and 30 seconds for selection. Immutable release details have infinite stale time. These are query cache thresholds, not a promise of automatic periodic polling; use Refresh when checking selection.
Developer integration
Portal hooks areuseResourcePackReleases, useResourcePackRelease(version), useEdgePackSet, useResourcePackSelection, and useUpdateResourcePackSelection. A successful mutation invalidates the selection query; write retries are disabled. The dialog retains the expected document version and blocks stale confirmation.
Use the HTTP reference for payloads and error behavior and the operational acceptance checklist for proxy/player verification.