Manifest Status Control

Background

Scoop's bucket updates manifest version numbers continuously via Github Actions, which brings two issues:

Manifest Error Risk

Manifests are automatically updated without review. When there are significant changes to an app's installation package, users may encounter unexpected errors.
Resolution depends on the maintainer's response time, during which all users are affected.

Missing Rename Notification

When a manifest is renamed, there is no way to proactively notify installed users.
The official approach is to keep the old manifest and add a reminder via the notes property, but users rarely check.

abyss implements real-time manifest status control through version number marking:

Pause Problematic Manifests

When a manifest issue is discovered, the version number is marked as pending.
Manifests in pending status cannot be installed or updated, protecting users from affected versions.
Once the issue is resolved, the version number is restored and users can use it normally.

Guide Renamed Manifests

TIP

For more details, please check the Manifests.

Badge	Description
	It is active, and can be installed or updated by Scoop.
	It is pending, and cannot be installed. If the installation is completed before `pending`, it cannot be updated by Scoop.
	It has been deprecated, and cannot be installed. If the installation is completed before `deprecated`, it cannot be updated by Scoop.
	It has been renamed, and cannot be installed or updated. The error message includes the new name, and you should use it to install. If there is data from Persist or Link, it will be migrated automatically.
	It is virtual, and does not actually install this app. It only performs data persistence through Persist or Link.