Package Registry requests may return 403 Forbidden for package operations, including publishing and downloading packages, even if the registry was previously working.
The affected projects will have their Package Registry setting be updated to disabled in the project UI.
If Package Registry is required for a project follow the steps below after the maintenance:
Open the project in GitLab and go to Settings > General > Visibility, project features, permissions.
Turn on Package registry and save the change.
The packages_enabled API attribute will be deprecated in 19.3.4. Use package_registry_access_level when you manage the package registry through the API or automation.
The UI change synchronizes the relevant project settings and should restore Package Registry access.
Please see our Package Registry troubleshooting article for detailed steps. https://support.gitlab.com/hc/en-us/articles/30888800919580-Package-registry-returns-403-Forbidden-with-no-audit-event-showing-it-was-disabled
If you do not need Package Registry for your projects, no action is required.