Merge branch...

Merge branch '343880-documentation-unclear-that-a-ci_job_token-cannot-access-generic-packages-from-another' into 'master'

Docs update permissions for job tokens + packages

See merge request gitlab-org/gitlab!82940

doc/ci/jobs/ci_job_token.md

@@ -23,6 +23,12 @@ You can use a GitLab CI/CD job token to authenticate with specific API endpoints
 - [Releases](../../api/releases/index.md).
 - [Terraform plan](../../user/infrastructure/index.md).
 
+NOTE:
+There's an open issue,
+[GitLab-#333444](https://gitlab.com/gitlab-org/gitlab/-/issues/333444),
+which prevents you from using a job token with internal projects. This bug only impacts self-managed
+GitLab instances.
+  
 The token has the same permissions to access the API as the user that caused the
 job to run. A user can cause a job to run by pushing a commit, triggering a manual job,
 being the owner of a scheduled pipeline, and so on. Therefore, this user must be assigned to

doc/user/packages/package_registry/index.md

@@ -60,6 +60,12 @@ For most package types, the following credential types are valid:
   allows access to packages in the project running the job for the users running the pipeline.
   Access to other external projects can be configured.
 
+  NOTE:
+  There's an open issue,
+  [GitLab-#333444](https://gitlab.com/gitlab-org/gitlab/-/issues/333444),
+  which prevents you from using a job token with internal projects. This bug only impacts self-managed
+  GitLab instances.
+  
 ## Use GitLab CI/CD to build packages
 
 You can use [GitLab CI/CD](../../../ci/index.md) to build packages.