chore(deps): bump next from 15.6.0-canary.58 to 16.1.7#5
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
chore(deps): bump next from 15.6.0-canary.58 to 16.1.7#5dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/next-16.1.7
branch
3 times, most recently
from
e4abd00 to
d80bf65
Compare
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/next-16.1.7
branch
2 times, most recently
from
fc88353 to
b9b47b9
Compare
Bumps [next](https://github.com/vercel/next.js) from 15.6.0-canary.58 to 16.1.7. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v15.6.0-canary.58...v16.1.7) --- updated-dependencies: - dependency-name: next dependency-version: 16.1.7 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/next-16.1.7
branch
from
b9b47b9 to
2d33e7f
Compare
Author
|
Superseded by #51. |
yonas
pushed a commit
that referenced
this pull request
Apr 21, 2026
…und agno SDK success-path hang Reimplements the approach from the now-closed PR CopilotKit#4093 (which I closed after CopilotKit#4095 merged the agno 2.5.17 upgrade, on the belief that the SDK bump had fixed the underlying SSE termination bug). Follow-up evidence collected 2026-04-19 showed the SDK upgrade only addressed the error path — production /api/smoke with real API keys still hangs because the agno SDK does not reliably emit TEXT_MESSAGE_END / RUN_FINISHED on the success path. Documented in Notion page 3473aa381852815b9765fd28fa53275a, item #5. Change: instead of `await res.text()` (which only resolves when the server closes the stream), read res.body incrementally with getReader() + TextDecoder. Short-circuit as soon as the buffer contains `"type":"TEXT_MESSAGE_CONTENT"` with `"OK"` — the agent has produced the expected output, so we cancel the reader and return a 200 success envelope without awaiting a terminal event that may never arrive. If the stream closes cleanly without confirmation, return a diagnostic 502 with stage="response_incomplete" so regressions surface clearly. Keep the existing 45s AbortSignal timeout as a final safety net. Response envelope shape is preserved for the smoke monitor parser. This is a client-side mitigation, not a fix. The real fix belongs upstream in the agno SDK's AG-UI interface. Keep this PR open until upstream is addressed and verified in production with real keys.
yonas
pushed a commit
that referenced
this pull request
Apr 21, 2026
…und agno SDK success-path hang (CopilotKit#4105) ## Summary Reimplements the SSE incremental reader workaround from the now-closed PR CopilotKit#4093 on a fresh branch off `main`. ## Background PR CopilotKit#4093 was closed under the assumption that PR CopilotKit#4095 (agno SDK upgrade to 2.5.17) had fixed the underlying SSE stream termination bug at the source. Follow-up diagnostics on 2026-04-19 revealed that the SDK upgrade only addressed the **error path**; production `/api/smoke` with real API keys still hangs because the agno SDK does not reliably emit `TEXT_MESSAGE_END` / `RUN_FINISHED` on the **success path**. Documented in Notion page `3473aa38-1852-815b-9765-fd28fa53275a`, item #5. ## Change `showcase/packages/agno/src/app/api/smoke/route.ts` — swap `await res.text()` for an incremental reader: - Read `res.body` via `getReader()` + `TextDecoder` + string buffer accumulator. - On each chunk, check whether the accumulated buffer contains `"type":"TEXT_MESSAGE_CONTENT"` along with `"OK"` in the delta. Once seen, cancel the reader and return a 200 success envelope — do not await a terminal event that the SDK may never send on the success path. - If the stream closes cleanly without ever producing the confirmation payload, return a 502 with `stage:"response_incomplete"` so regressions surface clearly in the smoke monitor. - Keep `AbortSignal.timeout(45000)` as the final safety net. - Response envelope shape preserved for the smoke monitor parser. ## Scope Only the agno `/api/smoke/route.ts` is touched. The other 16 showcase starters use the same `await res.text()` pattern but none have exhibited the hang in production — no speculative fixes. ## Caveat — this is a mitigation, not a fix The real fix belongs upstream in the agno SDK's AG-UI interface. **Do not merge-and-forget.** Keep this PR open until upstream is addressed and the fix is verified in production with real API keys, then revisit whether this client-side workaround can be removed. ## Test plan - [x] Visual inspection of the diff matches the pattern from PR CopilotKit#4093 - [x] Standalone `tsc --noEmit` against `route.ts` with DOM + ES2017 libs — clean (only missing `@types/node` for `process`, expected in dry-run; code compiles cleanly otherwise) - [ ] Production curl sanity check against `https://showcase-agno-production.up.railway.app/api/smoke` once deployed - [ ] Monitor next 12h of `Showcase: Smoke Monitor` runs for agno stability Closes/replaces the approach from CopilotKit#4093.
yonas
pushed a commit
that referenced
this pull request
Apr 22, 2026
…te integration slug; sort-ordered preview selection - Extract findFrameworksWithCell into @/lib/docs-render so the docs catch-all and framework-scoped catch-all share one implementation instead of carrying a near-identical local copy in each (finding #3). - Validate /docs/integrations/<slug> against the registry with notFound() when the slug is unknown. Previously a crafted URL like /docs/integrations/fake-framework silently fell through to an empty nav tree, indistinguishable from a valid integration with no scoped content (finding #4). - Sort integrations by sort_order then slug before picking the animated preview URL. Registry iteration order alone isn't deterministic w.r.t. the visual priority the docs UI shows everywhere else, so the preview now matches (finding #5).
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
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.
Bumps next from 15.6.0-canary.58 to 16.1.7.
Release notes
Sourced from next's releases.
Commits
bdf3e35v16.1.7dc98c04[backport]: fix: patch http-proxy to prevent request smuggling in rewrites (#...9023c0a[backport] Disallow Server Action submissions from privacy-sensitive contexts...36a97b9Allow blocking cross-site dev-only websocket connections from privacy-sensiti...93c3993[backport]: feat(next/image): add lru disk cache and `images.maximumDiskCache...c68d62dBackport documentation fixes for 16.1.x (#90655)5214ac1[backport]: ensure maxPostponedStateSize is always respected (#90060) (#90471)c95e357Backport/docs fixes 16.1.x (#90125)cba6144[backport] Apply server actions transform tonode_modulesin route handlers...3db9063[backport] [Cache Components] Prevent streaming fetch calls from hanging in d...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.