From 4cfc35dd0c80c93adde2b298a5de3a97a222f33b Mon Sep 17 00:00:00 2001 From: Alessandro Berti Date: Mon, 8 May 2023 10:17:19 +0200 Subject: [PATCH 1/3] fictious commit --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 2ca021da0..e51a7c833 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -42,7 +42,7 @@ * e561089945951e91b2ecfe0f223b35bd2d351630 * other NLP/LLM abstractions * 42b0d2a6f6fe7430d382117bf0ce54e8fd60ce23 - * return diagnostics dataframe in pm4py.conformance methods + * return diagnostics dataframe in pm4py.conformance methods& ### Changed * 44fc2aecd0885534dd2083a4011be9e031c3a04a From 2d95d6a1c5cbb619487277dd6d12e139958df716 Mon Sep 17 00:00:00 2001 From: Alessandro Berti Date: Mon, 8 May 2023 10:21:31 +0200 Subject: [PATCH 2/3] removed forced push --- .gitlab-ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 00e8a2627..44b56fcc0 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -46,4 +46,4 @@ push-release-branch: - 'echo -e "Host *\n\tStrictHostKeyChecking no\n\n" > ~/.ssh/config' # We force-push the release branch, because we want to overwrite the history of the target repository # In certain cases the target repo might be out of sync with the source repo, in that case a normal push would fail -> force-push - - git push target release --force + - git push target release From 81c2dbbd4883f42635f8cde200d789baafc0ef64 Mon Sep 17 00:00:00 2001 From: Alessandro Berti Date: Fri, 30 Jun 2023 16:41:40 +0200 Subject: [PATCH 3/3] docs(pm4py): updated changelog --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 719f644c8..d88ebb584 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,6 @@ # Changelog of pm4py -## pm4py 2.7.5 (2023.07.XX) +## pm4py 2.7.5 (2023.06.30) ### Added * f6d5a343808b350e83caac8cb0480e2ca671bfb4