Tippecanoe latest build shows v1.36.0 version string — even from latest March 2024 source
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 430
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I cloned the Tippecanoe repository (March 1, 2024 commit 2daf84a6c10d22fcd4151fa9fcff9bea5407293a) and successfully built it from source.
However, I noticed that running:
css
Copy
Edit
tippecanoe --version
Still shows:
nginx
Copy
Edit
tippecanoe v1.36.0
I checked version.hpp and saw that the version string is hardcoded to 1.36.0. There hasn’t been a bump even though there are newer commits.
Can you clarify:
Is this expected behavior, and does it require manual updating of version.hpp?
Or is there an automatic way to reflect the latest version / tag in the build?
I just want to confirm for accuracy before I proceed with production use.
If so, might be good if you made it show the correct version somehow.
Thanks
Nitin
Contributor guide
Research direction
Start by reading version.hpp and running tippecanoe --version against the March 2024 source described in the issue. Check how the version string is used during the build; done means the reported version behavior is consistent with the repository's tags or documented as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100