From da2333cd37747d692d5c78b0c94bd400ff883a9a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sviatoslav=20Sydorenko=20=28=D0=A1=D0=B2=D1=8F=D1=82=D0=BE?= =?UTF-8?q?=D1=81=D0=BB=D0=B0=D0=B2=20=D0=A1=D0=B8=D0=B4=D0=BE=D1=80=D0=B5?= =?UTF-8?q?=D0=BD=D0=BA=D0=BE=29?= Date: Sat, 24 Aug 2024 07:13:16 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=A6=20Make=20Git=20archives=20reproduc?= =?UTF-8?q?ible=20(#1338)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Some time ago, it was discovered that Git archives having `ref-names: $Format:%D$` in `.git_archival.txt` may change when references existing in the repository change over time [[1]]. This means that downloading an archive for a commit from an immutable URL may start yielding slightly different results. This hurts the ability of downstreams to source projects from Git archive URLs. With that in mind, modern `setuptools-scm` advises against having this entry in the `.git_archival.txt` template [[2]]. And this patch implements said recommendation. [1]: https://github.com/pypa/setuptools_scm/issues/806 [2]: https://setuptools-scm.readthedocs.io/en/latest/usage/#git-archives --- .git_archival.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/.git_archival.txt b/.git_archival.txt index 8fb235d7..7c510094 100644 --- a/.git_archival.txt +++ b/.git_archival.txt @@ -1,4 +1,3 @@ node: $Format:%H$ node-date: $Format:%cI$ describe-name: $Format:%(describe:tags=true,match=*[0-9]*)$ -ref-names: $Format:%D$