v0.7.33: workflow/custom block fix, community pages improvements, chat animation#5658
Merged
Conversation
…sistency (#5651) Aligns with the /integrations/[slug] convention (plural category, singular item). Adds a 301 redirect (both the bare hub page and every competitor detail page) so previously indexed URLs keep working, and updates every internal reference: footer nav, sitemap generation, and all import specifiers/canonical URLs/breadcrumb JSON-LD within the route itself.
…p, docs, emails, and readme (#5653)
… nuqs (#5648) * improvement(url-state): migrate list search/sort/filter view-state to nuqs * fix(url-state): clear mcpServerId selection when the selected workflow MCP server is deleted * fix(url-state): resolve-gated MCP server detail view + replace-on-close for detail back navigation * fix(url-state): explicit Suspense boundary for account settings sections
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryMedium Risk Overview Landing SEO: competitor pages move from Workspace UX: list search, sort, and filters for Files, Knowledge, Logs, Skills, and workspace settings panels are URL-backed via nuqs (debounced search, replace history for filters). Knowledge and account settings get Suspense boundaries for Execution: nested workflow runs pass UI: chat shimmer animation direction is reversed for left-to-right sweep. Reviewed by Cursor Bugbot for commit 8b9f593. Configure here. |
Contributor
Greptile SummaryThis PR updates landing/community links, URL state, and workflow billing attribution. The main changes are:
Confidence Score: 4/5The changed flow looks mergeable after fixing the settings search state leak.
apps/sim/app/workspace/[workspaceId]/settings/components/search-params.ts Important Files Changed
Reviews (1): Last reviewed commit: "fix(workflow, custom): billing attributi..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
…es to it (#5655) * fix(landing): align author-page UI with the site shell and link bylines to it Rebuilds ContentAuthorPage/ContentAuthorLoading to match the standard page-shell pattern used by ContentIndexPage/ContentPostPage (max-w-[1460px] header, BackLink, framed post-list rows with hover states) instead of the previous bare max-w-[900px] container with a 2-column image grid. Adds a styled not-found fallback matching the comparisons/integrations pattern. The byline author Link in ContentPostPage now points at the internal author page (/{basePath}/authors/{id}) instead of the author's external X/GitHub profile, giving the author page a real navigation entry point for the first time - previously it was only reachable via the sitemap. Also fixes both author-page route files to match on any of a post's authors (post.authors.some(a => a.id === id)) instead of only the primary author (post.author.id === id), so posts with co-authors show up on every listed author's page, consistent with the sitemap's own author enumeration. * fix(landing): address review findings on author-page UI rebuild - Not-found fallback no longer renders a nested <main id='main-content'> - blog/layout.tsx and library/layout.tsx already provide that landmark, so the fallback now uses <section> like the rest of the component. - Byline author link now encodeURIComponent()s the author id before using it as a route segment. - Loading skeleton's post-list wrapper now matches the real page's mx-auto max-w-[1460px] shell (was mx-20/max-lg:mx-8, which stretches past the header on wide viewports). * fix(landing): make author Person.image an absolute URL in JSON-LD Same class of bug as the earlier article-image fix: author.avatarUrl is a site-relative path, so Person.image was emitting an invalid relative URL for crawlers. Prefixes with SITE_URL, matching buildArticleJsonLd's existing pattern. * fix(landing): align author not-found fallback width with the site convention max-w-[1446px]/px-12 was copied from comparisons/not-found.tsx, which turns out to be the outlier - models/not-found.tsx and integrations/not-found.tsx both use max-w-[1460px]/px-20, matching the rest of the site's shell and this component's own success-state header. * fix(landing): encode author id consistently in every author URL builder The byline link encoded the author id, but buildAuthorMetadata's canonical URL, buildAuthorGraphJsonLd's Person.url/BreadcrumbList item, and sitemap.ts's buildAuthorPages URL still interpolated the raw id - a mismatch could point sitemap/canonical/structured-data URLs at a different route than the actual page. All four now encodeURIComponent() consistently.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
…nd log selection deep links (#5652) * improvement(url-state): shared sort/search url-state helpers + task and log selection deep links * improvement(url-state): audit fixes — cancel pending deep-link on click, void settings search setter * fix(url-state): review fixes — trim-on-read filters, replace-on-close for task modal, unified executionId write path * improvement(url-state): final audit polish — consistent handler deps, document schedules-refetch invariant * improvement(url-state): compose useSettingsSearch on the shared setter, trim chunk query read * chore(skills): sync url-state skill edits through the canonical SKILL.md * fix(url-state): reset chunk page in the same write as a search change
* improvement(admin): filter out banned users * fix timestamp glitch
…smooth agent-group narration (#5660) * feat(chat): natural-language tool titles, past-tense completion, and smooth agent-group narration * improvement(chat): drop per-row status icons on subagent tool calls * fix(chat): restrict narration seam space to sentence boundaries * improvement(chat): promote inline comments to TSDoc, support bold-italic in narration markdown * fix(chat): gate narration seam repair on channel transitions, render nested inline markdown recursively * improvement(chat): flip Gathering thoughts to past tense on completion * fix(chat): classify inline-markdown tokens by split parity, require non-space emphasis boundaries
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
4 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.
(improvement(url-state): shared sort/search url-state helpers + task and log selection deep links #5652)