Bug Fixes
-
echo object-format in all v2 commands
A v2 client must report its object format to the server, otherwise the
server assumes SHA-1 and aborts the request with a "mismatched object
format" error when talking to a SHA-256 repository.This affects both ls-refs and fetch. A persistent connection retains the
object format negotiated during ls-refs, but a stateless transport like
HTTP sends each command as its own request, so every v2 command must echo
the object-format the server advertised.So add the echo to
Command::default_featuresso it applies to every v2
command and permit object-format during v2 feature validation.Also add v2 wire-format sha256 tests for ls-refs and ref-in-want.
-
accept sha256 object-format from servers
Commit Statistics
- 7 commits contributed to the release over the course of 27 calendar days.
- 27 days passed between releases.
- 2 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Merge pull request #2642 from 10ne1/dev/aratiu/sha256-transport (da6b267)
- Review (ed998d1)
- Echo object-format in all v2 commands (6a7e5f4)
- Accept sha256 object-format from servers (96bf698)
- Merge pull request #2635 from GitoxideLabs/dependabot/cargo/cargo-7b971a5e8c (155ff6d)
- Bump the cargo group with 40 updates (9402adc)
- Merge pull request #2618 from GitoxideLabs/report (f7d4f33)