Read the now encrypted properties from `encrypted_properties`, and
ignore the integration.properties column, which will be removed
in a later release.

Changelog: changed

Experiment rollout issue url for pql three CTA

See merge request gitlab-org/gitlab!85089

Make geo:status output more explicit

See merge request gitlab-org/gitlab!83004

Track blocking epics removed on usage ping

See merge request gitlab-org/gitlab!84408

Use to_boolean helper for backup force env

See merge request gitlab-org/gitlab!85000

Implement API interface for Deployment Approval Rules

See merge request gitlab-org/gitlab!84692

Add a documentation example for code owners rules with **

See merge request gitlab-org/gitlab!84902

Includes more specific language for issue creation during Go upgrade process

See merge request gitlab-org/gitlab!84997

Add hard wraps. Fix spelling and word choice issues. Correct a
mis-capitalized term. Fix some instances of wrong indentation.

Refactor connection_spec.rb

See merge request gitlab-org/gitlab!84882

Implement first iteration of the agents REST API

See merge request gitlab-org/gitlab!83270

Changelog: added
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/83270
Epic: https://gitlab.com/groups/gitlab-org/-/epics/7204
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/347045

Use Pajamas checkbox for ldap_access_setting.html.haml

See merge request gitlab-org/gitlab!84852

Backfill routes namespace_id for projects

See merge request gitlab-org/gitlab!81121

Fix adding danger instructions

See merge request gitlab-org/gitlab!85078

Add new route for DAST Profile Library

See merge request gitlab-org/gitlab!84451

Use pajamas checkbox for user access level form

See merge request gitlab-org/gitlab!84849

Handle application javascript content type to be safe

See merge request gitlab-org/gitlab!83632

Changelog: added

This commit implements the API interface for the Deployment
Approval Rules.

This change is still behind deployment_approval_rules FF.

Ordering by "IS NULL" is equivalent to
using "NULLS LAST/FIRST" order and should be deprecated.

Changelog: changed
MR:
EE: true

Refactor DORA4 Documentation

See merge request gitlab-org/gitlab!83739

Add user preferences to customize Diffs colors

See merge request gitlab-org/gitlab!78281

Enable vulnerability_report_pagination feature flag by default

See merge request gitlab-org/gitlab!84553

Add validation for invalid protected branches for scan result policies

See merge request gitlab-org/gitlab!84107

scan result policies.

Changelog: fixed
EE: true

Add docs for Admin Area CI/CD limits

See merge request gitlab-org/gitlab!85070

This is an MVC for https://gitlab.com/gitlab-org/gitlab/-/issues/355969
to explicitly label failed, succeeded and total items counts.

geo_node_status_check_spec.rb doesn't test for specific example data.
Thus it remains unchanged.

Reducing GEO_STATUS_COLUMN_WIDTH a bit, because we are adding
up to almost 30 characters to each line in `print_counts`.
Co-authored-by: Catalin Irimie <cirimie@gitlab.com>
Changelog: changed
EE: true

Resolve "Audit and update buttons on Projects::WikisController#show"

See merge request gitlab-org/gitlab!84786

Add specs to ensure default password does not repeat

See merge request gitlab-org/gitlab!84665

Covers SAML, LDAP and OAuth

FE - Dispatch Snowplow events from their event definitions

See merge request gitlab-org/gitlab!84122

Changelog: added

Merge branch 'hchouraria-docs-proposal-remove-all-single-node-zero-downtime-instructions' into 'master'

Proposal: Remove all single-node zero downtime instructions

See merge request gitlab-org/gitlab!85008

With only Puma carried in GitLab 14.0 onwards
there is no possibility of minimizing any downtime
in single-node upgrades.

When the migration is run while leaving
the previous version's puma running, the
database changes are picked up in Rails
dynamically and UI errors begin to be
thrown to users.

Given the disruption of features is essentially
the same to users as a downtime when it
affects critical features such as merge requests
the section is false in indicating that
downtime is minimized.

Additionally this section is often discovered
by users and blindly followed even for
multiple version jumps that leads to
broken upgrades.

This change removes all sections related to zero
downtime upgrade instructions of single nodes.