From acd6e431b1a15ab2700bac2e8bc8393325770a92 Mon Sep 17 00:00:00 2001
From: to be continuous bot <pierre.smeyers+tbc@gmail.com>
Date: Sun, 16 Feb 2025 15:38:36 +0000
Subject: [PATCH] chore(deps): update dependency
to-be-continuous/semantic-release to v3.13
---
.gitlab-ci.yml | 2 +-
README.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 7c7db0c..2133bf4 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -12,7 +12,7 @@ include:
inputs:
shellcheck-files: "*.sh"
- component: $CI_SERVER_FQDN/to-be-continuous/gitleaks/gitlab-ci-gitleaks@2.7
- - component: $CI_SERVER_FQDN/to-be-continuous/semantic-release/gitlab-ci-semrel@3.12
+ - component: $CI_SERVER_FQDN/to-be-continuous/semantic-release/gitlab-ci-semrel@3.13
variables:
GITLAB_CI_FILES: "templates/gitlab-ci-maven.yml"
diff --git a/README.md b/README.md
index 71768d7..84feb89 100644
--- a/README.md
+++ b/README.md
@@ -87,7 +87,7 @@ It uses the following variable:
With its default arguments, the GitLab CI template for Maven forces the use of [JaCoCo Maven Plugin](https://www.eclemma.org/jacoco/trunk/doc/maven.html)
to compute code coverage during unit tests execution.
-In addition it makes the necessary to [integrate code coverage stats into your GitLab project](https://docs.gitlab.com/ee/ci/testing/code_coverage.html#view-code-coverage-results-in-the-mr) (report badge and viewable coverage in merge requests).
+In addition it makes the necessary to [integrate code coverage stats into your GitLab project](https://docs.gitlab.com/ee/ci/testing/code_coverage/#view-coverage-results) (report badge and viewable coverage in merge requests).
If you want to fix the JaCoCo plugin version or tweak the default configuration, you may have to configure the
[JaCoCo Maven Plugin](https://www.eclemma.org/jacoco/trunk/doc/maven.html) in your `pom.xml`, but be aware of the
--
GitLab