Skip to content
Snippets Groups Projects

Release post - GitLab 11.4

Merged James Ramsay (ex-GitLab) requested to merge release-11-4 into master
Compare and Show latest version
113 files
+ 1785
589
Compare changes
  • Side-by-side
  • Inline
Files
113
@@ -89,7 +89,7 @@ features:
GitLab now gives you a consistent experience with the ability to search
instance-wide from the top of every page.
We've also made search easier to use by showing group and project icons
We've also made search easier to use by showing group and project icons
in the results, plus expanding the width of the search bar accordingly.
- name: "Support for Android project import"
@@ -335,7 +335,7 @@ features:
description: |
License Management automatically detects the software licenses that you
are introducing with your code and its dependencies. In previous versions
of GitLab, this feature kept you informed of all licenses, but did not
of GitLab, this feature kept you informed of all licenses, but did not
allow you to define a policy about the licenses that should be allowed
in your production code.
@@ -624,10 +624,10 @@ features:
- GitLab 11.2 includes [Mattermost 5.1](https://mattermost.com/blog/mattermost-5-1-new-gif-selector-auto-linking-plugin-subpath-support-and-more/),
an [open source Slack-alternative](https://mattermost.com/) whose newest release includes a new GIF selector, auto-linking plugin,
subpath support, plus much more. Since it includes [security updates](https://about.mattermost.com/security-updates/), upgrading is recommended.
- `gitlab-ctl repmgr` now honors the directories set by `postgresql['data_dir']`.
- GitLab's Prometheus instrumentation now works out of the box on Docker containers.
- `git` has been updated to 2.18.0.
- Alertmanager has been updated to 0.15.1, gitlab-monitor has been updated to 2.18.0.
- `gitlab-ctl repmgr` now honors the directories set by `postgresql['data_dir']`.
- GitLab's Prometheus instrumentation now works out of the box on Docker containers.
- `git` has been updated to 2.18.0.
- Alertmanager has been updated to 0.15.1, gitlab-monitor has been updated to 2.18.0.
- name: "Performance improvements"
available_in: [core, starter, premium, ultimate]
@@ -683,6 +683,38 @@ barometer:
# DEPRECATIONS
deprecations:
- feature_name: "Change to existing Projects API `archived` parameter"
type: breaking change
due: August 22, 2018
reporter: rymai
description: |
[GitLab 10.0](/2017/09/22/gitlab-10-0-released/#api-v3) introduced a
change that caused the `archived` parameter for the
[`GET /projects` endpoint](https://docs.gitlab.com/ee/api/projects.html#list-all-projects)
to behave in a confusing way:
- Not supplying the parameter would only return non-archived projects
- Passing `archived=true` would return all projects,
including those that were archived
- Passing `archived=false` would only return non-archived projects
The 11.2 release [corrects this regression](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20566):
- Not supplying the parameter now **returns all projects, including those
that were archived**
- Passing `archived=true` now **only returns the archived projects**
- Passing `archived=false` still only returns non-archived projects (no
behavior change)
If you are using this API endpoint, you may want to change your current
usage as follows:
| Current usage (from GitLab 10.0 to 11.2) | New usage (starting with GitLab 11.2) |
| ------------- | --------- |
| No `archived` parameter | Pass `archived=false` |
| Using `archived=true` | Don't use the `archived` parameter anyore |
| Using `archived=false` | No change needed |
- feature_name: "Disable SAML and Bitbucket if OmniAuth is disabled"
due: August 22, 2018
reporter: akaemmerle
@@ -713,7 +745,7 @@ deprecations:
inadvertently removed ahead of schedule, so affected users should update their
Gitlab Pages' DNS `A` record immediately. For more information, see our
[GitLab Pages Update](/2018/08/28/gitlab-pages-update/) post.
We had changed the Pages IP on GitLab.com in the past, and the steps you need to follow are
the same as those detailed in [this earlier blog post](/2017/03/06/we-are-changing-the-ip-of-gitlab-pages-on-gitlab-com/),
with the exception of the new IP itself. <del>We plan to forward the old IPs for
@@ -722,5 +754,5 @@ deprecations:
may not be available until you make this change.</del> Note that DNS `CNAME`
records do not need to be changed. GitLab self-hosted instances are not
affected by this change.
This section will be updated if any additional information is posted.
Loading