Collection versions — v0.1 (immutable releases, pinning, upgrades)

Status: descriptive. It describes release/0.545.0. This is the spec that the docstring in collector/store/entitlements.py calls "immutable-versions". Every statement cites file:function. Gaps are listed under §6 *Open*.

When you buy a collection, you are entitled to its major line:

A version you bought never changes under you. Published versions are immutable, and your pin keeps working even if the seller later deprecates that version.

(routes/memory.py:_stage_collection). The versions stay in the tenant's projection (a git odb). Unpublishing clears a channel. It never deletes a version.

collection.released {id, tenant, version, prev_version, level, changelog, member_diff, by}).

pointed to before:

The version string is parsed as v?X.Y.Z (_semver_key). member_diff lists the members added, removed and changed.

collection.version.deprecated. Replaying the same version replaces its record.

(routes/billing.py:checkout, options.version).

acquires also record the version (routes/memory.py:import_collection, library_acquire).

the leading integer of v?N.). Several grants add their majors together. A grant without a version (admin grants, legacy grants, and purchases made before pinning existed) covers every major, so earlier buyers are never locked out.

older major may buy the new major (routes/billing.py:_refuse_own_or_owned).

The discovery row shows latest_release {version, level, count}, so a card shows whether the listing's latest release was major, minor or patch (store/discovery_index.py:_latest_release_of).

1. What a buyer gets

2. Versions and releases

3. Pinning at purchase

4. Reading and upgrading

5. Deprecation

6. Open