Skip to content

Release 0.2.4: fix JSR publish Deno panic - #56

Merged
proxymesh merged 2 commits into
mainfrom
release/0.2.4
Sep 1, 2026
Merged

Release 0.2.4: fix JSR publish Deno panic#56
proxymesh merged 2 commits into
mainfrom
release/0.2.4

Conversation

@proxymeshai

Copy link
Copy Markdown
Collaborator

Summary

  • 0.2.3 published to npm but failed on JSR: Deno panicked while rewriting bare net/tls/https imports (overlapping text changes on JSDoc import('net')).
  • Prefix Node builtins with node: so JSR no longer needs that rewrite.
  • Bump package.json and jsr.json to 0.2.4 so merge can cut v-0.2.4 and republish both registries.

Verification

  • npx jsr publish --dry-run succeeds after the import fix (previously panicked).
  • npm run test:unit passes.

Merging triggers GitHub release v-0.2.4 and npm/JSR publish via existing workflows.

Slack Thread

Open in Web Open in Cursor 

Deno's bare-node-builtins rewrite overlaps on JSDoc import('net')
and crashes during jsr publish. Prefix Node builtins with node: and
bump to 0.2.4 so npm/JSR can republish after 0.2.3's partial publish.

Co-authored-by: ProxyMesh AI <proxymeshai@users.noreply.github.com>
@proxymeshai
proxymeshai marked this pull request as ready for review September 1, 2026 18:18
@cursor
cursor Bot requested a review from proxymesh September 1, 2026 18:20

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a non-blocking comment and assigned reviewers. This is not a Dependabot package-version bump, so it is outside this automation’s approval policy even though Cursor Bugbot completed successfully with no findings (Cursor Security Agent was not present). Human review is required before merge.

Open in Web View Automation 

Sent by Cursor Approval Agent: dependabot approver

@proxymesh
proxymesh merged commit 3df77d5 into main Sep 1, 2026
1 check passed
@proxymesh
proxymesh deleted the release/0.2.4 branch September 1, 2026 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants