Docs: PHP composer registry is coming in 13.2
What does this MR do?
From Slack:
@dnsmichi: Seems that the PHP composer registry is missing in the release post. gitlab-com/www-gitlab-com!52380 (merged) is merged, so the docs are uptodate. Coming from this tweet - https://twitter.com/mzeis/status/1274756003125493760?s=21 Please respond directly if you like :)
@trizzi: It did miss the release and release post because the feature flag was not removed in time. It should be available on .com, but won’t be included until 13.2 for self-managed. We ARE moving the package registry to core. That work is happening this milestone, 13.2.
Related issue update: #15886 (comment 366635699)
This MR takes the MVC approach with only bumping the versions in two locations:
- Primary table
- Composer sub chapter
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team