Skip to content
Docs
Download Markdown
In this article

Dataset versioning

Read MAJOR, MINOR, and PATCH changes, and see how existing data access follows a release.

Download Markdown

Dataset SemVer 1.0 describes how content changes produce a version and how existing access treats later versions. It does not replace the access conditions or terms on a listing. A version number does not grant access to data.

How the version is formed

The format is MAJOR.MINOR.PATCH, compared numerically. For example, 1.10.0 is newer than 1.9.3. A dataset's first published version is 1.0.0; an unpublished draft has no content version.

The platform compares a release with the last published version. If several kinds of change happen together, the version advances by the highest level reached, and the record keeps each reason in order: MAJOR, then MINOR, then PATCH.

LevelChanges that trigger itWhat it means for you
MAJORA field is removed, renamed, or changes type; label values are removed, merged, or redefined; or the rule that selects dataset records changesMay break a program or model. A live feed does not automatically move to a new MAJOR.
MINORRecords, an optional field, or a label value are addedAdds content. A live feed follows within the same MAJOR.
PATCHRecords are corrected after review; a record is removed after a contributor withdraws consent or because of a legal takedownCorrects content. A live feed follows; a fixed set receives governed PATCH corrections.
No new versionOnly the listing page, price, or terms changeContent is unchanged. Terms have their own revision number.

For example, removing the promo field, adding 500 records, and correcting 10 records together produces a MAJOR version. The history records all three reasons, not only the version number.

How existing access follows

  • A live feed follows MINOR and PATCH releases within the MAJOR named by its grant. The buyer must opt in to a new MAJOR; it is not applied automatically.
  • A fixed set stays pinned to the exact version at activation. A governed PATCH can correct that set without adding later records to it.
  • A Deal stays pinned to the version named in its signed revision. A later MAJOR requires a new negotiation.

A Deal URL can reopen a specific history revision when you are signed in to a participating organizationThe Developer-side unit that holds Campaigns, data access, and funds. It does not change the active organization or grant access; if the Deal or revision is unavailable, the workspace does not substitute the latest revision.

These rules do not create authorization. Whether a listing offers one of these access modes depends on its current page and agreement. A version number does not prove that you have access or replace checks on purpose, license, and export conditions.

Changes that are easy to confuse

Consent withdrawal and legal takedowns remain PATCH changes. They reduce the record count, but they are required corrections and do not change the field structure or label meaning. The recorded reason states how many records were removed.

Changing the selection rule is MAJOR. Raising a minimum quality grade changes which records belong in the dataset. Even with the same fields, old and new versions then describe different populations.

Price and terms changes do not change the content version. The listing terms use their own revision number.

To understand a particular release, read the listing's version history and recorded reasons. If a version appears without reasons, do not guess what changed.