Skip to content
Snippets Groups Projects
Commit 4072bbda authored by 🤖 GitLab Bot 🤖's avatar 🤖 GitLab Bot 🤖 Committed by Joe Randazzo
Browse files

Release post - GitLab 17.8

parent 706ec832
No related branches found
No related tags found
1 merge request!137648Release post - GitLab 17.8
Showing
with 62 additions and 19 deletions
- version: '17.8'
name: ['Océane Legrand', 'Juan Pablo Gonzalez']
gitlab: ['oceane_scania', 'ScanianJP']
date: 'January 16, 2025'
post: '/releases/2025/01/16/gitlab-17-8-released/#mvp'
- version: '17.7'
name: Vedant Jain
gitlab: vedant-jain03
......
......@@ -5,8 +5,8 @@ features:
available_in: [ultimate]
gitlab_com: true
add_ons: []
image_url: '/images/unreleased/commit-link-vulnerability.png'
documentation_link: 'https://docs.gitlab.com/ee/user/application_security/vulnerabilities/#vulnerability-resolutions'
image_url: '/images/17_8/commit-link-vulnerability.png'
documentation_link: 'https://docs.gitlab.com/ee/user/application_security/vulnerabilities/#vulnerability-resolution'
reporter: charlieeekroon
stage: security_risk_management
categories:
......
......@@ -10,8 +10,7 @@ features:
You can now scan your project files directly in VS Code, before you've committed or pushed them, so you can find and fix security vulnerabilities faster. A SAST scanning side panel displays your scan results and updates as you make changes to your code. Hover over the vulnerability result to see a detailed description or open it in a separate editor window for more context. Reference our [documentation](https://docs.gitlab.com/ee/editor_extensions/visual_studio_code/#perform-sast-scanning) to get started.
 
