@pnpm/releasing.exportable-manifest 1100.1.1 → 1100.1.2

package/lib/transform/index.js

@@ -1,7 +1,8 @@
 import { pipe } from 'ramda';
 import { transformBin } from './bin.js';
 import { transformPeerDependenciesMeta } from './peerDependenciesMeta.js';
+import { transformRepository } from './repository.js';
 import { transformRequiredFields } from './requiredFields.js';
 export {};
-export const transform = pipe(transformRequiredFields, transformBin, transformPeerDependenciesMeta);
+export const transform = pipe(transformRequiredFields, transformBin, transformPeerDependenciesMeta, transformRepository);
 //# sourceMappingURL=index.js.map

package/lib/transform/repository.d.ts

@@ -0,0 +1,15 @@
+import type { ProjectManifest } from '@pnpm/types';
+import type { ExportedManifest } from './index.js';
+type Input = Pick<ProjectManifest, 'repository'>;
+type Output<Manifest extends Input> = Omit<Manifest, 'repository'> & Pick<ExportedManifest, 'repository'>;
+/**
+ * Normalizes a string `repository` into the object form `{ type: 'git', url }`.
+ *
+ * npm's `normalize-package-data` performs this conversion before publishing, so a
+ * package whose `repository` is a bare URL string still reaches the registry as an
+ * object. Some registries (e.g. Gitea) reject a string `repository` with a 500
+ * because they decode it into an object-typed struct. Matching npm keeps
+ * `pnpm publish` compatible with them. See https://github.com/pnpm/pnpm/issues/12099.
+ */
+export declare function transformRepository<Manifest extends Input>(manifest: Manifest): Output<Manifest>;
+export {};

package/lib/transform/repository.js

@@ -0,0 +1,21 @@
+/**
+ * Normalizes a string `repository` into the object form `{ type: 'git', url }`.
+ *
+ * npm's `normalize-package-data` performs this conversion before publishing, so a
+ * package whose `repository` is a bare URL string still reaches the registry as an
+ * object. Some registries (e.g. Gitea) reject a string `repository` with a 500
+ * because they decode it into an object-typed struct. Matching npm keeps
+ * `pnpm publish` compatible with them. See https://github.com/pnpm/pnpm/issues/12099.
+ */
+export function transformRepository(manifest) {
+    if (typeof manifest.repository !== 'string')
+        return manifest;
+    return {
+        ...manifest,
+        repository: {
+            type: 'git',
+            url: manifest.repository,
+        },
+    };
+}
+//# sourceMappingURL=repository.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnpm/releasing.exportable-manifest",
-  "version": "1100.1.1",
+  "version": "1100.1.2",
   "description": "Creates an exportable manifest",
   "keywords": [
     "pnpm",
@@ -28,11 +28,11 @@
     "p-map-values": "^0.1.0",
     "ramda": "npm:@pnpm/ramda@0.28.1",
     "@pnpm/catalogs.resolver": "1100.0.0",
-    "@pnpm/bins.resolver": "1100.0.5",
+    "@pnpm/error": "1100.0.0",
     "@pnpm/resolving.jsr-specifier-parser": "1100.0.0",
     "@pnpm/types": "1101.2.0",
     "@pnpm/workspace.project-manifest-reader": "1100.0.9",
-    "@pnpm/error": "1100.0.0"
+    "@pnpm/bins.resolver": "1100.0.5"
   },
   "devDependencies": {
     "@jest/globals": "30.3.0",
@@ -43,8 +43,8 @@
     "@pnpm/catalogs.config": "1100.0.0",
     "@pnpm/catalogs.types": "1100.0.0",
     "@pnpm/hooks.pnpmfile": "1100.0.11",
-    "@pnpm/releasing.exportable-manifest": "1100.1.1",
-    "@pnpm/prepare": "1100.0.11"
+    "@pnpm/prepare": "1100.0.12",
+    "@pnpm/releasing.exportable-manifest": "1100.1.2"
   },
   "engines": {
     "node": ">=22.13"