@cyanheads/biorxiv-mcp-server 0.2.5 → 0.2.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENTS.md CHANGED
@@ -1,7 +1,7 @@
1
1
  # Agent Protocol
2
2
 
3
3
  **Server:** biorxiv-mcp-server
4
- **Version:** 0.2.5
4
+ **Version:** 0.2.6
5
5
  **Framework:** [@cyanheads/mcp-ts-core](https://www.npmjs.com/package/@cyanheads/mcp-ts-core) `^0.12.3`
6
6
  **Engines:** Bun ≥1.3.0, Node ≥24.0.0
7
7
  **MCP SDK:** `@modelcontextprotocol/server` ^2.0.0
package/CLAUDE.md CHANGED
@@ -1,7 +1,7 @@
1
1
  # Agent Protocol
2
2
 
3
3
  **Server:** biorxiv-mcp-server
4
- **Version:** 0.2.5
4
+ **Version:** 0.2.6
5
5
  **Framework:** [@cyanheads/mcp-ts-core](https://www.npmjs.com/package/@cyanheads/mcp-ts-core) `^0.12.3`
6
6
  **Engines:** Bun ≥1.3.0, Node ≥24.0.0
7
7
  **MCP SDK:** `@modelcontextprotocol/server` ^2.0.0
package/Dockerfile CHANGED
@@ -3,8 +3,16 @@
3
3
  #
4
4
  # This stage installs all dependencies (including dev), builds the TypeScript
5
5
  # source code into JavaScript, and prepares the production assets.
6
+ #
7
+ # Pinned to BUILDPLATFORM, not the target platform. `bun run build` emits
8
+ # platform-independent JavaScript and only `dist/` is copied forward, so this
9
+ # stage has no reason to run under emulation — and under QEMU it does not run
10
+ # at all: Bun's JavaScriptCore aborts with a spurious MemoryExhaustion
11
+ # assertion (~21 MB peak), so a cross-arch build of this stage fails outright
12
+ # on an arm64 host. Building natively also removes emulation from the slowest
13
+ # stage of a multi-arch build.
6
14
  # ==============================================================================
7
- FROM oven/bun:1.4.0 AS build
15
+ FROM --platform=$BUILDPLATFORM oven/bun:1.4.0 AS build
8
16
 
9
17
  WORKDIR /usr/src/app
10
18
 
package/README.md CHANGED
@@ -7,7 +7,7 @@
7
7
 
8
8
  <div align="center">
9
9
 
10
- [![Version](https://img.shields.io/badge/Version-0.2.5-blue.svg?style=flat-square)](./CHANGELOG.md) [![License](https://img.shields.io/badge/License-Apache%202.0-orange.svg?style=flat-square)](./LICENSE) [![Docker](https://img.shields.io/badge/Docker-ghcr.io-2496ED?style=flat-square&logo=docker&logoColor=white)](https://github.com/users/cyanheads/packages/container/package/biorxiv-mcp-server) [![MCP SDK](https://img.shields.io/badge/MCP%20SDK-^2.0.0-green.svg?style=flat-square)](https://modelcontextprotocol.io/) [![npm](https://img.shields.io/npm/v/@cyanheads/biorxiv-mcp-server?style=flat-square&logo=npm&logoColor=white)](https://www.npmjs.com/package/@cyanheads/biorxiv-mcp-server) [![TypeScript](https://img.shields.io/badge/TypeScript-^7.0.2-3178C6.svg?style=flat-square)](https://www.typescriptlang.org/) [![Bun](https://img.shields.io/badge/Bun-v1.4.0-blueviolet.svg?style=flat-square)](https://bun.sh/)
10
+ [![Version](https://img.shields.io/badge/Version-0.2.6-blue.svg?style=flat-square)](./CHANGELOG.md) [![License](https://img.shields.io/badge/License-Apache%202.0-orange.svg?style=flat-square)](./LICENSE) [![Docker](https://img.shields.io/badge/Docker-ghcr.io-2496ED?style=flat-square&logo=docker&logoColor=white)](https://github.com/users/cyanheads/packages/container/package/biorxiv-mcp-server) [![MCP SDK](https://img.shields.io/badge/MCP%20SDK-^2.0.0-green.svg?style=flat-square)](https://modelcontextprotocol.io/) [![npm](https://img.shields.io/npm/v/@cyanheads/biorxiv-mcp-server?style=flat-square&logo=npm&logoColor=white)](https://www.npmjs.com/package/@cyanheads/biorxiv-mcp-server) [![TypeScript](https://img.shields.io/badge/TypeScript-^7.0.2-3178C6.svg?style=flat-square)](https://www.typescriptlang.org/) [![Bun](https://img.shields.io/badge/Bun-v1.4.0-blueviolet.svg?style=flat-square)](https://bun.sh/)
11
11
 
12
12
  </div>
13
13
 
@@ -0,0 +1,11 @@
1
+ ---
2
+ summary: "Fixes the GHCR build stage that made 0.2.5 ship with no container image — this is the first tagged image, carrying everything 0.2.5 shipped elsewhere"
3
+ breaking: false
4
+ security: false
5
+ ---
6
+
7
+ # 0.2.6 — 2026-08-25
8
+
9
+ ## Fixed
10
+
11
+ - **Docker build stage no longer fails under emulation** — the build stage now pins `FROM --platform=$BUILDPLATFORM oven/bun:1.4.0 AS build` instead of building for the target platform. On an arm64 build host, the `linux/amd64` leg previously ran under QEMU, where Bun 1.4.0's JavaScriptCore aborted with a spurious MemoryExhaustion assertion during `bun run build`; the stage only emits platform-independent JavaScript and `dist/` is the sole artifact copied forward, so it never needed emulation. This is what blocked 0.2.5's GHCR publish — that release has no image on GHCR. `0.2.6` is the first tagged image, and it also carries `@cyanheads/mcp-ts-core` 0.12.3 and the other 0.2.5 changes that published everywhere else.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cyanheads/biorxiv-mcp-server",
3
- "version": "0.2.5",
3
+ "version": "0.2.6",
4
4
  "mcpName": "io.github.cyanheads/biorxiv-mcp-server",
5
5
  "description": "Search and retrieve bioRxiv and medRxiv preprints — by DOI, date interval, or keyword — via MCP. STDIO or Streamable HTTP.",
6
6
  "type": "module",
package/server.json CHANGED
@@ -6,14 +6,14 @@
6
6
  "url": "https://github.com/cyanheads/biorxiv-mcp-server",
7
7
  "source": "github"
8
8
  },
9
- "version": "0.2.5",
9
+ "version": "0.2.6",
10
10
  "packages": [
11
11
  {
12
12
  "registryType": "npm",
13
13
  "registryBaseUrl": "https://registry.npmjs.org",
14
14
  "identifier": "@cyanheads/biorxiv-mcp-server",
15
15
  "runtimeHint": "bun",
16
- "version": "0.2.5",
16
+ "version": "0.2.6",
17
17
  "packageArguments": [
18
18
  {
19
19
  "type": "positional",
@@ -62,7 +62,7 @@
62
62
  "registryBaseUrl": "https://registry.npmjs.org",
63
63
  "identifier": "@cyanheads/biorxiv-mcp-server",
64
64
  "runtimeHint": "bun",
65
- "version": "0.2.5",
65
+ "version": "0.2.6",
66
66
  "packageArguments": [
67
67
  {
68
68
  "type": "positional",