Repository navigation
chore(release): version packages - #1455
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| { | ||
| "name": "@maple-dev/effect-sdk", | ||
| "version": "0.10.0", | ||
| "version": "0.10.1", |
There was a problem hiding this comment.
🔴 Stale lockfile blocks package releases
After these version bumps, bun install --frozen-lockfile rejects the unchanged workspace versions in bun.lock. Release and CI jobs use frozen installs, so the packages cannot publish.
Learn more
The workspace lockfile records the versions of the CLI, example, alchemy provider, and Effect SDK. All four package manifests changed, but their lockfile records still contain the old versions. The release workflow and CI install action use frozen installs, which refuse a stale lockfile. The binary release workflow does as well.
Example: With the SDK manifest at 0.10.1 and its lockfile workspace entry at 0.10.0, the release job stops at its frozen install before it reaches publishing.
Recommended fix: Regenerate and commit bun.lock with bun install --lockfile-only, then verify bun install --frozen-lockfile succeeds.
Was this helpful? React with 👍 or 👎 to provide feedback.
| { | ||
| "name": "@maple-dev/effect-sdk", | ||
| "version": "0.10.0", | ||
| "version": "0.10.1", |
There was a problem hiding this comment.
🟡 SDK telemetry retains previous release version
When publishing 0.10.1, SDK_VERSION remains 0.10.0 in the SDK version constant. Exported telemetry identifies the new release as the old one, and the version test fails.
Learn more
The published package version and the SDK's embedded version are separate values. The SDK version constant remains 0.10.0, and exporters embed it in their HTTP headers. The version test checks equality with the manifest.
Example: An app using the newly published @maple-dev/effect-sdk@0.10.1 sends maple-effect-sdk-server/0.10.0 as its exporter user-agent. Telemetry from 0.10.0 and 0.10.1 then looks identical by SDK version.
Recommended fix: Update SDK_VERSION alongside the manifest to 0.10.1 and run the SDK version test before publishing.
Was this helpful? React with 👍 or 👎 to provide feedback.
22d3aa4 to
2c526e6
Compare
2c526e6 to
52819f6
Compare
Release #1455 bumped package.json to 0.10.1 but left SDK_VERSION at 0.10.0, so version.test.ts fails on main and the published SDK reports the old version in its user-agent.
* feat(mcp): expose integrations through the MCP list_integrations reports each connected integration (GitHub, Cloudflare, Railway, PlanetScale, Prometheus scrape targets, chat workspaces), what it feeds, and which resources are failing, stale or disconnected, from Maple's own poller and sync state. list_infra and inspect_infra gain provider kinds: cloudflare_zones, cloudflare_workers, railway_services and planetscale_databases, on the same queries as the web infra pages. A zone inspects by section (traffic, breakdown, security, dns). The overview reads a provider's kinds only when that integration is connected. * fix(effect-sdk): sync SDK_VERSION with the 0.10.1 release Release #1455 bumped package.json to 0.10.1 but left SDK_VERSION at 0.10.0, so version.test.ts fails on main and the published SDK reports the old version in its user-agent. * fix(browser): sync SDK_VERSION with the 0.11.0 release Same miss as effect-sdk: package.json is 0.11.0 but SDK_VERSION stayed at 0.10.1, which fails version.test.ts.
1 participant
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@maple-dev/browser@0.11.0
Minor Changes
c060d5d: New
privacy.persistence: "memory"mode keeps all SDK state in memory: no cookies, localStorage, sessionStorage or IndexedDB, and no visitor id. Like consent, the setting is page-global and only ever tightens.Opting out now deletes the SDK's cookies on every parent domain instead of probing for them, so an opt-out never writes a cookie and also clears ids written under a broader domain.
@maple-dev/alchemy@0.2.1
Patch Changes
@maple-dev/effect-sdk@0.10.1
Patch Changes
HttpServerErrorResponseexception on Effect 4.0.2 and later, which now fails the span itself with anHttpServerErrorfor any 5xx response. Without this, those responses were grouped as one genericHttpServerErrorissue.@maple/cli@0.0.27
Patch Changes
maple service-mapnow lists the databases services call (fromdb.system.nameanddb.namespace), and with-s <service>that service's external HTTP, messaging and RPC calls, so dependencies that run no OpenTelemetry SDK show up in the terminal too. The JSON output is now an object:edges,databases, andexternalwhen-sis set.-snow keeps only the edges touching that service, inbound and outbound, filtered in the query rather than from the top 200 edges, and an unknown service name lists the known ones. Remote mode prints service edges only, and its-skeeps outbound edges.@maple-examples/effect-todo@0.0.1
Patch Changes