feature:outdated
Check if any pinned features have newer versions available on GitHub.
Usage
splent feature:outdated [--upgrade]
| Option | Description |
|---|---|
--upgrade |
Automatically upgrade all outdated features to their latest version. |
Examples
Check for updates:
splent feature:outdated
Check and upgrade all at once:
splent feature:outdated --upgrade
Example output
feature:outdated
Checking 6 pinned feature(s) against GitHub...
Feature Current Latest Status
------------ ------------ ------------ ------------
auth v1.5.0 v1.5.3 ⬆ update
confirmemail v1.2.9 v1.2.9 ✔ latest
profile v1.5.0 v1.5.2 ⬆ update
public v1.5.0 v1.5.2 ⬆ update
redis v1.5.0 v1.5.2 ⬆ update
reset v1.2.9 v1.2.9 ✔ latest
4 feature(s) can be updated.
splent feature:upgrade <feature> update one
splent feature:outdated --upgrade update all
splent cache:prune clean old cached versions
Description
Queries the GitHub tags API for each pinned feature and compares the current version against the latest available release using proper semver sorting.
Status values:
| Status | Meaning |
|---|---|
⬆ update |
A newer version is available on GitHub. |
✔ latest |
The pinned version is already the latest. |
? unreachable |
Could not reach the GitHub API for this feature. |
When --upgrade is passed, all outdated features are upgraded by delegating to feature:upgrade --yes for each one.
Notes
- Set
GITHUB_TOKENto avoid GitHub API rate limits (60 req/hr unauthenticated vs 5,000 authenticated). - Only checks pinned features (with
@version). Editable features are skipped. - To upgrade a single feature, use
feature:upgrade <feature>directly.
Pairs well with
feature:upgrade– upgrade a single feature.feature:pin– pin editable features to their latest cached version.cache:prune– clean up old cached versions after upgrading.product:resolve– update symlinks after upgrading.