Publish version v0.2.27

[Kitenite]

Description

Related Issues

Type of Change

• Bug fix
• New feature
• Documentation update
• Release
• Refactor
• Other (please describe):

Testing

Screenshots (if applicable)

Additional Notes

---

Important

Update version to v0.2.27 and modify anthropic-beta header handling in LlmManager and getAnthropicProvider.

• Release:
  • Update version in package.json from 0.2.26 to 0.2.27.
• Headers:
  • Remove anthropic-beta header from LlmManager in index.ts.
  • Add anthropic-beta header to getAnthropicProvider in llmProvider.ts.

^{This description was created by for fad59bf. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to fad59bf in 1 minute and 12 seconds

More details

• Looked at 39 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 7 drafted comments based on config settings.

1. apps/studio/electron/main/chat/index.ts:91

• Draft comment:
  Removed local 'anthropic-beta' header; ensure this is correctly set via llmProvider.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. apps/studio/electron/main/chat/llmProvider.ts:46

• Draft comment:
  Added 'anthropic-beta' header to config; confirm it meets API requirements and there's no duplication/conflict.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. apps/studio/package.json:4

• Draft comment:
  Version bump to 0.2.27 looks good; verify that release notes and documentation (e.g., onboarding docs) are updated elsewhere if required.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

4. apps/studio/electron/main/chat/index.ts:91

• Draft comment:
  Removed the 'anthropic-beta' header from the stream config; header is now configured in the provider. Ensure this change maintains consistent behavior.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

5. apps/studio/electron/main/chat/llmProvider.ts:48

• Draft comment:
  Added the 'anthropic-beta' header to the provider config when using auth tokens. Confirm if this header should also be applied when using an API key for consistency.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
  This is a speculative comment asking the author to verify something. It's asking "should we also do X?" rather than stating a clear problem. The comment is about a change (the new header), but it's not identifying an actual issue - just raising a question. Per the rules, we should not ask authors to verify or confirm things.
  The comment does point out a potential inconsistency in the codebase that could be worth addressing. Maybe there's a real technical reason this header should be in both places?
  While the inconsistency is worth noting, without strong evidence that the header is definitely required in both paths, this remains a speculative comment asking for verification - exactly what the rules say to avoid.
  Delete this comment as it's speculative and asks for verification rather than identifying a clear issue requiring changes.

6. apps/studio/package.json:4

• Draft comment:
  Version bump to 0.2.27 is correct. However, the PR description mentions onboarding documentation improvements, yet no documentation changes are present. Please verify that all intended updates are included.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is asking the PR author to verify that all intended updates are included, which violates the rule against asking the author to confirm their intention or to update the PR description. It does not provide a specific code suggestion or point out a specific issue in the code.

7. apps/studio/package.json:30

• Draft comment:
  Typographical error: The script name 'pree2e' seems off. It might be intended as 'pre:e2e' or another naming convention. Please confirm and correct if necessary.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_bXkREeAxVS0GFPhK

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.