Skip to content

chore(effect): release 0.1.0 - #325

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--effect
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--effect

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.1.0 (2026-11-03)

Initial release of @coder/ai-sdk-effect, an Effect bridge that exposes a LanguageModel over CoderAgent with structured error classification and per-call generation options. This version targets Effect 4 and supports Effect 4.1.

Highlights

  • Published the @coder/ai-sdk-effect package providing an Effect-based LanguageModel over CoderAgent. (#324)
  • Migrated the bridge to Effect 4 with support for Effect 4.1. (#425)
  • Added per-call generation options including agent model and reasoning effort. (#242)
  • Classified agent errors, mapping 402 responses to quota errors that carry raw usage data. (#328)
  • Fixed error classification so InvalidResponseError is treated as a malformed-response error. (#381)

Features

  • effect: add a LanguageModel over CoderAgent (#241) (277c0ce)
  • effect: add Effect bridge spike package (#145) (1dce33f)
  • effect: add per-call agent model and reasoning effort options (#242) (286e947)
  • effect: classify 402 as quota and carry raw usage (#328) (6fb4c63)
  • effect: classify agent errors and add per-call generation options (#240) (fd2eabe)
  • effect: forward toolChoice unconditionally and add a live tool-call case (#319) (ef6a0c0)
  • effect: migrate bridge to effect 4 (#320) (661c4c2)
  • effect: publish @coder/ai-sdk-effect (#324) (3e44f02)
  • effect: support effect 4.1 (#425) (127c96e)

Bug Fixes

  • effect: classify InvalidResponseError as malformed-response (#381) (3098d5b)

Documentation

  • effect: drop leftover spike wording from source comments (#331) (056fe9b)
  • rewrite READMEs for readability and split long guides into docs/ (#234) (1c5079b)

This PR was generated with Release Please. See documentation.

@ThomasK33

Copy link
Copy Markdown
Member

Hold: do not merge this PR until the npm trusted publisher for @coder/ai-sdk-effect exists. The owner steps are in #324 under "Owner steps".

  1. The owner publishes a 0.0.0 name placeholder and deprecates it.
  2. The owner adds the trusted publisher for coder/ai-sdk and release-please.yml, with npm publish allowed.
  3. The maintainer merges this PR within 48 hours of step 2. publish-effect then publishes 0.1.0 through OIDC with provenance.

A new trusted-publisher setup expires if it doesn't complete a publish within 2 days, so step 3 must follow step 2 promptly.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: medium

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--effect branch from 2415d8b to bb589a5 Compare October 12, 2026 17:44
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--effect branch 24 times, most recently from 94e9044 to 24a6d7a Compare October 16, 2026 04:02
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--effect branch 3 times, most recently from a8a9280 to 9f025e0 Compare October 23, 2026 16:09
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--effect branch 11 times, most recently from dfab48a to b717367 Compare October 24, 2026 21:04
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--effect branch 9 times, most recently from 0c5fb6d to da76174 Compare October 27, 2026 21:34
@ThomasK33

ThomasK33 commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

Note on the new Documentation entry. It comes from #418, which adds EGM.md contract files only. Those files are not in the npm tarball. #418's squash commit body repeated the branch commit's docs: subject, and release-please read that line as a second, visible commit. I added a BEGIN_COMMIT_OVERRIDE block with the chore: subject to the #418 body. The next release-please run on main drops this entry. The rest of this release PR is unchanged.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: xhigh

@ThomasK33

Copy link
Copy Markdown
Member

Update: the release-please run after #422 applied the override. This PR no longer lists the #418 entry. The rest of the release is unchanged.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: xhigh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant