Conversation
🦋 Changeset detectedLatest commit: b4898fd The changes in this PR will be included in the next version bump. This PR includes changesets to release 10 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
TL;DR — Bumps Next.js from Key changes
Summary ｜ 7 files ｜ 5 commits ｜ base: Next.js version bump
The
PostCSS config renames and
|
![pullfrog[bot]](https://avatars.githubusercontent.com/in/1768019?s=60&v=4){kind=small}
There was a problem hiding this comment.
Clean, mechanical Next.js version bump from 16.1.6 to 16.2.1 across agents-docs and agents-manage-ui. Lockfile changes are purely resolution-string substitutions with one expected new transitive dep (baseline-browser-mapping@2.10.10). The postcss config renames (.js/.mjs → .ts) normalize file extensions with identical content. Changeset correctly scopes to @inkeep/agents-manage-ui (docs is in the ignore list). No issues found.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Review Summary
(1) Total Issues | Risk: Medium
🟠⚠️ Major (1) 🟠⚠️
Inline Comments:
- 🟠 Major:
agents-manage-ui/package.json:15filesarray referencespostcss.config.mjsbut file was renamed topostcss.config.ts
💭 Consider (1) 💭
💭 1) create-agents-template/ Template projects still use Next.js 16.1.6
Issue: The create-agents-template/apps/mcp/package.json and create-agents-template/apps/manage-ui/package.json still reference next: 16.1.6.
Why: New projects scaffolded from the template will start with an older Next.js version. This may be intentional if templates follow a separate release cadence, but worth considering for consistency.
Fix: Optionally update template projects to ^16.2.1 in a follow-up PR if templates should stay in sync with the main packages.
🚫 REQUEST CHANGES
Summary: The Next.js upgrade and PostCSS config TypeScript migration look good. The one blocking issue is that agents-manage-ui/package.json needs its files array updated to reference postcss.config.ts instead of the old postcss.config.mjs filename. This is a 1-click fix in the inline comment above.
Discarded (3)
| Location | Issue | Reason Discarded |
|---|---|---|
postcss.config.ts |
PostCSS config should use .js extension not .ts | Invalid — project uses TypeScript configs consistently (next.config.ts exists), and Next.js 16+ supports .ts config files |
.changeset/wet-bees-drive.md |
Should include agents-docs in changeset | Invalid — agents-docs is private and in the ignored packages list per AGENTS.md |
coverage.config.ts:156 |
References postcss.config.js glob | Invalid — this is a wildcard exclusion pattern (**/postcss.config.js) for coverage, not a direct file reference |
Reviewers (2)
| Reviewer | Returned | Main Findings | Consider | While You're Here | Inline Comments | Pending Recs | Discarded |
|---|---|---|---|---|---|---|---|
pr-review-devops |
1 | 0 | 0 | 0 | 1 | 0 | 0 |
pr-review-standards |
4 | 0 | 1 | 0 | 0 | 0 | 3 |
| Total | 5 | 0 | 1 | 0 | 1 | 0 | 3 |
There was a problem hiding this comment.
PR Review Summary
(0) Total Issues | Risk: Low
This is a re-review following PR synchronization. The prior blocking issue has been resolved:
| Prior Issue | Status |
|---|---|
files array referenced postcss.config.mjs after rename to .ts |
✅ Fixed via 4a5e37d |
✅ What's Changed (Clean)
- Next.js
^16.1.6→^16.2.1inagents-docsandagents-manage-ui— patch release bump - PostCSS config TypeScript migration —
.js/.mjs→.ts(aligns with Next.js 16's native TS config support) tailwind.config.mjsremoved from files array — correct for Tailwind CSS v4 which doesn't require a separate config file- Changeset correctly scopes to
@inkeep/agents-manage-ui(docs is private/ignored) - Lockfile shows expected transitive dependency updates
💭 Consider (from prior review)
The create-agents-template/ still uses Next.js 16.1.6 — this can be addressed in a follow-up if templates should stay in sync with main packages.
✅ APPROVE
Summary: Clean, mechanical Next.js version bump with proper PostCSS config migration to TypeScript. Prior blocking issue resolved. Ship it! 🚀
Reviewers (0)
| Reviewer | Returned | Main Findings | Consider | While You're Here | Inline Comments | Pending Recs | Discarded |
|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — |
Note: Re-review — no sub-agents dispatched as prior issues resolved and no new changes requiring deep review.
There was a problem hiding this comment.
PR Review Summary
(0) Total Issues | Risk: Low
This is a delta re-review scoped to changes since the last automated review (4a5e37d).
Delta Changes Reviewed
| File | Change | Assessment |
|---|---|---|
coverage.config.ts:154-155 |
Updated glob patterns **/next.config.js → **/next.config.ts and **/postcss.config.js → **/postcss.config.ts |
✅ Correct — aligns coverage exclusions with actual file extensions after config migration |
This is a mechanical follow-up to the PostCSS config TypeScript migration that was already reviewed and approved.
✅ APPROVE
Summary: Clean delta — coverage exclusion patterns correctly updated to match the .ts config file extensions. Ready to merge! 🚀
Reviewers (0)
| Reviewer | Returned | Main Findings | Consider | While You're Here | Inline Comments | Pending Recs | Discarded |
|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — |
Note: Delta re-review — trivial 2-line change to glob patterns required no sub-agent dispatch.
|
🔎💬 Inkeep AI search and chat service is syncing content for source 'Inkeep Agent Framework Docs' |
Ito Test Report ❌17 test cases ran. 1 failed, 16 passed. Across 17 executed test cases, 16 passed and 1 failed, showing strong stability across Manage and Docs coverage including login/auth redirects, returnUrl sanitization and invitation precedence, open-redirect and rapid-submit abuse handling, tenant-path isolation, docs slug/404 recovery, styling compilation, and docs API/OpenGraph/text utility routes. ❌ Failed (1)
🟡 Docs home route renders with structured layout
Relevant code:
if (typeof window !== 'undefined') {
posthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY || '', {
api_host: process.env.NEXT_PUBLIC_POSTHOG_HOST || 'https://us.i.posthog.com',
capture_pageview: false,
person_profiles: 'always',
disable_surveys: true,
disable_external_dependency_loading: true,
loaded: (posthog) => {
import '@/instrumentation-client';
export function PostHogProvider({ children }: { children: ReactNode }) {
return <PHProvider client={posthog}>{children}</PHProvider>;
}
if (process.env.NODE_ENV === 'test' || !process.env.NEXT_PUBLIC_POSTHOG_KEY) {
console.log(`[PostHog Server] Skipping event capture: ${event} (${distinctId})`);
return;
}
try {
const posthog = new PostHog(process.env.NEXT_PUBLIC_POSTHOG_KEY, {
host: process.env.NEXT_PUBLIC_POSTHOG_HOST || 'https://us.i.posthog.com',✅ Passed (16)
Commit: Tell us how we did: Give Ito Feedback |
1 participant
No description provided.