This feature is available for GitLab.com customers on the Ultimate tier. We welcome your [feedback](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues/1775) and are excited to mature this functionality in the upcoming milestones.
For a demonstration, watch this [video of SAST scanning in VS Code](https://www.youtube.com/watch?v=KOYdVdA6ZCs).
 
<figure class="video_container">
<iframe src="https://www.youtube-nocookie.com/embed/KOYdVdA6ZCs" frameborder="0" allowfullscreen="true"> </iframe>
</figure>
 
......@@ -6,7 +6,7 @@ features:
gitlab_com: true
add_ons: []
documentation_link: 'https://docs.gitlab.com/ee/user/project/releases/'
image_url: '/images/unreleased/list_the_deployments_related_to_a_release.png'
image_url: '/images/17_8/list_the_deployments_related_to_a_release.png'
reporter: nagyv-gitlab
stage: deploy
categories:
......
......@@ -6,7 +6,7 @@ features:
gitlab_com: true
add_ons: []
documentation_link: 'https://docs.gitlab.com/ee/user/application_security/policies/merge_request_approval_policies.html'
image_url: '/images/unreleased/multiple-distinc-approvers-nov-19.png'
image_url: '/images/17_8/multiple-distinc-approvers-nov-19.png'
reporter: g.hickman
stage: security_risk_management
categories:
......@@ -19,6 +19,6 @@ features:
 
Example uses of this improvement include:
 
**Distinct role approvals:** One approval from a Developer role and another from a Maintainer role.\
**Role and group approvals**: One approval from Developer or Maintainer and a separate approval from a member of the Security Group.\
**Distinct group approvals:** One approval from a member of the Python Experts Group and another separate approval from a member of the Security Group.
- **Distinct role approvals:** One approval from a Developer role and another from a Maintainer role.
- **Role and group approvals**: One approval from Developer or Maintainer and a separate approval from a member of the Security Group.
- **Distinct group approvals:** One approval from a member of the Python Experts Group and another separate approval from a member of the Security Group.
features:
secondary:
- name: "Primary domain redirect for GitLab Pages"
available_in: [core, premium, ultimate] # Include all supported tiers
available_in: [core, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/project/pages/#primary-domain'
gitlab_com: true
reporter: mmacfarlane
......
features:
primary:
- name: "Machine Learning model experiments tracking GA"
- name: "Machine learning model experiments tracking in GA"
available_in: [core, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/project/ml/experiment_tracking/'
video: 'https://www.youtube.com/embed/x09L_aYgP7o'
video: 'https://www.youtube.com/embed/jkZq3SYm7a8'
reporter: tmccaslin
stage: modelops
categories:
- 'MLOps'
epic_url: 'https://gitlab.com/groups/gitlab-org/-/epics/9341'
description: |
When creating machine learning models, data scientists often experiment with different parameters, configurations, and feature engineering to improve the performance of the model. Keeping track of all this metadata and the associated artifacts so that the data scientist can later replicate the experiment is not trivial. Machine learning experiment tracking enables them to log parameters, metrics, and artifacts directly into GitLab, giving easy access later on while also keeping all experimental data within your GitLab environment. This feature is now availible as generally availible with enhanced data displays, ehanced permissions, deeper integration with GitLab, and bug fixes.
When creating machine learning models, data scientists often experiment with different parameters, configurations, and feature engineering to improve the performance of the model. Keeping track of all this metadata and the associated artifacts so that the data scientist can later replicate the experiment is not trivial. Machine learning experiment tracking enables them to log parameters, metrics, and artifacts directly into GitLab, giving easy access later on while also keeping all experimental data within your GitLab environment. This feature is now generally available with enhanced data displays, enhanced permissions, deeper integration with GitLab, and bug fixes.
......@@ -8,6 +8,7 @@ features:
categories:
- 'MLOps'
issue_url: 'https://gitlab.com/groups/gitlab-org/-/epics/16193'
force_left: true
description: |
Data scientists and Machine Learning engineers primarily work in Python environments, but integrating their machine learning workflows with GitLab's MLOps features often requires context switching and understanding of GitLab's API structure. This can create friction in their development process and slow down their ability to track experiments, manage model artifacts, and collaborate with team members.
 
......
---
mvp:
fullname: ['Océane Legrand', 'Juan Pablo Gonzalez']
gitlab: ['oceane_scania', 'ScanianJP']
description: |
Everyone can [nominate GitLab's community contributors](https://gitlab.com/gitlab-org/developer-relations/contributor-success/team-task/-/issues/490)!
Show your support for our active candidates or add a new nomination! 🙌
Through the Co-Create Program, [Océane Legrand](https://gitlab.com/oceane_scania) has been leading efforts to enhance the Conan package registry feature set, collaborating with Juan Pablo Gonzalez.
Their work has focused on bringing the feature closer to GA readiness while implementing Conan version 2 support.
This collaboration demonstrates how the Co-Create Program can drive significant improvements to GitLab's package registry capabilities.
They were nominated by [Raimund Hook](https://gitlab.com/stingrayza), Senior Fullstack Engineer, Contributor Success at GitLab, who highlighted their persistent collaboration and continuous iteration on the Conan Package Registry features.
Their work exemplifies GitLab values and will benefit all Conan users on the platform.
Océane Legrand is a Full Stack Developer at Scania where she works on maintaining their self-hosted GitLab instance on AWS.
"The work I'm doing in open source impacts both GitLab and Scania," says Océane.
"Contributing through the Co-Create Program has given me new skills, like experience with Ruby and background migrations. When my team at Scania faced an issue during an upgrade, I was able to help troubleshoot because I'd already encountered it through the program."
[Learn more about GitLab's Co-Create Program](https://about.gitlab.com/community/co-create/) where customers work directly with our product and engineering teams to develop new features and enhance existing ones.
---
features:
secondary:
top:
- name: "Enhance security with protected container repositories"
available_in: [core, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/packages/container_registry/container_protection_rules.html'
documentation_link: 'https://docs.gitlab.com/ee/user/packages/container_registry/container_repository_protection_rules.html'
image_url: '/images/17_8/protected_containers.png'
reporter: trizzi
stage: package
categories:
......
---
features:
secondary:
- name: "Safeguard your dependencies with protected packages"
available_in: [core, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/packages/package_registry/package_protection_rules.html'
gitlab_com: true
image_url: '/images/17_8/protected_pypi_packages.png'
reporter: trizzi
stage: package
categories:
- 'Package Registry'
issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/323971'
description: |
We're thrilled to introduce support for protected PyPI packages, a new feature designed to enhance the security and stability of your GitLab package registry. In the fast-paced world of software development, accidental modification or deletion of packages can disrupt entire development processes. Protected packages address this issue by allowing you to safeguard your most important dependencies against unintended changes.
From GitLab 17.8, you can protect PyPI packages by creating protection rules. If a package is matched by a protection rule, only specified users can update or delete the package. With this feature, you can prevent accidental changes, improve compliance with regulatory requirements, and streamline your workflows by reducing the need for manual oversight.
......@@ -6,7 +6,7 @@ features:
gitlab_com: true
add_ons: []
documentation_link: 'https://docs.gitlab.com/ee/user/group/epics/manage_epics.html#epic-color'
image_url: '/images/unreleased/customizable_colors_for_epics.png'
image_url: '/images/17_8/customizable_colors_for_epics.png'
reporter: amandarueda
stage: plan
categories:
......
......@@ -6,7 +6,7 @@ features:
gitlab_com: true
add_ons: []
documentation_link: 'https://docs.gitlab.com/ee/user/group/epics/#relationships-between-epics-and-other-items'
image_url: '/images/unreleased/epic_ancestors.png'
image_url: '/images/17_8/epic_ancestors.png'
reporter: amandarueda
stage: plan
categories:
......
......@@ -6,7 +6,7 @@ features:
gitlab_com: true
add_ons: []
documentation_link: 'https://docs.gitlab.com/ee/user/group/epics/manage_epics.html#health-status.'
image_url: '/images/unreleased/epic_health_status.png'
image_url: '/images/17_8/epic_health_status.png'
reporter: amandarueda
stage: plan
categories:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment