[
https://issues.apache.org/jira/browse/ARROW-13083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17363615#comment-17363615
]
Krisztian Szucs commented on ARROW-13083:
-----------------------------------------
We cannot use the {{git describe}} command with this workflow since it
calculates the distance since the last tag reachable from the current commit.
An alternative could be to manually calculate the distance from the merge-base
of the current commit and the latest tag where the latest should be defined by
{{setup.py::default_version}} variable which we periodically bump after each
release.
> [Python] Wrong SCM version detection both in setup.py and crossbow
> ------------------------------------------------------------------
>
> Key: ARROW-13083
> URL: https://issues.apache.org/jira/browse/ARROW-13083
> Project: Apache Arrow
> Issue Type: Bug
> Components: Python
> Reporter: Krisztian Szucs
> Priority: Major
>
> Wanted to install nightly wheels for a rust integration test when I noticed
> that the nightly wheels get produced with base version 3.0.0.
> This is due to the recently changed release workflow. Now we're creating tags
> from release branches without a post rebase step, so setuptools_scm fails to
> find the correct version number on diverged branches.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
