Skip to content

Release 6.10.2025 - #576

Merged
maxtechera merged 2 commits into
productionfrom
staging
Oct 6, 2025
Merged

Release 6.10.2025 #576
maxtechera merged 2 commits into
productionfrom
staging

Conversation

@maxtechera

Copy link
Copy Markdown
Collaborator

No description provided.

@vercel

vercel Bot commented Oct 6, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
answerai-docs Building Building Preview Oct 6, 2025 4:01pm
the-answerai Building Building Preview Oct 6, 2025 4:01pm

@maxtechera
maxtechera merged commit 4d501c4 into production Oct 6, 2025
6 of 9 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

import clsx from 'clsx'
import useDocusaurusContext from '@docusaurus/useDocusaurusContext'
import Layout from '@theme/Layout'
import JsonLd from '@site/src/components/JsonLd'
import ThreeJsScene from '@site/src/components/Annimations/SphereScene'
import UsingAnswerAgentAISubmenu from '@site/src/components/UsingAnswerAgentAISubmenu'

P1 Badge Remove unused UsingAnswerAgentAISubmenu import

The JSX component <UsingAnswerAgentAISubmenu /> was removed from the page, but the import remains. With noUnusedLocals/ESLint enabled (as configured for this repo), this unused import will cause pnpm lint or the TypeScript build to fail for the docs package. Either remove the import or reintroduce the component.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting

Comment on lines +27 to +48
// Delete duplicate chatflows, keeping only the most recently updated one for each group
const deleteResult = await queryRunner.query(`
DELETE FROM "chat_flow"
WHERE id IN (
SELECT cf.id
FROM "chat_flow" cf
INNER JOIN (
SELECT
"userId",
"parentChatflowId",
MAX("updatedDate") as max_updated_date
FROM "chat_flow"
WHERE "parentChatflowId" IS NOT NULL
AND "deletedDate" IS NULL
GROUP BY "userId", "parentChatflowId"
HAVING COUNT(*) > 1
) duplicates
ON cf."userId" = duplicates."userId"
AND cf."parentChatflowId" = duplicates."parentChatflowId"
WHERE cf."deletedDate" IS NULL
AND cf."updatedDate" < duplicates.max_updated_date
)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Ensure duplicate cleanup handles rows with identical updatedDate

The new automatic cleanup deletes duplicates only when updatedDate is strictly less than the group’s MAX(updatedDate). If two or more chatflows in the same (userId, parentChatflowId) group have the exact same updatedDate (for example, cloned records saved in the same transaction), none of them satisfy < max_updated_date, so duplicates remain and the subsequent unique index creation will fail with a constraint violation. Consider deleting all but one record per group using a deterministic tie breaker (e.g., ROW_NUMBER over updatedDate DESC, id DESC) or re-checking for duplicates after the delete before adding the index.

Useful? React with 👍 / 👎.

Comment on lines 82 to 85
/* Push everything down to account for the fixed banner */
:global(body) {
padding-top: 54px !important;
:global(.navbar) {
top: 54px !important;
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep body content offset when fixed webinar banner is shown

Previously the layout applied padding-top: 54px to the body to push all content below the fixed webinar banner. The change now only offsets .navbar, so the main content still starts at the top of the viewport while the banner remains fixed at top: 0, leaving the first ~54 px of content hidden under the banner when it is active. Consider preserving the body offset (or adding equivalent margin to the main wrapper) so the banner doesn’t obscure page content.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant