Skip to content

Deprecate V1 metadata format for licenses

GitLab customers with an active subscriptions can reach out to GitLab Support when encountering unexpected problems with this change.

Deprecation Summary

The V1 dataset will no longer be available for download starting from the release date of GitLab %17.0.

Users who have the package_metadata_synchronization feature flag enabled are advised to upgrade to the latest GitLab instance, and remove the feature flag configuration.

Who can use the V1 dataset?

  1. SaaS: this does not affect gitlab.com as we do not expose the dataset to end users. The gitlab.com instance has used V2 since 16.3.
  2. Self-managed:
    1. Out of the box, and without any user interaction, GitLab instances do not use V1 data.
    2. GitLab versions 15.9 to 16.2 include the package_metadata_synchronization feature flag, which allows use of V1 when manually enabled.
    3. GitLab versions from 16.3 use the V2 dataset by default. The package_metadata_synchronization feature flag allows use of V1 when manually enabled.
    4. GitLab versions from 16.6 remove the package_metadata_synchronization feature flag, and can no longer use V1.

Breaking Change

Yes.

Affected Topology

Self-managed.

Affected Tier

  • Ultimate

Checklists

Labels

  • This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
  • This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

  • As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
  • On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post.
  • On the major milestone:

Mentions

  • Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.
    • To see who the stable counterparts are for a product team visit product categories
      • If there is no stable counterpart listed for Sales/CS please mention @timtams
      • If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
      • If there is no stable counterpart listed for Marketing please mention @cfoster3
  • Your GPM has been @mentioned so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.

Deprecation Milestone

Planned Removal Milestone

Links

Edited by Brie Carranza
OSZAR »