chore(core): point wren-core-py / wren / wren-core-wasm at Canner/WrenAI by goldmedal · Pull Request #2230 · Canner/WrenAI

goldmedal · 2026-05-04T06:59:13Z

Summary

After the wren-engine import, the canonical repo URL is Canner/WrenAI. The published package manifests still pointed at Canner/wren-engine. Updating them so PyPI / npm / crates.io show the correct Repository and Issues links.

Changes

File	Field
`core/wren-core-py/Cargo.toml`	`repository`
`core/wren-core-py/pyproject.toml`	`Repository`, `Issues`
`core/wren/pyproject.toml`	`Repository`, `Issues`
`core/wren-core-wasm/Cargo.toml`	`repository`
`core/wren-core-wasm/package.json`	`repository.url` + `repository.directory` (now `core/wren-core-wasm`)

Intentionally NOT changed

CHANGELOG.md historical links (core/wren-core-py/CHANGELOG.md, core/wren/CHANGELOG.md) — those reference real wren-engine PR numbers and commits. The archived Canner/wren-engine repo will keep resolving them; rewriting to Canner/WrenAI would dangle (different PR numbering on the new repo).
core/wren-core/Cargo.toml — workspace root, no repository field set; sub-crates inherit nothing for this field.

🤖 Generated with Claude Code

Summary by CodeRabbit

Chores
- Updated package metadata and repository/issue links to point to the new WrenAI locations.
Documentation
- Updated installation and CDN examples to use the new scoped package name and adjusted example import URLs so guides and quick-start snippets reflect the new package identity.

After the import, the canonical repo URL is Canner/WrenAI rather than the now-archived Canner/wren-engine. Updates the package manifests so PyPI / npm / crates.io display the correct Repository / Issues links: - core/wren-core-py/Cargo.toml repository - core/wren-core-py/pyproject.toml Repository, Issues - core/wren/pyproject.toml Repository, Issues - core/wren-core-wasm/Cargo.toml repository - core/wren-core-wasm/package.json repository.url + repository.directory (now core/wren-core-wasm under the new layout) CHANGELOG entries that link to historical wren-engine PR numbers/commits are intentionally left alone — those resolve against the archived wren-engine repo and would dangle if rewritten to WrenAI's renumbered PR space.

coderabbitai · 2026-05-04T06:59:26Z

Walkthrough

Repository and package metadata URLs were updated across manifests and docs to point from https://github.com/Canner/wren-engine to https://github.com/Canner/WrenAI, and the npm package name/registry import was changed to @wrenai/wren-core-wasm.

Changes

Repository Metadata Migration

Layer / File(s)	Summary
Cargo Manifests `core/wren-core-py/Cargo.toml`, `core/wren-core-wasm/Cargo.toml`	`[package].repository` updated to `https://github.com/Canner/WrenAI`.
Python Project Metadata `core/wren-core-py/pyproject.toml`, `core/wren/pyproject.toml`	`[project.urls]` `Repository` and `Issues` links changed to `https://github.com/Canner/WrenAI` and issues page.
Node package identity `core/wren-core-wasm/package.json`	`name` changed to `@wrenai/wren-core-wasm`; `repository.url` set to `https://github.com/Canner/WrenAI.git` and `repository.directory` to `core/wren-core-wasm`; `homepage`/`bugs.url` updated.
Docs / Examples `core/wren-core-wasm/README.md`, `core/wren-core-wasm/AGENT_GUIDE.md`, `core/wren-core-wasm/examples/test-cdn.html`	CDN/import snippets and install examples updated to use `@wrenai/wren-core-wasm` import paths/URLs.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

PaulChen79
cyyeh

Poem

🐰 I hopped through files both near and far,
Swapped links to WrenAI, a shiny star.
Package names scoped, the docs now gleam,
A tiny hop toward a brighter dream. 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes the main change: updating repository URLs across multiple core packages from Canner/wren-engine to Canner/WrenAI.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch chore/update-repo-urls

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

@WrenAI

Adopt the @WrenAI npm org scope so the package lives under a namespace we own, and add publishConfig.access=public so first publish doesn't trip on scoped packages defaulting to private. Update README, AGENT_GUIDE and the CDN example to match the new import path. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@core/wren-core-wasm/examples/test-cdn.html`:
- Line 41: The import in test-cdn.html (import { WrenEngine } from
'https://unpkg.com/@wrenai/wren-core-wasm@0.1.0/dist/index.js') points to an
unpublished package and will 404; either publish the
`@wrenai/wren-core-wasm`@0.1.0 package to npm so the unpkg URL resolves, or update
this import (and the same reference in README.md and AGENT_GUIDE.md) to a
published version or a local/dev CDN URL; ensure the chosen version string in
the import matches the package version you publish.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: cf150011-ed32-4210-8307-c1f14aea0907

