fix: update src link to analytics

[andostronaut]

This is an automated pull request for branch develop

Summary by CodeRabbit

• Chores
  • Updated the source URL for the analytics script in the RootLayout component.

[coderabbitai]

Walkthrough

The changes in this pull request involve an update to the RootLayout component located in the app/layout.tsx file. The primary modification is the alteration of the script source URL from https://umami.kinotio.io/script.js to https://analytics.kinotio.io/script.js. This change does not impact the overall structure or functionality of the component, which continues to render its children and includes an additional script for a status widget, with no changes to locale handling or class name application.

Changes

File	Change Summary
app/layout.tsx	Updated script source URL from umami.kinotio.io to analytics.kinotio.io.

Possibly related PRs

• feat: improve seo #19: Modifications to the metadata object in app/layout.tsx, unrelated to the script source URL change.
• feat: add products on navbar and use sytem theme #39: Changes to the ThemeProvider configuration in RootLayout, not connected to the script source URL update.
• fix: search params on sub layout and use arrow function #46: Transition to arrow function syntax in RootLayout, a structural change not related to the script source URL modification.

🐰 In the meadow, hopping free,
A script was changed, oh what glee!
From umami's charm to analytics' might,
Our layout shines, all feels just right.
With every bounce, we celebrate,
A brighter path we now create! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9afe1da and c6a6691.

📒 Files selected for processing (1)

• app/layout.tsx (1 hunks)

🔇 Additional comments (1)

app/layout.tsx (1)

23-23: Verify analytics endpoint configuration.

The change from umami.kinotio.io to analytics.kinotio.io appears correct, but we should ensure:

1. The new analytics endpoint is properly configured and accessible
2. No analytics data loss during the transition

Let's verify the endpoint configuration:

Consider implementing these best practices for analytics transitions:

1. Run both old and new endpoints in parallel temporarily to ensure data consistency
2. Monitor analytics events in both systems during the transition period
3. Document the DNS change in your infrastructure documentation

✅ Verification successful

Analytics endpoint is properly configured and accessible

The new analytics endpoint at analytics.kinotio.io is:

• Returning HTTP 200 status code
• Serving JavaScript content with correct MIME type
• Protected by Cloudflare CDN
• Properly configured with security headers including CSP
• Has appropriate caching headers for optimal performance

The endpoint is fully operational and correctly configured for analytics tracking.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the new analytics endpoint is accessible and returns a valid script

# Test: Verify the HTTP response and content type
curl -I https://analytics.kinotio.io/script.js

Length of output: 1505

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.