EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Hacker News·20d ago·5 min read
Looking forward to Git 2.56 – and 3.0
TL;DR
Git 2.56 introduces several usability improvements, while the anticipated Git 3.0 may shift to SHA-256 hashing, enhancing security but potentially causing compatibility issues.
✦ Why It Matters
Prepare for Git 3.0 by ensuring your tools support SHA-256 and reftables.
Key Takeaways
- Test your repositories for SHA-256 compatibility before upgrading.
- Utilize the new drop command to manage commit history more easily.
- Monitor GitHub's support for SHA-256 to avoid future issues.
- Adopt reftables for better performance in large repositories.
Full Summary
Git 2.56, set for release in late September, includes over 700 non-merge commits with enhancements like a new command to drop commits from history and improved suggestions for branch updates. However, it does not fundamentally alter the user experience.
The upcoming Git 3.0 is expected to transition to the SHA-256 hash function, replacing the outdated SHA-1, which has security vulnerabilities. This change is crucial as hashes are used to verify repository integrity.
While GitLab and Forgejo support SHA-256, GitHub's compatibility remains uncertain, posing a risk for users. Additionally, Git 3.0 may enforce lower-case object IDs and adopt a more efficient reftable storage mechanism for references, improving performance for large repositories.
The decision on whether to release 3.0 soon is pending from Git maintainer Junio Hamano.