Today we are releasing version 12.10.1 for GitLab Community Edition and Enterprise Edition.
This version resolves a number of regressions and bugs in this month's 12.10 release and prior versions.
GitLab Community Edition and Enterprise Edition
- Move Group Deploy Tokens to new Group-scoped Repository settings
- Move project deploy tokens section back to repository settings
- Migrate dismissals to vulnerabilities
- Fix requirements permission documentation
- Add feature flag for merge_ref_head
- Fix bug creating project from git push through ssh
- Fix Web IDE deleting newly added files
- Fix Service Templates missing Active toggle
- Fix merge requests stuck in checking state
- Fix null dereference in project_import_status
- Fix 500 error accessing restricted visibility levels
- Ensure the pg bin files fallback for geo-postgresql
- Prevent gitlab upgrades from GitLab 11.x
- Fixes Omnibus package HA pg-upgrade scenario
- Print a deprecation notice for postgres upgrades if <11
This version includes one post-deploy migration, but should not require any downtime.
Please be aware that by default the Omnibus packages will stop, run migrations,
and start again, no matter how “big” or “small” the upgrade is. This behavior
can be changed by adding a
which is only used for updates.
To update, check out our update page.
Access to GitLab Starter, Premium, and Ultimate features is granted by a paid subscription.
Alternatively, sign up for GitLab.com to use GitLab's own infrastructure.
We want to hear from you
Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum.Share your feedback