chore: merge develop to main for Cloudflare production deploy - #184
Conversation
…ons for 'follow us' and 'youtube'
… all relevant files
…onCodePanel with pseudocode tab
…le-specific strings
… and line numbering in PythonCodePanel
…sorting order toggle functionality
…-tab Multilingual pseudocode tab, sort-order control, and theme-safe syntax highlighting
…I/CD processes and security settings
…ance settings panel for tree node count, and update translations
… update translations
…lgorithm list generation
…and related metadata (#165)
… tests, translations, and metadata (#166)
…e metadata for consistency
Feat: add Tree Traversals Category (#160)
…e into visualization components
…scenarios - Added support for graph algorithms including topological sort with scenario options. - Introduced GraphAlgorithmCategoryVisualizer and GraphAlgorithmMatrixVisualizer components for rendering. - Implemented GraphScenarioDropdown for selecting graph scenarios. - Enhanced visual representation with GraphAlgorithmVideoScene and GraphAlgorithmMatrixScene. - Updated registry and configuration files to accommodate new graph algorithms and scenarios. - Added tests for new components and functionalities to ensure reliability.
- Remove lucide-react dependency entirely - Install @phosphor-icons/react v2.1.10 - Map all 33 unique Lucide icons to Phosphor equivalents - Replace text labels with inline SVG brand icons in footer social links - Add missing i18n keys for Facebook, Instagram, TikTok in all 3 locales - Update 5 test file mocks from lucide-react to @phosphor-icons/react - 1519 tests passing, lint and format clean
…impleIcons
- Add weight=bold to all 58 Phosphor icon render sites across 21 files
- Replace amateur inline SVG brand icons with SimpleIcons (SiYoutube, SiInstagram, SiTiktok) from react-icons
- Remove hand-crafted TikTok music note SVG that looked unprofessional
- Remove Facebook icon from footer entirely
- Fix strokeWidth={1.75} prop on GitHubRepoBadge icon (Lucide prop, now weight=bold)
- All 1519 tests passing, lint and format clean
refactor: replace lucide-react with @phosphor-icons/react + add footer social links
…st Inter, click-to-load YouTube embeds with local thumbnails, and publish Privacy Policy and Terms of Use for public launch.
feat: privacy launch, legal pages, self-hosted fonts, YouTube click-to-load
chore(security): Phase 0 hardening — headers, Semgrep CI, deps
chore: migrate hosting from Netlify to Cloudflare Workers (static assets)
✅ Deploy Preview for dev-bayanflow ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
Contribution workflow
main: This PR targetsmainfromdevelop.Description
This is not a v0.5.0 release PR. It merges
developintomainso the Cloudflare Workers production deploy can run onmain— the next step in the Netlify → Cloudflare migration.developalready has the migration merged (#183) and deploys to the staging worker. Merging tomaintriggers deploy to the production worker (bayan-flow.workers.dev). Custom domains (bayanflow.com,dev.bayanflow.com) stay on Netlify until DNS cutover.Everything else on
develop(tree/graph categories, legal pages, sound work, etc.) ships with this merge because that is how the branches diverged — not because we are cutting a release tag.Type of Change
Related Issues
Fixes #
Changes Made
Why this PR exists (migration)
wrangler.jsonc— static SPA ondist/,staging/productionenvironmentsdeploy-cloudflare.yml— deploys to production worker after CI passes onmainpreview-cloudflare.yml— PR previews on staging workerpublic/_headers— security headers (CSP, HSTS, etc.) ported from Netlifynetlify.tomlkept for rollback (~2 weeks)public/_redirects(conflicts with Cloudflare SPA routing)Also included (already on
develop, not release-scoped)developis ~76 commits ahead ofmain. Notable work that rides along:No version bump or GitHub Release is planned as part of this merge.
Algorithm Details (if applicable)
N/A for migration intent. Registry completeness unchanged on
develop.Testing
developCI green (including Cloudflare staging deploy)mainhttps://bayan-flow.workers.devbefore DNS cutover/app, footer Product Hunt badge, one locale switchTest Results
Rely on latest green CI on
develop. Post-merge, verify production worker URL loads.Screenshots/GIFs
N/A
Code Quality
developbranch CI passingPerformance Impact
Accessibility
Breaking Changes
mainbayanflow.comDNS unchanged until manual cutoverCF_API_TOKEN,CF_ACCOUNT_ID(already configured)Checklist
develop(chore: migrate hosting from Netlify to Cloudflare Workers (static assets) #183)develophttps://bayan-flow.workers.devAdditional Notes
After merge (migration sequence)
main→https://bayan-flow.workers.devwrangler.jsonc, redeploydev.bayanflow.comandbayanflow.comin Cloudflare dashboardnetlify.tomlWhat this PR is not
Rollback
Point DNS back to Netlify if needed. Netlify projects and
netlify.tomlremain available.Reviewer Guidelines:
main