Advised Git adaptation is actually Git v2.28. Minimal needed version of Git v2.24 remains the same.
GitLab installments with multiple online nodes must certanly be improved to 13.1 before upgrading to 13.2 (and later) considering a busting change in Rails which can end up in authorization dilemmas.
2.0 remediates an email confirmation sidestep. After improving, if the your own people become unexpectedly encountering 404 or 422 mistakes whenever signing in, or aˆ?blockedaˆ? information while using the demand range, their profile may have been un-confirmed. If so, please ask them to check always their mail for a re-confirmation back link. To find out more, read the debate of Email verification problems.
2.0 depends on the btree_gist extension for PostgreSQL. For installments with an outwardly managed PostgreSQL set-up, please be sure to download the extension manually before updating GitLab if databases individual for GitLab just isn’t a superuser. It is not required for installations utilizing a GitLab managed PostgreSQL databases.
Y production (
- No less than Git v2.24 (earlier, the minimum called for version got Git v2.22).
- Advised Git v2.26.
Problem to achieve this causes interior mistakes inside Gitaly solution in some RPCs as a result of the use of the new –end-of-options Git flag.
In addition, in 1.0, the version of rail was upgraded from 6.0.3 to 6.0.3.1. The Rails improve included a big change to CSRF token generation which will be maybe not backwards-compatible – GitLab servers because of the newer Rails version generate CSRF tokens which aren’t recognizable by GitLab servers using old Rails adaptation – which could cause non-GET requests to do not succeed for multi-node GitLab installments.
Thus, if you are using multiple Rails computers and particularly updating from 13.0, all hosts must initial end up being improved to 13.1.Z before improving to 13.2.0 or later on:
However, period cookie downgrades are not backed. Therefore after updating to 12.2.0, any downgrades would result to all periods are invalidated and users are signed out.
If you are planning to update from 12.0.Z to .Z , it is important to perform an intermediary upgrade to 12.1.Z before upgrading to .Z to avoid problems like #215141.
In 12.0.0 we produced different database relating adjustment. These variations need that consumers very first improve towards current patch release. After upgraded to .Z, consumers can improve to 12.0.Z. Troubles to take action may bring about databases migrations not-being applied, that could trigger software mistakes.
It is also necessary that you upgrade to 12.0.Z before thinking of moving a later form of 12.Y.
Instance 1: you’re at this time making use of GitLab .8, the https://hookupdate.net/it/wantmatures-review/ latest spot launch for .Z. You are able to improve as always to 12.0.Z.
Sample 2: you may be at this time utilizing a version of GitLab 10.Y. To improve, earliest improve towards final 10.Y production (10.8.7) then your last 11.8). After improved to .8 you’ll be able to safely improve to 12.0.Z.
GitLab 13
Users have been signed in before Maintenance form was allowed will still be closed in. If administrator whom enabled upkeep form manages to lose her treatment, they will not be able to disable upkeep function through the UI. Therefore, you can easily disable upkeep form through the API or rail system.
This bug got fixed in GitLab 14.5.0, and is expected to feel backported to GitLab 14.3 and 14.4.
When it comes to items, the GitLab Runner tries to upload all of them 3 times, thereafter the work at some point fails.
- ci_build_needs
4.0 contains a back ground migration to move all remaining repositories in heritage space to hashed space. You’ll find understood problems with this migration that are set in 5.4 and later. Preferably, miss 13.4.0 and update to 13.5.4 or more instead. Observe that the migration may take quite a while to run, based on what amount of repositories must certanly be moved. Make sure to be sure all background migrations have finished before updating further.