Shaun Thompson

I'd imagine [gitlab-org/gitlab issue 223679](https://gitlab.com/gitlab-org/gitlab/-/issues/223679) should resolve this but the timeline seems bit fluid (and far out there).

@holzman - Do we still want to advance this? If so, there appear to be some open items ;)

Ok to close this issue then @brettmorien ?

Did you find the related issue from Canonical @spjmurray?

Does the directory structure update in 16.3 make the project/component distinction firm enough to move forward? Reference [Merge Request](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127448).

I think we're seeing something similar on gitlab.com but so far it only manifests in projects marked as a CI/CD Catalog. https://docs.gitlab.com/ee/ci/components/catalog.html https://docs.gitlab.com/ee/architecture/blueprints/ci_pipeline_components/ ```bash [6:47:13 PM] [semantic-release] [@semantic-release/gitlab] › ✘...

> > I think we're seeing something similar on gitlab.com but so far it only manifests in projects marked as a CI/CD Catalog. > > @autotmp Not sure, the request...

Did the stale timer expire?

Would you be able to provide any insight/reproduction guidance @jan-kiszka ?

Any luck/feedback @amyboose ?