Follow-up from "Updating flags to confirm Dedicated"
Related to #439130 (comment 1794362833)
The following discussions from !146136 (merged) should be addressed:
-
@marcel.amirault started a discussion:
For these .com admin only features, we can start with this as a safe default, but we should double check if Dedicated will have access to these through their support channels
-
@marcel.amirault started a discussion (
doc/api/group_releases.md
):I think they forgot to remove the flag note, from:
I started with this initial suggestion, but actually realize we probably need to add version history for the whole page?
**Offering:** GitLab.com, Self-managed, GitLab Dedicated Review your groups' [releases](../user/project/releases/index.md) with the REST API. NOTE: For more information about the project releases API, see [Releases API](releases/index.md).
-
@marcel.amirault started a discussion (
doc/api/group_ssh_certificates.md
):Looks like this one is wrong too:
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/421915) in GitLab 16.4 [with a flag](../user/feature_flags.md) named `ssh_certificates_rest_endpoints`. Disabled by default. > - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/424501) in GitLab 16.9.