Skip to content

chore(release): staging to production - 2026.01.26 - #895

Merged
maxtechera merged 10 commits into
productionfrom
staging
Jan 26, 2026
Merged

chore(release): staging to production - 2026.01.26#895
maxtechera merged 10 commits into
productionfrom
staging

Conversation

@github-actions

@github-actions github-actions Bot commented Jan 23, 2026

Copy link
Copy Markdown

🚀 Release: Staging to Production

Release Date: 2026-01-26

Changes in this release

  • fix(SUPPORT-18): auto-detect JWT tokens in browser extension requests (a9e895e)
  • fix(AGENT-586): remove unnecessary zIndex from AppDrawer (4ff5e4e)
  • fix(AGENT-586): fix AppDrawer overlapping page content (455dc39)
  • fix: simplify no-console rule to always be warning (8e273f3)
  • fix: exclude scripts directory from eslint (3809952)
  • fix: resolve remaining lint errors for CI (52fbf2f)
  • fix: resolve all eslint lint errors (4e28dd6)

This PR is automatically created/updated when commits are pushed to staging.
Merging this PR will trigger the release workflow to create a new GitHub release.

claude and others added 5 commits January 23, 2026 17:17
- Fix @typescript-eslint/no-unused-vars rule not found in useSidekickData.ts
- Add missing setError PropTypes in AssistantDialog.jsx
- Fix React hooks called conditionally in DatasetItems.jsx and users/index.jsx
  - Move early return statements after all hook definitions
- Add eslint-disable comments for legitimate control regex patterns (\x1b for ANSI codes)
- Remove unnecessary escape characters in regex patterns
- Add eslint-disable for while(true) infinite loop pattern in netlify.js
- Apply auto-fixes from lint-fix command (76 files)

Result: 0 errors, 905 warnings (warnings are expected no-console in scripts)

https://claude.ai/code/session_011J33mUeS8fnCF3JiWxxFwL
- Change console.log to console.info in AAIDomains.ts, AAIUrls.ts, AAIRecordManager.ts
- Add eslint-disable no-console for pgvector CLI scripts
- Prefix unused variables with underscore:
  - DocStoreLoader.ts: userId, organizationId
  - Youtube.ts, AAIEmbedding.ts, AAIExaSearch.ts: options parameter
  - CreateCalendarEvent.ts: response
  - AAIPostgres.ts: namespace (3 occurrences)
  - utils.ts: nodeData parameters (8 occurrences)
  - modelLoader.ts: MASTER_MODEL_LIST

Result: 0 errors, 769 warnings

https://claude.ai/code/session_011J33mUeS8fnCF3JiWxxFwL
Add scripts/** to .eslintignore to exclude all CLI scripts from linting.
These scripts are meant for console output and should not trigger no-console warnings.

https://claude.ai/code/session_011J33mUeS8fnCF3JiWxxFwL
Remove redundant ternary condition that was setting 'warn' in both cases.

https://claude.ai/code/session_011J33mUeS8fnCF3JiWxxFwL
…baVoI

fix: resolve all eslint lint errors
@vercel

vercel Bot commented Jan 23, 2026

Copy link
Copy Markdown

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

Project Deployment Review Updated (UTC)
answerai-docs Building Building Preview Jan 23, 2026 8:37pm
the-answerai Building Building Preview Jan 23, 2026 8:37pm

Request Review

diecoscai and others added 3 commits January 26, 2026 16:48
Override MUI's default position: fixed on drawer paper with
position: relative so the drawer participates in normal document
flow within the flex container instead of floating over content.

Also add height: 100% to both the root Drawer and drawer paper
to ensure proper sizing in the flex layout.

This is the proper fix in packages-answers/ui instead of modifying
Flowise core files.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
With position: relative, the drawer is now in normal document flow
and doesn't need explicit z-index management.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…yout-fix

fix(AGENT-586): Fix AppDrawer overlapping page content
@github-actions github-actions Bot changed the title chore(release): staging to production - 2026.01.23 chore(release): staging to production - 2026.01.26 Jan 26, 2026
@claude

claude Bot commented Jan 26, 2026

Copy link
Copy Markdown

PR Review: Staging to Production Release (2026-01-26)

✅ Overall Recommendation: APPROVE

This release contains low-risk quality improvements and bug fixes. The changes are production-ready.


📊 Summary

Changes: 409 additions, 387 deletions across 89 files
Focus Areas: ESLint cleanup, UI bug fixes, code quality improvements

Key Changes:

  1. ESLint configuration improvements - Simplified rules, excluded scripts directory
  2. AppDrawer UI fix (AGENT-586) - Resolved overlapping content issue
  3. Code cleanup - Removed unused imports, fixed console.log violations
  4. Minor refactoring - Simplified authentication and repository code

🔍 Detailed Analysis

✅ Strengths

1. ESLint Configuration (Low Risk)

  • Simplified no-console rule to always warn (removed CI check)
  • Excluded scripts/** from linting (appropriate for build scripts)
  • Good code hygiene improvements across the codebase

2. UI Bug Fix - AppDrawer (AGENT-586)

  • Files: packages-answers/ui/src/AppDrawer.tsx, packages-answers/ui/src/AppLayout/AppLayout.Client.tsx
  • Removed problematic zIndex: 9999 that was causing content overlap
  • Simplified drawer implementation - cleaner approach ✅

3. Code Quality Improvements

  • Removed unused imports across multiple files (billing, auth, components)
  • Fixed React hooks ordering in useSidekickData.ts (was a legitimate bug) ✅
  • Cleaned up unnecessary console.log statements
  • Removed dead code and unused variables

4. Database Migration Cleanup

  • Simplified queries in AAIBackfillWorkspaceId migration
  • Reduced unnecessary type casting in migrations
  • No schema changes, only query optimizations ✅

⚠️ Minor Concerns (Non-blocking)

1. Broad ESLint Exclusion

-.eslintignore: scripts/bws-secure/**
+.eslintignore: scripts/**

Impact: Low - Scripts are typically not linted, but this is broader than necessary
Recommendation: Consider reverting to scripts/bws-secure/** if other scripts should be linted

2. Removed Error Context
Several files removed error handling context:

  • packages/server/src/aai/auth/enrichUserData.ts - Simplified error handling
  • packages/server/src/middlewares/authentication/findOrCreateUser.ts - Similar simplification

Impact: Minimal - Error messages still present, just less verbose
Note: No security impact, just less debugging context

3. Console.log Cleanup
Multiple console.log statements were removed. Verify these weren't needed for production debugging.


🔒 Security Analysis

✅ No Security Issues Found

Multi-tenancy patterns: ✅ Intact
Authentication middleware: ✅ No changes to security logic
Authorization checks: ✅ All organizationId filtering preserved
Database queries: ✅ No new security vulnerabilities introduced

Note: Changes to authentication files are purely cleanup (removing unused imports and variables), not logic changes.


🧪 Testing Recommendations

Since this is a production release:

  1. Smoke test the AppDrawer fix

    • Verify drawer doesn't overlap content
    • Test on different screen sizes
    • Check z-index interactions with other UI elements
  2. Verify authentication flow

    • Login/logout still works
    • User creation and workspace initialization
    • API key authentication
  3. Check billing components

    • Heavy formatting changes in BillingComponents.tsx
    • Ensure no visual regressions
  4. Monitor for console errors

    • Many console.log statements removed
    • Watch for any needed logging that was accidentally removed

📝 Code Quality Notes

Positive patterns observed:

  • ✅ Consistent use of early returns
  • ✅ Proper TypeScript types maintained
  • ✅ No bypassing of authentication checks
  • ✅ Following repository conventions

Formatting changes:

  • Extensive Prettier formatting in BillingComponents.tsx (77 lines changed)
  • Improved code readability with proper line breaks and indentation

🎯 Final Verdict

APPROVE - This release is production-ready.

Risk Level: Low
Breaking Changes: None
Security Impact: None

Pre-merge Checklist:

  • Verify CI/CD passes all checks
  • Smoke test AppDrawer fix in staging
  • Confirm authentication flows work
  • Monitor error logs after deployment

Great work on the code quality improvements! The ESLint cleanup and bug fixes will make the codebase more maintainable going forward.

🤖 Review conducted by Claude Code PR Reviewer

maxtechera and others added 2 commits January 26, 2026 18:24
Browser extension sends JWT without x-request-from: aai header, causing
requests to fall through to API key validation and fail with 401.

Changes:
- Add looksLikeJWT() helper to detect JWT tokens (3 dot-separated segments)
- Extract handleApiKeyAuth() to avoid code duplication
- Try JWT auth if header present OR token looks like JWT
- Fall back to API key auth if JWT verification fails

This maintains backwards compatibility:
- Existing header-based routing unchanged
- API keys (no dots) won't be misidentified as JWTs
- Fallback adds resilience without breaking existing integrations

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…extension-jwt-auth

fix(SUPPORT-18): Auto-detect JWT tokens in browser extension requests
@maxtechera
maxtechera merged commit c762603 into production Jan 26, 2026
9 of 13 checks passed
@maxtechera
maxtechera temporarily deployed to staging - aai-unified2-flowise-moonstruck January 26, 2026 21:28 — with Render Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants