Internal projects cannot be cloned with job token
-
Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.
What does this MR do and why?
Internal projects can no longer be cloned with job token starting from %18.0 from a separate project. See #554314 (closed) for a full description of the issue.
References
- Project feature Package registry impacts abilit... (#554314 - closed)
- Breaking change: Leaked CI_JOB_TOKEN can be use... (#420678 - closed)
- Added build_download_code permission for intern... (!150763 - merged)
- Restricting job token for public and internal p... (!135263 - merged)
How to set up and validate locally
See the issue. After applying this MR, cloning a submodule should work.
MR acceptance checklist
MR Checklist ( @nwittstruck)
-
Changelog entry added, if necessary -
Documentation created/updated via this MR -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Tested in all supported browsers -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the javascript style guides -
Conforms to the database guides
Related to #554314 (closed)
Edited by Nicholas Wittstruck