📥 Commits

Reviewing files that changed from the base of the PR and between 4aceaf0 and 237fde8.

📒 Files selected for processing (4)

core/wren-core-wasm/AGENT_GUIDE.md
core/wren-core-wasm/README.md
core/wren-core-wasm/examples/test-cdn.html
core/wren-core-wasm/package.json

✅ Files skipped from review due to trivial changes (2)

core/wren-core-wasm/AGENT_GUIDE.md
core/wren-core-wasm/README.md

🚧 Files skipped from review as they are similar to previous changes (1)

core/wren-core-wasm/package.json

coderabbitai · 2026-05-04T07:28:49Z

        // unpkg used instead of jsDelivr: jsDelivr's free CDN has a 50 MB per-file
        // limit and the WASM binary is ~68 MB raw. unpkg handles larger files.
-        import { WrenEngine } from 'https://unpkg.com/wren-core-wasm@0.1.0/dist/index.js';
+        import { WrenEngine } from 'https://unpkg.com/@wrenai/wren-core-wasm@0.1.0/dist/index.js';


⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Is @wrenai/wren-core-wasm published on npm?

💡 Result:

No, @wrenai/wren-core-wasm is not published on npm.

Citations:

1: https://github.com/Canner/wren-engine/releases/tag/wren-v0.3.0

2: https://libraries.io/pypi/wren-core-py

3: https://pypi.org/project/wren-engine/

Publish @wrenai/wren-core-wasm@0.1.0 to npm before merging.

The unpkg CDN URL will fail to load (404) because @wrenai/wren-core-wasm@0.1.0 is not published on npm. This breaks the example code entirely. The same URL is referenced in README.md and AGENT_GUIDE.md, so publishing the package is a blocking dependency for this and other consumer-facing docs.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed. In `@core/wren-core-wasm/examples/test-cdn.html` at line 41, The import in test-cdn.html (import { WrenEngine } from 'https://unpkg.com/@wrenai/wren-core-wasm@0.1.0/dist/index.js') points to an unpublished package and will 404; either publish the `@wrenai/wren-core-wasm`@0.1.0 package to npm so the unpkg URL resolves, or update this import (and the same reference in README.md and AGENT_GUIDE.md) to a published version or a local/dev CDN URL; ensure the chosen version string in the import matches the package version you publish.

github-actions Bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code rust Pull requests that update rust code core wasm labels May 4, 2026

goldmedal requested a review from PaulChen79 May 4, 2026 07:03

goldmedal and others added 2 commits May 4, 2026 15:19

chore: npm pkg fix

237fde8

github-actions Bot added the documentation Improvements or additions to documentation label May 4, 2026

coderabbitai Bot reviewed May 4, 2026

View reviewed changes

PaulChen79 approved these changes May 4, 2026

View reviewed changes

goldmedal merged commit a63ee3d into main May 4, 2026
17 checks passed

goldmedal deleted the chore/update-repo-urls branch May 4, 2026 07:55

This was referenced May 5, 2026

fix(ci): split wasm RC publish into a token-based workflow #2240

Merged

docs: post-rebrand cleanup — core docs naming, README quick start, quickstart skill repo #2246

Merged

This was referenced May 15, 2026

docs(wren-core-wasm): refresh onboarding for inline-mode default #2290

Merged

fix(skills): refresh stale docs URLs and wren-engine repo references #2304

Merged

chore(wren)!: rename PyPI package from wren-engine to wrenai #2315

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(core): point wren-core-py / wren / wren-core-wasm at Canner/WrenAI#2230

chore(core): point wren-core-py / wren / wren-core-wasm at Canner/WrenAI#2230
goldmedal merged 3 commits into
mainfrom
chore/update-repo-urls

goldmedal commented May 4, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented May 4, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot left a comment

Uh oh!

coderabbitai Bot May 4, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

goldmedal commented May 4, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Intentionally NOT changed

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented May 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Suggested reviewers

Poem

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot May 4, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

goldmedal commented May 4, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented May 4, 2026 •

edited

Loading