feature:outdated
Introduction
feature:outdated compares every pinned feature of your selected product with the newest version tagged on the forge. Run it to see what you can upgrade.
splent feature:outdated
feature:outdated
Checking 3 pinned feature(s) against the forge...
Feature Current Latest Status
------- ------------ ------------ ------------
auth v1.2.7 v1.2.7 ✔ latest
notes v1.2.0 v1.4.0 ⬆ update
reports v1.0.0 v1.1.0 ⬆ update
2 feature(s) can be updated.
splent feature:upgrade <feature> update one
splent feature:outdated --upgrade update all
splent cache:prune clean old cached versions
Only pinned features, those with @version, are checked. It reads features, plus features_dev or features_prod for the current SPLENT_ENV.
Upgrading everything that is behind
splent feature:outdated --upgrade
It hands every outdated feature to one run of feature:upgrade --yes. pip resolves them together with the rest of the product, so a planned version can be lower than the newest tag. The plan, the migrations and the checks are those of feature:upgrade.
Reference
| Option | Description |
|---|---|
--upgrade |
Upgrade every outdated feature in one run of feature:upgrade |
| Status | Meaning |
|---|---|
⬆ update |
The forge has a newer tag |
✔ latest |
The pinned version is the newest |
? unreachable |
The tags could not be read, or there are none |
It needs a selected product (SPLENT_APP). Set SPLENT_FORGE_TOKEN, or GITHUB_TOKEN, to avoid the forge’s anonymous rate limit. With --upgrade, it exits 1 and prints feature:upgrade did not upgrade every feature, see its plan above. when not all of them moved.
See also
feature:upgradeupgrades one feature, several or the whole product.feature:versionslists every version of one feature.cache:pruneremoves old cached versions after upgrading.