Add latest changes from gitlab-org/gitlab@master

5 files changed, 24 insertions, 10 deletions

diff --git a/doc/api/audit_events.md b/doc/api/audit_events.md
index e4856010b6c..89e89366de5 100644
--- a/doc/api/audit_events.md
+++ b/doc/api/audit_events.md
@@ -138,16 +138,10 @@ Example response:
 
 ## Group Audit Events
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/34078) in GitLab 12.5.
-> - Support for keyset pagination [added](https://gitlab.com/gitlab-org/gitlab/-/issues/333968) in GitLab 15.2.
-> - Also returning project audit events for projects within the given group was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/feat/337757) in GitLab 16.1 behind feature flag `audit_event_group_rollup`. Disabled by default.
-
-FLAG:
-On self-managed GitLab, by default returning project audit events for projects within the given group is not available. To make it available, ask an administrator
-to [enable the feature flag](../administration/feature_flags.md) named `audit_event_group_rollup`. On GitLab.com, this feature is not available. The feature is not ready for
-production use.
+> Support for keyset pagination [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/333968) in GitLab 15.2.
 
 The Group Audit Events API allows you to retrieve [group audit events](../administration/audit_events.md#group-events).
+This API cannot retrieve project audit events.
 
 A user with:
 
diff --git a/doc/ci/components/index.md b/doc/ci/components/index.md
index 999c9b0c0fb..c6659e7b7de 100644
--- a/doc/ci/components/index.md
+++ b/doc/ci/components/index.md
@@ -185,6 +185,8 @@ each containing resources that you can add to your CI/CD pipelines.
 
 ### Mark the project as a catalog resource
 
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/407249) in GitLab 16.1.
+
 After components are added to a components repository, they can immediately be [used](#use-a-component-in-a-cicd-configuration) to build pipelines in other projects.
 
 However, this repository is not discoverable. You must mark this project as a catalog resource to allow it to be visible in the CI Catalog
diff --git a/doc/development/ai_features.md b/doc/development/ai_features.md
index ff3d97f52b6..cab6ef0fd0c 100644
--- a/doc/development/ai_features.md
+++ b/doc/development/ai_features.md
@@ -26,7 +26,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 - Configuration for Moderation check of inputs
 - Automatic Markdown Rendering of responses
 - Centralised Group Level settings for experiment and 3rd party
-- Experimental API endpoints for exploration of AI API’s by GitLab team members without the need for credentials
+- Experimental API endpoints for exploration of AI APIs by GitLab team members without the need for credentials
   - OpenAI
   - Google Vertex AI
 
@@ -103,7 +103,7 @@ For features that use the embedding database, additional setup is needed.
 #### Tips for local development
 
 1. When responses are taking too long to appear in the user interface, consider restarting Sidekiq by running `gdk restart rails-background-jobs`. If that doesn't work, try `gdk kill` and then `gdk start`.
-1. Alternatively, bypass Sidekiq entirely and run the chat service syncronously. This can help with debugging errors as GraphQL errors are now available in the network inspector instead of the Sidekiq logs.
+1. Alternatively, bypass Sidekiq entirely and run the chat service synchronously. This can help with debugging errors as GraphQL errors are now available in the network inspector instead of the Sidekiq logs.
 
 ```diff
 diff --git a/ee/app/services/llm/chat_service.rb b/ee/app/services/llm/chat_service.rb
diff --git a/doc/development/gems.md b/doc/development/gems.md
index caff4ea1b03..4d364242efd 100644
--- a/doc/development/gems.md
+++ b/doc/development/gems.md
@@ -60,6 +60,7 @@ They should not be published to RubyGems.
 You can see example adding new Gem: [!121676](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/121676).
 
 1. Create a new Ruby Gem in `gems/gitlab-<name-of-gem>` with `bundle gem gems/gitlab-<name-of-gem> --no-exe --no-coc --no-ext --no-mit`.
+1. Remove the `.git` folder in `gems/gitlab-<name-of-gem>` with `rm -rf gems/gitlab-<name-of-gem>/.git`.
 1. Edit `gitlab-<name-of-gem>/README.md` to provide a simple description of the Gem.
 1. Edit `gitlab-<name-of-gem>/gitlab-<name-of-gem>.gemspec` and fill the details about the Gem as in the following example:
 
diff --git a/doc/update/removals.md b/doc/update/removals.md
index a5cd33e50d9..97f25897bf5 100644
--- a/doc/update/removals.md
+++ b/doc/update/removals.md
@@ -36,6 +36,23 @@ For removal reviewers (Technical Writers only):
 
 {::options parse_block_html="true" /}
 
+## Removed in 16.1
+
+### GitLab Runner images based on Alpine 3.12, 3.13, 3.14
+
+<div class="deprecation-notes">
+- Announced in: GitLab <span class="milestone">15.11</span>
+- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29639).
+</div>
+
+In alignment with the [GitLab Runner container images support policy](https://docs.gitlab.com/runner/install/docker.html#gitlab-runner-container-images-support-lifecycle), as of GitLab 16.1, we have stopped publishing runner images based on the following end-of-life Alpine versions:
+
+- Alpine 3.12
+- Alpine 3.13
+- Alpine 3.14
+
+We recommend that customers use GitLab Runner versions published with Alpine 3.15 or 3.16.
+
 ## Removed in 16.0
 
 ### Auto DevOps no longer provisions a database by default