Skip to content

chore: sync upstream opencode (2982 commits)#198

Open
kevint-cerebras wants to merge 2983 commits into
devfrom
auto/sync-upstream-20260503
Open

chore: sync upstream opencode (2982 commits)#198
kevint-cerebras wants to merge 2983 commits into
devfrom
auto/sync-upstream-20260503

Conversation

@kevint-cerebras
Copy link
Copy Markdown
Owner

Automated sync from sst/opencode dev branch.

2982 new commits from upstream.

Had merge conflicts — accepted upstream versions. The sync-fix workflow will automatically build, test, and restore any overwritten customizations.

Brendonovich and others added 30 commits April 28, 2026 15:51
…738)

Co-authored-by: Andrew Avsenin <snatvb@ya.ru>
Reject negative and fractional sync sequence values in Effect HttpApi schemas so replay/history validation matches the legacy Hono routes.
Document legacy 400 bad-request responses on TUI Effect HttpApi payload-validation endpoints and cover them with OpenAPI parity tests.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: jiwenshang <jiwenshang@xiaohongshu.com>
rekram1-node and others added 28 commits May 2, 2026 21:43
Switch triage agent to gpt-5.4-nano for faster issue assignment. Remove label
management from the triage tool so it only assigns owners based on team
ownership rules. This reduces noise in the issue tracker and ensures issues
get to the right team member immediately without unnecessary labels.

Update team structures to reflect current ownership and add script for
processing unassigned issues.
Removes the automated vouch system that filtered issues and PRs from non-vouched users. This simplifies the contribution process by removing the requirement for maintainers to manually vouch contributors before they can participate.
This script was used to batch-triage open GitHub issues without assignees.
Removing as the triage workflow has evolved and this batch approach is no longer needed.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 3, 2026

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

  1. Open an issue describing the bug/feature (if one doesn't exist)
  2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

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.