@foss.global/gitmanager 2.5.0 → 2.5.1

package/changelog.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 2026-10-14 - 2.5.1
+
+### Fixes
+
+- `pushRefs()` returns `applied` for a push in which some refs already hold their new object and the others change.
+  - The up-to-date refs report `ok` with `up to date` and the changed refs are pushed in the same atomic push; before, the call threw although the push had landed. A sent ref the remote reports as `no match` still makes the push `rejected`.
+  - The readme states that atomic pushes need a Smart HTTP remote (Git updates a dumb-HTTP remote ref by ref) and names the remote helper output caps: 128 MiB per push and 64 KiB per line.
+
 ## 2026-10-14 - 2.5.0
 
 ### Features

package/dist_rust/rustgitmanager_linux_amd64.tsrust-build.json

@@ -1,12 +1,12 @@
 {
   "format": "tsrust.build-provenance.v2",
-  "binarySha256": "a4e49a68adbeabe1fbd8952b0f3859a7aabce5f31dacc2c263d2c0110ecb2c15",
+  "binarySha256": "f99202edee12731c9b5fdf0d81211c1d25507301e4c58a2abebb7cbdf5925a7f",
   "buildInfo": {
     "projectName": "@foss.global/gitmanager",
-    "projectVersion": "2.5.0",
-    "gitCommit": "116a69d1745236d064315a45f862dc722a405ce2",
+    "projectVersion": "2.5.1",
+    "gitCommit": "a1e66ae23b7642e699d6639bce9f99daa29dfb0c",
     "gitDirty": false,
-    "builtAt": "2026-10-14T07:21:46.137Z",
+    "builtAt": "2026-10-14T08:05:34.179Z",
     "tsrustVersion": "4.5.1",
     "binary": "rustgitmanager",
     "target": "linux_amd64"

package/dist_rust/rustgitmanager_linux_arm64.tsrust-build.json

@@ -1,12 +1,12 @@
 {
   "format": "tsrust.build-provenance.v2",
-  "binarySha256": "996505ba6f293ecc9e59584e38ec0a885433faf083d5bd0625cf48f9e501b07e",
+  "binarySha256": "0df3f8f592f4ffe26c4a2774cc68bf5b4a70acc7a8cc2e4eeff283d82115e87d",
   "buildInfo": {
     "projectName": "@foss.global/gitmanager",
-    "projectVersion": "2.5.0",
-    "gitCommit": "116a69d1745236d064315a45f862dc722a405ce2",
+    "projectVersion": "2.5.1",
+    "gitCommit": "a1e66ae23b7642e699d6639bce9f99daa29dfb0c",
     "gitDirty": false,
-    "builtAt": "2026-10-14T07:24:04.603Z",
+    "builtAt": "2026-10-14T08:07:48.908Z",
     "tsrustVersion": "4.5.1",
     "binary": "rustgitmanager",
     "target": "linux_arm64"

package/dist_ts/00_commitinfo_data.js

@@ -3,7 +3,7 @@
  */
 export const commitinfo = {
     name: '@foss.global/gitmanager',
-    version: '2.5.0',
+    version: '2.5.1',
     description: 'Headless Git manager for the foss.global Git platform, with a TypeScript API and Rust engine.'
 };
 //# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiMDBfY29tbWl0aW5mb19kYXRhLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vdHMvMDBfY29tbWl0aW5mb19kYXRhLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiJBQUFBOztHQUVHO0FBQ0gsTUFBTSxDQUFDLE1BQU0sVUFBVSxHQUFHO0lBQ3hCLElBQUksRUFBRSx5QkFBeUI7SUFDL0IsT0FBTyxFQUFFLE9BQU87SUFDaEIsV0FBVyxFQUFFLCtGQUErRjtDQUM3RyxDQUFBIn0=

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@foss.global/gitmanager",
-  "version": "2.5.0",
+  "version": "2.5.1",
   "private": false,
   "description": "Headless Git manager for the foss.global Git platform, with a TypeScript API and Rust engine.",
   "exports": {

package/readme.md

@@ -176,9 +176,9 @@ await gitManager.setDefaultBranch({ org: 'mirror.org', repo: 'interfaces', defau
 
 - `pushRefs()` drives Git's HTTP remote helper (`git remote-https`, or `git remote-http` for a loopback remote) over its standard input. It lists the remote's refs, checks every lease against that listing (`expectedOldObjectId: null` for a create, so the ref must not exist), and sends all updates in one atomic receive-pack request, one `<old> <new> <ref>` command per ref (a delete has no new object). The remote checks each old object again inside its atomic ref transaction, so a ref that moves between the listing and the push fails the whole push. Command lines keep the same size however many updates a push holds. A lease replaces the fast-forward rule, so a leased update may rewind or move a tag.
 - `applied` means every ref is `ok`. `rejected` means the remote refused the push and changed no ref: a ref whose lease failed is `stale`, a ref that already holds its `newObjectId` is `ok` (`up to date`, see below), and every other ref is `rejected` (`atomic push failed`, or the remote's reason). Any refusal the remote reports per ref returns `rejected`. `pushRefs()` throws only when it cannot tell what the remote did: a transport failure, a missing or unreadable ref status, an outcome that is neither, such as a partial update, a remote without the `atomic` capability, or a push request the remote refused as too large.
-- Git sends nothing for a ref that already holds `newObjectId`, whatever its lease says, and reports it `ok` with the message `up to date`, so a retried push whose first response was lost reads as `applied`. Such a ref is not changed, but its lease was not checked either: `ok` never means the lease matched. Deleting a ref that is already gone is `stale`.
-- The remote must advertise the `atomic` receive-pack capability. Without it Git refuses before it sends anything, and `pushRefs()` throws a `GitManagerError` with code `atomicPushUnsupported`; it never falls back to ref-by-ref updates.
-- Each `newObjectId` must be in the managed repository; a missing one throws a `GitManagerError` with code `objectNotFound` before any connection. A push holds one or more updates of distinct full ref names under `refs/`; object IDs are full lowercase hexadecimal. GitManager sets no upper bound and never splits a push. A remote that refuses the push request as too large (HTTP 413) makes `pushRefs()` throw a `GitManagerError` with code `remoteLimitExceeded`; nothing was pushed.
+- Git sends nothing for a ref that already holds `newObjectId`, whatever its lease says, and reports it `ok` with the message `up to date` while the push's other refs are sent as usual, so a retried push whose first response was lost reads as `applied`. Such a ref is not changed, but its lease was not checked either: `ok` never means the lease matched. Deleting a ref that is already gone is `stale`.
+- The remote must advertise the `atomic` receive-pack capability. Without it Git refuses before it sends anything, and `pushRefs()` throws a `GitManagerError` with code `atomicPushUnsupported`; it never falls back to ref-by-ref updates. That holds for Smart HTTP remotes only: against a dumb-HTTP remote Git runs `http-push`, which updates ref by ref and is not atomic, so a push remote must serve Smart HTTP.
+- Each `newObjectId` must be in the managed repository; a missing one throws a `GitManagerError` with code `objectNotFound` before any connection. A push holds one or more updates of distinct full ref names under `refs/`; object IDs are full lowercase hexadecimal. GitManager sets no limit on the number of updates and never splits a push. It reads at most 128 MiB of the remote helper's output per push (the remote's ref listing and one status line per listed or pushed ref) and at most 64 KiB per line, and throws when the helper writes more. A remote that refuses the push request as too large (HTTP 413) makes `pushRefs()` throw a `GitManagerError` with code `remoteLimitExceeded`; nothing was pushed.
 - URL policy, enforced by GitManager: `https://`, or `http://` only to a loopback IP literal in its canonical spelling, `127.0.0.0/8` as four decimal octets without leading zeros or exactly `[::1]`. Other spellings of a loopback address (an uppercase scheme, octal, hexadecimal or single-integer forms, a trailing dot, other IPv6 forms) are refused rather than normalized, so Git receives exactly the URL the policy checked. Host names over `http`, `localhost` included, are refused, because a credential sent over plain `http` to a name would go wherever that name resolves. `ssh://`, `git://`, `file://`, `ext::`, local paths, scp-like URLs and URLs with user information are refused. The policy runs before any process starts, and its errors never quote the URL.
 - The credential, `caCertificates` and `timeoutMs` behave as for mirrors: the credential travels only in the Git process environment as an `Authorization` header, with no credential helper, no hooks, no redirects and no global or system Git config; error text replaces the remote URL with `<push-remote>`. The remote URL is never stored in the repository.
 - `{ signal }` aborts a push as described in [Cancellation, concurrency and stop](#cancellation-concurrency-and-stop). An abort before the updates are sent (the signal already aborted, or an abort during the local object check or the remote ref listing) changes nothing anywhere. An abort after that rejects with `transferAborted` as well, but the remote may have applied the push: the remote applies an atomic push completely or not at all, and the abort can land before or after it did. Read the remote refs again before retrying.

package/ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@foss.global/gitmanager',
-  version: '2.5.0',
+  version: '2.5.1',
   description: 'Headless Git manager for the foss.global Git platform, with a TypeScript API and Rust engine.'
 }