Add deprecation notice: Dependency Proxy for Packages — 19.1

Tim Rizzirequested to merge
duo-edit-20260303-231241 into master

Be sure to link this MR to the relevant deprecation issue(s).

Please review:

They are frequently updated, and everyone should make sure they are aware of the current standards (PM, PMM, EM, and TW).

EM/PM release post item checklist

  • Set yourself as the Assignee, meaning you are the DRI.
  • For breaking changes:
    • Add the breaking change label to the MR.
    • If the breaking change affects GitLab.com, add window with a value of 1, 2, or 3. The value represents the planned release window for GitLab.com, typically in the three weeks before the major release date. You should intentionally plan this window ahead of time. If you're not sure, ask @swiskow.
  • Confirm this MR is labeled release post itemdeprecation
  • Follow the process to create a deprecation YAML file.
  • Add reviewers by the 10th.
  • Add scoped devops:: and group:: labels as necessary.
  • Add the appropriate milestone to this MR.
  • If the changes modify log format(addition/deletion/modification) of product feature, tag @gitlab-com/gl-security/engineering-and-research/security-logging team over the GitLab issue/MR.
  • When ready to be merged (and no later than the 15th) @mention the TW for final review and merge.

Reviewers

When the content is ready for review, it must be reviewed by a Technical Writer and Engineering Manager, but can also be reviewed by Product Marketing, Product Design, and the Product Leaders for this area. Please use the reviewers feature for all reviews. Reviewers will then approve the MR and remove themselves from Reviewers when their review is complete.

Edited by Tim Rizzi

Merge request reports