- Also limit listing skipped designs to 2 files in flash

Trim extra period when merge error displayed

See merge request gitlab-org/gitlab!23737

Revert "Merge branch 'aws-version-bump' into 'master'"

See merge request gitlab-org/gitlab!23829

Add Epics Activity info to Group Export

Closes #198523

See merge request gitlab-org/gitlab!23613

Updates security release template

See merge request gitlab-org/gitlab!23822

Stop exposing Secure artifacts in MR widget entity

See merge request gitlab-org/gitlab!23824

This reverts merge request !22865

We are not consuming the endpoints anymore, since we are now using the
new comparison endpoints. Thus we can stop exposing them.

After moving the development from dev.gitlab.org to a private group on
gitlab.com/gitlab-org/, we no longer need links on dev. This MR updates
the security release issue template to reflect that.

Drop kibana_hostname column

See merge request gitlab-org/gitlab!23503

Fix Rubocop offenses for cops with 1 or 2 offenses

See merge request gitlab-org/gitlab!23506

Dequarantine clone using deploy key spec

Closes #196047

See merge request gitlab-org/gitlab!23799

Remove open icon from function endpoint

Closes #196855

See merge request gitlab-org/gitlab!23508

Resolve "Knative domain name/endpoint section links to invalid doc"

Closes #38297

See merge request gitlab-org/gitlab!23715

Skip squashing with only one commit in a merge request

Closes #198971

See merge request gitlab-org/gitlab!23744

We noticed in https://gitlab.com/gitlab-org/gitaly/issues/2395 that the
backend was unnecessarily attempting to squash merge requests with one
commit. This happened because `SquashService` skips the squash if two
conditions are met:

1. The number of commits < 2
2. The `squash_commit_message` is null

If a `squash_commit_message` is passed, this indicates that the user
wants the squashed commit to have a different commit message.

By default, the frontend always sends `squash_commit_message`,
regardless of whether the squash button is available in the merge
request. With this change, the frontend will only send this parameter if
the button is shown (i.e. when the commit count is >= 2).

Alternatively, we could also change the backend to skip squashing if
only the first condition is met.

Closes https://gitlab.com/gitlab-org/gitlab/issues/198971

Fix error displaying group edit page

See merge request gitlab-org/gitlab!23774

Use CTE optimization fence for loading projects in dashboard

Closes #198440

See merge request gitlab-org/gitlab!23754

Certain users experienced Error 500s when loading projects from the
dashboard because the PostgreSQL query planner attempted to scan all
projects rather than just the user's authorized projects. This would
cause the query to hit a statement timeout.

To fix this, we add support for a CTE optimization fence to load
authorized projects first, which can be optionally used by
`ProjectsFinder` via the `use_cte` parameter. To be safe, we only enable
it for the finder call that loads the list of projects behind the
`use_cte_for_projects_finder` feature flag.

Closes https://gitlab.com/gitlab-org/gitlab/issues/198440

Fix E2E test navigation to Group Security Dashboard

Closes #198636

See merge request gitlab-org/gitlab!23710

Remove invalid data from issue_tracker_data table

See merge request gitlab-org/gitlab!23759

Remove environments REST API endpoint occurences

See merge request gitlab-org/gitlab!23659

Add selective sync support to Geo Nodes API create endpoint

Closes #4731

See merge request gitlab-org/gitlab!23729

Remove outdated Secure VueX frontend code

See merge request gitlab-org/gitlab!23624

Allow the new created group as part of the paid signup flow
to be edited before it’s license is applied.

Since we now retrieve data from the Backend, we can remove the parsing
log from the Frontend. See:
https://gitlab.com/groups/gitlab-org/-/epics/1425

Since we now retrieve data from the Backend, we can remove the parsing
log from the Frontend. See:
https://gitlab.com/groups/gitlab-org/-/epics/1425

Since we now retrieve data from the Backend, we can remove the parsing
log from the Frontend. See:
https://gitlab.com/groups/gitlab-org/-/epics/1425

Since we now retrieve data from the Backend, we can remove the parsing
log from the Frontend. See:
https://gitlab.com/groups/gitlab-org/-/epics/1425

Rework conditions when user uses license seat and when to show the badge

See merge request gitlab-org/gitlab!23522

Fix for puma issue running via `rails s`

See merge request gitlab-org/gitlab!23603

A recent update seems to have broken running the server locally
via `bundle exec rails s`. Puma no longer seems to respond to
`#cli_config` in that scenario, so this patch fixes that situation.

Separate project hook, indentity, export status and shared goup classes from entities

See merge request gitlab-org/gitlab!23789

Indicate Sentry error level in GitLab

See merge request gitlab-org/gitlab!23346