build: reproducibility issue with hatch version
See original GitHub issueI’m currently seeing our wheel file contents changing without changes to source:
diff -r locally-built-whl/tuf-1.1.0.dist-info/WHEEL github-whl/tuf-1.1.0.dist-info/WHEEL
2c2
< Generator: hatch 0.23.0
---
> Generator: hatch 0.22.0
So yes, we need to pin hatch version. This makes a lot of sense to me – why would we not pin the build tool when we pin all other dependencies?
I’m also a bit worried about that 0.22? Where did that come from – I don’t see it on pypi?
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
#1005825 - hatchling: please make the build reproducible
Debian Bug report logs - #1005825 hatchling: please make the build reproducible. version graph. Package: src:hatchling; Maintainer for src: ...
Read more >About - Hatch
Standardized build system with reproducible builds by default · Robust environment management with support for custom scripts · Easy publishing to ...
Read more >Release-pipeline: reproducible builds · Issue #18292 - GitHub
To be clear, reproducible builds have been possible for a long time. The only requirement is that the source be checked out to...
Read more >CMake / G++ reproducible build issue with changing build path
For quite some time I have been investigating with limited success reproducible build issue I have with a software I am packaging for...
Read more >Reproducible Builds vs Semantic Versioning - Matrix AI
Theoretically you should be able to update patch and minor versions of dependencies without any kind of problem.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
https://github.com/ofek/hatch/releases/tag/hatchling-v0.24.0
I think this is the issue: we depend on hatchling only but for some reason the WHEEL file documents it as
hatch
but still usinghatchling
version numbers.Then it makes sense: