Skip to content

OpenCode v1.1.43#103

Merged
catrielmuller merged 307 commits intodevfrom
catrielmuller/kilo-opencode-v1.1.43
Feb 4, 2026
Merged

OpenCode v1.1.43#103
catrielmuller merged 307 commits intodevfrom
catrielmuller/kilo-opencode-v1.1.43

Conversation

@catrielmuller
Copy link
Collaborator

https://github.com/anomalyco/opencode/releases/tag/v1.1.43

  • Transferred the kilo translation to packages/kilo-i18n.
  • This PR was generated using the transformed upstream merge script (Upstream Merge Automation #102), so some conflicts were resolved in favor of the script's outcome.

actions-user and others added 30 commits January 26, 2026 18:50
@catrielmuller catrielmuller changed the title OenCode v1.1.43 OpenCode v1.1.43 Feb 3, 2026
on:
push:
branches: [dev]
pull_request:
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: pull_request trigger likely can't write/push to beta (and may be unsafe if it ever can)

This job needs contents: write and runs bun script/beta.ts which force-pushes the beta branch. On pull_request events from forks, GITHUB_TOKEN is typically read-only and secrets are unavailable, so this workflow usually can't push. If the intent is to run the sync when a maintainer-applied label is present, pull_request_target + a safe checkout strategy (avoid executing PR code) is usually the workable pattern.

push:
branches:
- dev
pull_request:
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: pull_request trigger + commit/push step will fail or behave unexpectedly for forks

This workflow later runs git push origin HEAD:${{ github.ref_name }}. On pull_request events, github.ref_name is not the head branch name (often NNN/merge), and for fork PRs the token typically cannot push to the fork anyway. Consider guarding to same-repo PRs only (or switching to pull_request_target with tight constraints) to avoid noisy failures.

const cmd = strings.reduce((acc, str, i) => acc + str + (values[i] ?? ""), "")
return {
async nothrow() {
const proc = Bun.spawn(cmd.split(" "), {
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: cmd.split(" ") argument parsing is brittle and can break commands

In $(...), using cmd.split(" ") will mis-handle quoted args, paths with spaces, and any future interpolations that include whitespace. This can cause hard-to-diagnose failures (or, if values ever become user-influenced, opens the door to argument injection). Prefer Bun's built-in $ (from bun) or Bun.spawn([cmd, ...args]) with an explicit argv array.

1. Check the logs for error messages
2. Try running with `--print-logs` to see output in the terminal
3. Ensure you have the latest version with `opencode upgrade`
3. Ensure you have the latest version with `kilo upgrade`
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: Docs command likely incorrect (kilo binary may not exist)

This repo appears to expose the CLI as opencode (see packages/opencode/package.json bin), so kilo upgrade is likely a broken command for users.

Suggested change
3. Ensure you have the latest version with `kilo upgrade`
3. Ensure you have the latest version with `opencode upgrade`

let output = [`version=${Script.version}`]

if (!Script.preview) {
await $`gh release create v${Script.version} -d --title "v${Script.version}" ${Script.preview ? "--prerelease" : ""}`
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: Dead Script.preview check + possible empty CLI arg

This block only runs when !Script.preview, so ${Script.preview ? "--prerelease" : ""} can never add --prerelease. Also, interpolating "" into Bun’s $`` can pass an empty argument to gh`, which may be treated as an (invalid) asset path.

Suggested change
await $`gh release create v${Script.version} -d --title "v${Script.version}" ${Script.preview ? "--prerelease" : ""}`
await $`gh release create v${Script.version} -d --title "v${Script.version}"`

If you do want prereleases for preview builds, the surrounding if (!Script.preview) likely needs restructuring so preview runs gh release create with --prerelease.

const previous = await getLatestRelease()
const notes = await buildNotes(previous, "HEAD")
// notes.unshift(highlightsTemplate)
await $`git commit -am "release: v${Script.version}"`
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: Release publish can fail when there’s nothing to commit

git commit -am ... exits non-zero if there are no changes (e.g. rerunning the script or if version files were already updated), and Bun’s $`` throws on non-zero exits. Consider guarding with git status --porcelain/git diff --quiet` before committing (or handle the “nothing to commit” case explicitly).

await $`git commit -am "release: v${Script.version}"`
await $`git tag v${Script.version}`
await $`git fetch origin`
await $`git cherry-pick HEAD..origin/dev`.nothrow()
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: Cherry-pick failures are ignored

git cherry-pick ....nothrow() returns { exitCode, stdout, stderr }, but the result is ignored. If the cherry-pick fails (conflicts, empty range, etc.), the script will still push tags/branches and edit the release notes, which can leave the release in a partially-updated state.


- Big Pickle is a stealth model that's free on OpenCode for a limited time. The team is using this time to collect feedback and improve the model.
- GLM 4.7 Free is available on Kilo for a limited time. The team is using this time to collect feedback and improve the model.
- Kimi M2.5 Free is available on Kilo for a limited time. The team is using this time to collect feedback and improve the model.
Copy link
Contributor

Choose a reason for hiding this comment

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

SUGGESTION: Typo in model name (Kimi M2.5Kimi K2.5)

Suggested change
- Kimi M2.5 Free is available on Kilo for a limited time. The team is using this time to collect feedback and improve the model.
- Kimi K2.5 Free is available on Kilo for a limited time. The team is using this time to collect feedback and improve the model.

@kiloconnect
Copy link
Contributor

kiloconnect bot commented Feb 3, 2026

Code Review Summary

Status: 10 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 9
SUGGESTION 1
Issue Details (click to expand)

WARNING

File Line Issue
packages/web/src/content/docs/zen.mdx 67 Docs endpoint URL has duplicated scheme (https://https://), breaking the link
packages/web/src/content/docs/zen.mdx 107 Models list URL has duplicated scheme (https://https://), breaking the link
script/version.ts 9 Dead Script.preview check + possible empty CLI arg in gh release create
script/publish.ts 64 Release publish can fail when there’s nothing to commit
script/publish.ts 67 Cherry-pick failures are ignored (result of .nothrow() unused)
packages/web/src/content/docs/themes.mdx 68 $schema URL likely should remain opencode.ai (docs consistency)
packages/web/src/content/docs/themes.mdx 147 Theme schema URL likely should remain opencode.ai
packages/web/src/content/docs/tools.mdx 18 $schema URL likely should remain opencode.ai
.github/workflows/pr-management.yml 85 Contributor label condition likely misses most external PR authors

SUGGESTION

File Line Issue
packages/web/src/content/docs/zen.mdx 159 Typo in model name (Kimi M2.5Kimi K2.5)
Other Observations (not in diff)

Issues found in unchanged code that cannot receive inline comments:

File Line Issue
(none)
Files Reviewed (10 files)

Fix these issues in Kilo Cloud

```json title="opencode.json" {3}
{
"$schema": "https://opencode.ai/config.json",
"$schema": "https://kilo.ai/config.json",
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: $schema URL likely should remain opencode.ai (docs consistency)

Existing docs/comments indicate schemas stay https://opencode.ai/...; switching to kilo.ai may break editor validation until the schema is published there.

Suggested change
"$schema": "https://kilo.ai/config.json",
"$schema": "https://opencode.ai/config.json",

```json title="my-theme.json"
{
"$schema": "https://opencode.ai/theme.json",
"$schema": "https://kilo.ai/theme.json",
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: Theme schema URL likely should remain opencode.ai

If the theme schema isn’t hosted at kilo.ai yet, this change will break validation for custom theme files.

Suggested change
"$schema": "https://kilo.ai/theme.json",
"$schema": "https://opencode.ai/theme.json",

```json title="opencode.json"
{
"$schema": "https://opencode.ai/config.json",
"$schema": "https://kilo.ai/config.json",
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: $schema URL likely should remain opencode.ai

Other docs in this PR were flagged for the same change; if kilo.ai/config.json isn’t guaranteed to exist, keeping opencode.ai avoids broken schema validation for users.

Suggested change
"$schema": "https://kilo.ai/config.json",
"$schema": "https://opencode.ai/config.json",

const issueNumber = isPR ? context.payload.pull_request.number : context.payload.issue.number;
const authorAssociation = isPR ? context.payload.pull_request.author_association : context.payload.issue.author_association;

if (authorAssociation === 'CONTRIBUTOR') {
Copy link
Contributor

Choose a reason for hiding this comment

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

WARNING: Contributor label condition likely misses most external PR authors

pull_request.author_association commonly returns FIRST_TIME_CONTRIBUTOR / FIRST_TIMER for new community PRs (and NONE in some cases). Checking only CONTRIBUTOR may skip labeling the majority of non-member PRs. Consider including the first-time values or inverting the check (eg, label when association is not MEMBER/OWNER/COLLABORATOR).

@catrielmuller catrielmuller merged commit 0699a35 into dev Feb 4, 2026
10 checks passed
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.