From 6693c327c718d9b2bb421d3942a8409068f6e9e9 Mon Sep 17 00:00:00 2001 From: Walter Lozano <walter.lozano@collabora.com> Date: Fri, 18 Oct 2024 14:18:43 -0300 Subject: [PATCH] Release apertis-dev-tools version 0.2026.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Walter Lozano <walter.lozano@collabora.com> Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com> --- debian/changelog | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/debian/changelog b/debian/changelog index d1ed623..577acc8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,22 @@ +apertis-dev-tools (0.2026.0) apertis; urgency=medium + + * apertis-pkg-merge-upstream-to-downstreams: + - Don't print useless information while canceling pipelines. + - ensure merge request is created against the right project: + In case of a forked project, like we are doing with the test of the + rebase, the GitLab API creates by default the MR against the original + project instead of the forked project. To ensure the merge request is + created against the forked project, we use the push option + merge_request.target_project to overwrite the default behavior and to + create the merge request against the forked project. + * Use upstream recommended workaround to still return a RunningCommand object + of an executed sh command. This is required due to a breaking change in + python3-sh 2.x. + * Keep compatibility with python3-sh 1.x, by using _return_cmd + only when required. + + -- Walter Lozano <walter.lozano@collabora.com> Wed, 19 Feb 2025 13:55:39 +0100 + apertis-dev-tools (0.2024.19) apertis; urgency=medium * ci-license-scan: Add proposed whitelist. -- GitLab