The recommended Git variation is actually Git v2.28. The minimum called for type of Git v2.24 remains the exact same.
GitLab installations having several internet nodes needs to be improved to 13.1 before improving to 13.2 (and later) due to a busting improvement in rail that can produce agreement problem https://hookupdate.net/it/swingtowns-review/.
2.0 remediates an email confirmation avoid. After improving, if the their customers were all of a sudden encountering 404 or 422 mistakes when finalizing in, or aˆ?blockedaˆ? emails with all the demand line, their particular reports might have been un-confirmed. In this case, be sure to keep these things always check their own e-mail for a re-confirmation back link. To learn more, see our debate of Email confirmation issues.
2.0 hinges on the btree_gist extension for PostgreSQL. For installments with an externally handled PostgreSQL set-up, please ensure that you install the expansion manually before improving GitLab if the databases individual for GitLab is not a superuser. This is not essential for installments utilizing a GitLab managed PostgreSQL databases.
Y production (
- About Git v2.24 (previously, the minimum requisite version was actually Git v2.22).
- The recommended Git v2.26.
Failure to do so brings about interior problems into the Gitaly provider in some RPCs as a result of utilization of the brand-new –end-of-options Git flag.
Also, in 1.0, the form of rail ended up being improved from 6.0.3 to 6.0.3.1. The Rails improve integrated a change to CSRF token generation which is perhaps not backwards-compatible – GitLab servers using the latest Rails type create CSRF tokens which are not recognizable by GitLab servers making use of the old rail version – that may cause non-GET desires to fail for multi-node GitLab installations.
Thus, if you are using multiple Rails hosts and particularly upgrading from 13.0, all machines must initially getting enhanced to 13.1.Z before improving to 13.2.0 or after:
However, period cookie downgrades commonly backed. So after updating to 12.2.0, any downgrades would result to all classes being invalidated and users is logged around.
If you’re planning to update from 12.0.Z to .Z , it is important to perform an intermediary improvement to 12.1.Z before upgrading to .Z in order to avoid problems like #215141.
In 12.0.0 we made different database relating changes. These variations require that consumers initially update into the newest area release. After enhanced to .Z, consumers can improve to 12.0.Z. Failure to do so may produce databases migrations not-being applied, that may lead to application errors.
It’s also needed that your upgrade to 12.0.Z before thinking of moving a subsequent type of 12.Y.
Sample 1: you are presently utilizing GitLab .8, the most recent area launch for .Z. You are able to upgrade as usual to 12.0.Z.
Instance 2: you will be currently making use of a form of GitLab 10.Y. To update, very first upgrade toward finally 10.Y release (10.8.7) then final 11.8). After enhanced to .8 you can safely update to 12.0.Z.
GitLab 13
Consumers have been finalized in before Maintenance means ended up being enabled will still be finalized in. If the admin exactly who allowed Maintenance form will lose her treatment, they will not be able to disable repair means through the UI. In this case, you are able to disable Maintenance form through the API or Rails console.
This insect is solved in GitLab 14.5.0, and is also expected to feel backported to GitLab 14.3 and 14.4.
When it comes to artifacts, the GitLab Runner tries to publish them three times, and after that the job ultimately fails.
- ci_build_needs
4.0 include a back ground migration to go all continuing to be repositories in heritage storage to hashed storing. There are identified difficulties with this migration which are solved in 5.4 and soon after. Preferably, miss 13.4.0 and improve to 13.5.4 or more rather. Observe that the migration may take a while to perform, depending on what amount of repositories should be relocated. Be sure to be sure all history migrations need finished before upgrading furthermore.