Compute
How to read the changelog
What a customer-visible Compute change entry records, why a source change is not a release, and how to decide in four steps whether an entry affects the versions you run.
What a change entry records
Every customer-visible entry carries the same four parts. Read them in this order.
| Part | What it tells you |
|---|---|
| The change | What behavior differs now, in the terms you see |
| Affected versions | Which API, contract, workflow, profile, adapter or client versions move |
| Migration | What you must change, and whether a fresh quote or approval is needed |
| Availability | When the change became reachable for your account |
Availability is the part people skip. An entry without it would only be a claim about Lithi's own work.
A source change is not a release
Work landing inside Lithi is not a change to your account. Code can exist for a long time before any version you can call moves.
An entry is published when the change is reachable for you and its version is released. That is why the entry names versions rather than dates alone.
So read the affected versions, not the description. A description that sounds relevant with no version you run is not your change yet.
Deciding whether an entry affects you
- Read the affected versions on the entry.
- Compare them with the contract release on a recent response, the
workflow.versionyou pin, your profile version, and your client version. - If none of yours appears, the entry does not affect you. Record the date and move on.
- If one appears, read the migration line before your next run, not after it.
Step two needs values you should already be recording. If you are not logging the contract release from your responses, start there; without it you cannot answer step three at all.
What an entry never contains
No entry carries a price, a rate or a fee. Your quote is the only authority on what you can be charged.
No entry carries a private identifier, an account name, or another customer's detail. It also carries no completion-time promise; timing belongs to your quote and your limits.deadline.
If an entry looks like it should contain one of those, it is describing where to find it instead.
Where entries are published
The change record is published with the API description in developer settings in the portal, so the entry and the schema it describes stay together.
Each released client keeps its own version history on its client page. A client can change without any Compute version moving, and the reverse is equally true.
Read what each version line covers before you interpret an affected-versions list, and the migration steps once you know an entry applies to you.