update package dependencies, and ergonomics updates - #10
Merged
Conversation
fix route.ts for opneai v4
johnprg
pushed a commit
that referenced
this pull request
Dec 23, 2025
[Docs] 'Nice to Have' items' implementation
jpr5
added a commit
that referenced
this pull request
Apr 18, 2026
…(as const) R19-5 #10: Exit-code constants were plain numeric constants, so process.exitCode assignments could drift to any number without a compile error. Make each constant literal (as const), add a PinsExitCode closed union, and route every exit-code assignment through a setExitCode(code: PinsExitCode) helper so typos become compile errors and adding a new exit code is a deliberate edit to both the constant list and the union.
shaneholloman
pushed a commit
to shaneholloman/copilotkit
that referenced
this pull request
Apr 21, 2026
…v titles - titleFromSlug now Title-Cases the result (multimodal-inputs → Multimodal Inputs) instead of returning a lowercased fallback. The lowercase labels previously clashed with the docs-render and reference-breadcrumb conventions elsewhere (finding CopilotKit#10). - Wrap getTitleForSlug in a process-scoped cache with dev-mode invalidation, mirroring reference-items.ts. Previously every entry in NAV_DEFINITION re-opened and re-parsed its MDX file on every request — multiply across ~20 nav entries per render and it added noticeable fs churn (finding CopilotKit#11).
AlemTuzlak
added a commit
that referenced
this pull request
Apr 22, 2026
## CI hygiene fixes Four direct-fix items surfaced during the 2026-04-16 QA/E2E blitz, bundled as one PR with one commit per fix: 1. **`test_unit.yml` paths-ignore** — add `showcase/**` + `sdk-python/**` (prevents spurious TS unit matrix runs on showcase-only or sdk-python-only PRs). `sdk-python-old/**` was mentioned in the plan but doesn't exist on main; only the two existing dirs are added. 2. **`test_doc-examples.yml`** — scope PR trigger to `branches: [main]` (matches convention of other workflows). 3. **`e2e_dojo.yml`** — symmetric `.changeset` path filter on push+PR (was asymmetric — already in the `dorny/paths-filter` step's `ts:` list, so this aligns the trigger). 4. **`starter-smoke.yml`** — rename internal job id (`starter-smoke` → `smoke-starter`) and artifact name pattern (cosmetic; matches the new `test_<layer>-<target>` / `smoke-<layer>` naming convention; no external consumers). ### Fix skipped **`showcase_smoke-monitor.yml` slug normalization** (item #10 in the Notion page) — inspecting the file, it already uses the `showcase/packages/` slug convention (`ms-agent-python`, `ms-agent-dotnet`, `strands`). The apparent inconsistency is actually in `starter-smoke.yml`, whose matrix keys must stay as `ms-agent-framework-*` / `strands-python` because they are literal directory names in `examples/integrations/` (used as `working-directory: examples/integrations/${{ matrix.starter }}`). So there is no actionable change here — the two files use different slug conventions *by necessity*, because they target different directories (deployed `showcase/packages/*` vs. local `examples/integrations/*`). Flagging for the author of the blitz notes in case the actual concern was something else. Refs: [Bugs Found During Blitz](https://www.notion.so/3443aa381852812fb595c5118dd68818) items #3, #8, #9, #12.
jpr5
added a commit
that referenced
this pull request
Jun 12, 2026
…red claimed/running deletes, reclaimed excludes thrown releases, stale window is family-configured (CF7 #10) Contracts-side SweepResult.expiredPending doc needs the sibling edit (out of scope for this branch).
jpr5
added a commit
that referenced
this pull request
Jun 12, 2026
…ong-expired carve-out Sibling of the queue-client prose fix (CF7 #10), which flagged this contract doc as describing only the drain phase: despite the name, the lease phase's long-expired carve-out also claim-deletes claimed/running rows (stale created-age, long-expired or unparseable lease) into this count — no re-queue, no comm error, no reclaimed increment.
huangyingting
pushed a commit
to repomesh/CopilotKit
that referenced
this pull request
Jun 12, 2026
…-side parity (SU7-F1/F2/F3)
SU7-F1 — backend host pattern hardening:
- F1.1 Reject bare trailing ?/# in the backend host pattern
- F1.2 Strip internal tab/CR/LF from the backend host pattern
- F1.3 Warn when ignoring an empty-string local backend override
- F1.4 Reject empty-userinfo @ in the backend host pattern authority
- F1.5 Keep __proto__ keys as data in local-backend maps
- F1.6 Commit the local-backends memo key only after the value computes
- F1.7 Trim local backend overrides before validation and name the real
rejection
- F1.8 Honest FATAL when the pattern host is a stray scheme fragment
- F1.9 Canonicalize the pattern authority for parity with the override
path
- F1.10 Acknowledge the staging-to-prod fail-open in the pattern fallback
- F1.11 Harden backend-url/local-backends-env test hygiene
SU7-F2 — runtime-config & client-config edge cases:
- F2.1 Branch POSTHOG_HOST rejection reasons (scheme/degenerate/parse-
failure) instead of the catch-all mislabel
- F2.2 Reject loopback BASE_URL/DOCS_HOST in production instead of the
silent http:// prepend
- F2.3 Key the DOCS_HOST fallback once-guard on (mode, shellHost, value)
and mode-prefix all value-only guard keys
- F2.4 Reject a present-but-empty posthogKey in the client config reader
- F2.5 Drop the trailing slash from SSR_PLACEHOLDER_URL for structural
parity with server values
- F2.6 Attribute the DOCS_HOST slash-strip to readDocsHost itself
- F2.7 Normalize trailing-dot FQDN spellings in the docs self-host loop
guard (both compare sides)
- F2.8 Harden console spies to capture all log args; pin the full all-env
config shape; converge SSR simulation on vi.stubGlobal
SU7-F3 — script-side parity, table classification & test isolation:
- F3 CopilotKit#1 Handle a missing reference integration per the error contract
- F3 CopilotKit#2 Port the runtime backend-host-pattern normalization into the
generator — scheme/trailing-slash strip, degenerate fallback,
NEXT_PUBLIC fallback
- F3 CopilotKit#3 Treat non-mapping manifest parses (empty/null/scalar/array YAML)
as validation errors, not TypeErrors
- F3 CopilotKit#4 Label a missing/unreadable constraints.yaml per the stderr+exit(1)
error contract
- F3 CopilotKit#5 Align atomic-write tmp naming with the test harness straggler-
sweep convention; guard main() on direct invocation
- F3 CopilotKit#6 Correct the determineCellStatus unshipped docstring; replace
stale hardcoded cell counts with formulas
- F3 CopilotKit#7 Isolate the pattern suite on a per-suite tmpdir harness; snapshot
the generator's full write set
- F3 CopilotKit#8 Classify discarded duplicate wildcards as duplicates — hoist the
owner check above the destination warns
- F3 CopilotKit#9 Reject a root ("/") EXACT seo-redirect source — homepage-hijack
twin of the root-wildcard guard
- F3 CopilotKit#10 Reject seo-redirect entries with non-printable-ASCII source/
destination — close the silent-dead-entry class
- F3 CopilotKit#11 Strip trailing slashes in normalizePosthogHost before the scheme
test
- F3 CopilotKit#12 Message-filter the empty-slug-set error count; pin the single
matcher entry
huangyingting
pushed a commit
to repomesh/CopilotKit
that referenced
this pull request
Jun 18, 2026
…command, and lsof-graceful inspector - Update 12 slot-0-assumption tests for slot-0 reservation contract - Add lsof stub and foundation smoke for isolate.bats - Tests CopilotKit#1-CopilotKit#3: slot pinning behavior - Tests CopilotKit#4-CopilotKit#7: port-probe and stale-reap behavior - Tests CopilotKit#8-CopilotKit#10: slot state, slots subcommand, concurrent claim - New test for _slot_state ports=? when lsof unavailable
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.