Skip to content

Releases: RollingVersions/git-client

@rollingversions/[email protected]

15 Mar 13:10
258cc97
Compare
Choose a tag to compare

Bug Fixes

  • Support git people with no name (#7)

@rollingversions/[email protected]

06 Mar 13:52
e7afeda
Compare
Choose a tag to compare

New Features

  • Added parseFetchResponseV2 method that returns an AsyncGenerator instead of a stream (#5)

  • Added a raw option to parseFetchResponse to allow getting the raw packfile bytes (#5)

Bug Fixes

  • Fixed the excessive memory usage for parseFetchResponse (#5)

    The entire packfile is now buffered into memory, but once that is done, far less memory is allocated during actual parsing. In large, real world git repositories, this uses hundreds of times less memory.

@rollingversions/[email protected]

06 Mar 13:52
e7afeda
Compare
Choose a tag to compare

Breaking Changes

  • Options passed into PackfileParserStream are now {store?: Store, storeMode?: 'compressed | 'raw'} instead of two separate stores for references and offsets (#5)

New Features

  • Added parsePackfile method that returns an AsyncGenerator instead of a stream (#5)

Bug Fixes

  • Fixed the excessive memory usage for PackfileParserStream (#5)

    The entire packfile is now buffered into memory, but once that is done, far less memory is allocated during actual parsing. In large, real world git repositories, this uses hundreds of times less memory.

@rollingversions/[email protected]

06 Mar 14:04
65e608e
Compare
Choose a tag to compare

Bug Fixes

  • Add missing export (#6)

@rollingversions/[email protected]

06 Mar 13:53
e7afeda
Compare
Choose a tag to compare

New Features

  • Added store and storeMode options to fetchObjects to allow passing a custom store (#5)

  • Added raw option to fetchObjects to allow getting the packfile as a binary stream (#5)

  • Added fetchObjectsV2 that returns an async generator instead of a stream (#5)

Bug Fixes

  • Fixed the excessive memory usage for fetchObjects (#5)

    The entire packfile is now buffered into memory, but once that is done, far less memory is allocated during actual parsing. In large, real world git repositories, this uses hundreds of times less memory.

@rollingversions/[email protected]

20 Feb 12:14
114b5d3
Compare
Choose a tag to compare

Bug Fixes

  • Remove console.log statement (#3)

@rollingversions/[email protected]

13 Sep 17:37
48f2d44
Compare
Choose a tag to compare

Breaking Changes

  • Uses node.js streams instead of async generators (#2)

Bug Fixes

  • No longer breaks when chunks in stream happen at bad times (#2)

@rollingversions/[email protected]

13 Sep 17:37
48f2d44
Compare
Choose a tag to compare

New Features

  • Initial realease (#2)

@rollingversions/[email protected]

13 Sep 17:37
48f2d44
Compare
Choose a tag to compare

Breaking Changes

  • Uses node.js streams instead of async generators (#2)

@rollingversions/[email protected]

13 Sep 17:37
48f2d44
Compare
Choose a tag to compare

Breaking Changes

  • Uses node.js streams instead of async generators (#2)

Bug Fixes

  • No longer breaks when chunks in stream happen at bad times (#2)