Upgrade to 17.6.2

[Patrick-Remy]

GitLab Patch Release: 17.6.2 (see https://about.gitlab.com/releases/2024/12/11/patch-release-gitlab-17-6-2-released/)

[kkimurak]

Note: We are temporarily suspending our release process. This is because the build time exceeds the 1 hour limit of CircleCI's free plan.
It is possible to merge your patches, but the release will not happen automatically.

Also, please do not mix multiple upgrade to single pull request.

[Patrick-Remy]

Hope the investigation for the long build-times will be successful, as building myself also takes about 45min :-)

Okay, I added both commits so that anyone who want to build itself, can also build the subsequent version.
But if it's against the convention, you could also squash them on merge.

[Oicho]

Regarding the circle ci issue I could lend some compute power and install what is needed for the integration with circle ci.

Looks like self hosted runners are allowed in the free tier. https://circleci.com/docs/plan-free/#self-hosted-runners

Feel free to reach out.

[kkimurak]

@Oicho Really Thank you for the very attractive offer, but there's still a problem with that. As far as I know, none of the currently active maintainer have access to CircleCI's settings. Only users with Admin role can register Self Hosted Runners. Probably @sachilles has contributor privileges since it seems to have no privilege to manage role (correct me if I'm wrong).
Circleci docs:

• permission table : https://circleci.com/docs/ja/roles-and-permissions-overview/
• role management : https://circleci.com/docs/ja/manage-roles-and-permissions/

Furthermore, it seems that these settings are applied to each organization, not per project. It makes the current setup where everything is in the sameersbn namespace is even more inappropriate (in the sense that it is difficult to maintain without sameersbn).

[Collatum-IT-GmbH-Admin]

Is there a timeline when we can expect a new gitlab version? Or is the build issue still unresolved?

[kkimurak]

Is there a timeline when we can expect a new gitlab version?

No

Or is the build issue still unresolved?

Yes, maybe merging #3049 can temporarily solve the build time issue.

Please don't rush. If you are in a hurry, build it yourself or use the pre-release provided by a kind community member: #3042 (comment)

[kkimurak]

Also note that this patch, which skips the intermediate version, will probably never be directly merged. Given the history, most of the time when such a pull request has been created, it has been reworked by the maintainer into separate pull requests, each with its own release. This is because there have been many people who have complained about intermediate versions not being released.

[sachilles]

Closed in favor of #3053 . Anyway thanks for your contribution, that "lives in #3053".