No option to connect a package to a repository

[eric-creekside]

Select Topic Area

Question

Body

On this documentation page, it says I can connect a package to one of my repositories. Here's what it says:

But on my package page(s), there is no such option. I have the list of versions (under the assets) and a "Package settings" link. On the Package Settings page, there's nothing about connecting to a repository. Only Options tab (with only the button to delete the package), and Manage Versions tab.
Here's what I see:

Why don't I have the Connect Repository option? What am I missing?

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[eric-creekside]

Asked almost a year ago - no answers to this? Seems like a bug but I'm willing to accept that I'm just missing something.

[tinaheidinger]

This isn't supported for Maven packages - what type of package are you looking at?

[eric-creekside]

This isn't supported for Maven packages - what type of package are you looking at?

Indeed I'm talking about Maven packages. Is there a specific reason we can't link Maven packages to a repo?
At the least, the documentation I referenced should mention that limitation.

[tinaheidinger]

The Maven registry runs on an older version of our architecture, where all packages are published to a repository. The packages inherit the repo's permissions, so there is no need to link them explicitly. All other package types are published at organization level and can optionally linked to a repository, thus the linking feature.
The docs page that you referenced says

When you publish a package that is scoped to a personal account or an organization, the package is not linked to a repository by default.

That doesn't apply to Maven since these packages are scoped to a repository. I admit that this is a bit confusing, but the plan is for all registries to run on the new architecture, so they'll eventually reach feature parity.