Repair function problem in 9 to 14.4
Advised Git adaptation was Git v2.28. Minimal necessary type of Git v2.24 remains the exact same.
GitLab installations which have several web nodes must certanly be enhanced to 13.1 before improving to 13.2 (and soon after) because a breaking improvement in rail that may end in authorization problems.
2.0 remediates an email verification sidestep. After updating, if several of the people were all of a sudden encountering 404 or 422 problems when finalizing around, or aˆ?blockedaˆ? emails with all the demand range, their particular account was un-confirmed. If so, be sure to ask them to examine their unique mail for a re-confirmation connect. To find out more, read our conversation of Email confirmation problems.
2.0 relies on the btree_gist expansion for PostgreSQL. For installments with an outwardly was able PostgreSQL set-up, please ensure that you put in the expansion manually before updating GitLab if the database consumer for GitLab is not a superuser. This is simply not needed for installments utilizing a GitLab handled PostgreSQL database.
Y launch (
- At the very least Git v2.24 (previously, minimal expected type is Git v2.22).
- The recommended Git v2.26.
Problem to achieve this brings about internal mistakes within the Gitaly provider in some RPCs as a result of utilization of the newer —end-of-options Git banner.
In addition, in 1.0, the type of rail ended up being enhanced from 6.0.3 to 6.0.3.1. The Rails upgrade provided a big change to CSRF token generation that is perhaps not backwards-compatible — GitLab hosts making use of the latest Rails version generate CSRF tokens that are not identifiable by GitLab machines utilizing the elderly Rails adaptation — which could result non-GET desires to do not succeed for multi-node GitLab installations.
Therefore, if you work with several rail computers and specifically updating from 13.0, all hosts must first getting improved to 13.1.Z before improving to 13.2.0 or later:
But treatment cookie downgrades aren’t recognized. Therefore after updating to 12.2.0, any downgrades would cause all periods are invalidated and consumers is logged aside.
Should you decide to improve from 12.0.Z to .Z , it is necessary to execute an intermediary upgrade to 12.1.Z before upgrading to .Z in order to avoid issues like #215141.
In 12.0.0 we made numerous database relating changes. These adjustment need that users 1st improve to the current spot production. After improved to .Z, users can improve to 12.0.Z. Troubles to do so may end in databases migrations not applied, that may trigger application errors.
Additionally it is needed that you improve to 12.0.Z before moving to a later form of 12.Y.
Example 1: you are presently making use of GitLab .8, which is the current spot launch for .Z. You’ll update as usual to 12.0.Z.
Instance 2: you are currently making use of a version of GitLab 10.Y. To improve, earliest upgrade to the final 10.Y production (10.8.7) then the last 11.8). After improved to .8 you can easily securely upgrade to 12.0.Z.
GitLab 13
Consumers who were finalized in before servicing form got allowed will continue to be finalized in. If admin who enabled repair means manages to lose their own session, then they will be unable to disable upkeep form through the UI. In that case, possible disable Maintenance setting via the API or rail console.
This bug had been fixed in GitLab 14.5.0, and is expected to become backported to GitLab 14.3 and 14.4.
As for the items, the GitLab athlete tries to upload them three times, and after that the task eventually fails.
- ci_build_needs
4.0 consists of a background migration to move all continuing to be repositories in heritage storage space to hashed storing. You’ll find identified difficulties with this migration that are repaired in 5.4 and later. Whenever possible, avoid 13.4.0 and upgrade to 13.5.4 or more alternatively. Observe that the migration usually takes a while to run, depending on what number of repositories must be relocated. Make sure to make sure that all back ground migrations have complete before updating furthermore.