Skip to content

Open-source status page, incident response and uptime monitoring

add more docs (#1709)

Thibault Le Ouayedcb4028129a
diff --git a/apps/docs/package.json b/apps/docs/package.json
index 5edfa0bb5..6d28e0597 100644
--- a/apps/docs/package.json
+++ b/apps/docs/package.json
@@ -10,21 +10,21 @@
"astro": "astro"
},
"dependencies": {
- "@astrojs/check": "0.9.4",
- "@astrojs/react": "4.3.1",
- "@astrojs/sitemap": "3.5.1",
- "@astrojs/starlight": "0.35.2",
- "@astrojs/starlight-tailwind": "4.0.1",
+ "@astrojs/check": "0.9.6",
+ "@astrojs/react": "4.4.2",
+ "@astrojs/sitemap": "3.6.0",
+ "@astrojs/starlight": "0.37.1",
+ "@astrojs/starlight-tailwind": "4.0.2",
"@fontsource-variable/inter": "5.2.8",
"@openpanel/astro": "1.0.1",
"@tailwindcss/vite": "4.1.8",
- "astro": "5.13.7",
+ "astro": "5.16.6",
"sharp": "0.33.5",
- "starlight-image-zoom": "0.13.0",
- "starlight-links-validator": "0.17.2",
- "starlight-llms-txt": "0.5.1",
- "starlight-showcases": "0.3.0",
- "starlight-sidebar-topics": "0.6.0",
+ "starlight-image-zoom": "0.13.2",
+ "starlight-links-validator": "0.19.2",
+ "starlight-llms-txt": "0.7.0",
+ "starlight-showcases": "0.3.1",
+ "starlight-sidebar-topics": "0.6.2",
"tailwindcss": "4.1.11",
"unplugin-icons": "22.1.0"
},
diff --git a/apps/docs/src/content/docs/concept/best-practices-status-page.mdx b/apps/docs/src/content/docs/concept/best-practices-status-page.mdx
index 341f7a380..356254ad9 100644
--- a/apps/docs/src/content/docs/concept/best-practices-status-page.mdx
+++ b/apps/docs/src/content/docs/concept/best-practices-status-page.mdx
@@ -1,6 +1,6 @@
---
-title: Best Practices for Status Pages
-description: "How to communicate effectively during incidents and build user trust through transparency"
+title: Building Trust with Status Pages
+description: "Understanding how to communicate effectively during incidents and build user trust through transparency."
---
@@ -23,111 +23,106 @@ description: "How to communicate effectively during incidents and build user tru
+------------------------------------------------+
```
-## Why status pages matter
+## The purpose of a status page
-Status pages are essential tools for communicating service health and incidents to users. They build trust by providing transparency and should be a core component of any software company's communication strategy.
+A status page is more than just a dashboard of green lights. It's a critical tool for communication and a cornerstone of building trust with your users. Its primary purpose is to provide a single, authoritative source of truth about your service's health and any ongoing incidents.
-When done right, status pages:
-- **Reduce support burden**: Users self-serve incident information
-- **Build trust**: Transparency demonstrates accountability
-- **Improve communication**: Centralized, consistent incident updates
-- **Demonstrate professionalism**: Shows you take reliability seriously
+When done right, a status page:
+- **Reduces support burden**: Users can self-serve information about outages instead of contacting your team.
+- **Builds trust**: Proactive transparency, even when things go wrong, demonstrates accountability.
+- **Improves communication**: It provides a central and consistent channel for incident updates.
+- **Demonstrates professionalism**: It shows that you take reliability and user experience seriously.
-Following a set of best practices ensures your status page is effective and helpful.
+This article explores the principles that make a status page an effective tool for building trust.
+## Principles of Effective Status Pages
+### Maintain Transparency and Honesty
+A status page's effectiveness hinges on being a reliable source of truth. Be upfront about issues, even minor ones. Hiding problems erodes user trust and can lead to frustration and a higher support load.
-## Best Practices for a Status Page
+- **Communicate Clearly:** Use simple, non-technical language. Your users shouldn't need a technical dictionary to understand the impact of an issue.
-### Maintain Transparency and Honesty
-
-A status page's primary goal is to be a single source of truth. Be upfront about issues, even minor ones. Hiding problems erodes user trust and can lead to more support requests.
-
-- **Communicate Clearly:** Use simple, non-technical language. Users shouldn't need a dictionary to understand what's happening.
-
-- **Be Timely:** Update the page as soon as an incident is confirmed and provide regular updates throughout the resolution process.
+- **Be Timely:** Update the page as soon as an incident is confirmed. Provide regular, predictable updates throughout the resolution process, even if the only update is "we're still working on it."
### Automate Where Possible
-Manual updates during an outage are prone to error and can be slow. Automating your status page can provide more accurate and timely information.
+Manual updates during a high-stress outage are prone to error and can be slow. Automation ensures that your status page reflects reality quickly and accurately.
-- **Integrate Monitoring Tools:** Connect your internal monitoring and alerting systems to your status page. When a metric crosses a threshold (e.g., high error rate), the status page can automatically be updated.
+- **Integrate Monitoring Tools:** Your status page should be directly connected to your internal monitoring and alerting systems. When a metric crosses a threshold (e.g., a high error rate), the status page can be updated automatically to reflect a degraded state.
-- **Use an API:** we provide APIs that allow you to programmatically update component statuses and post new incidents.
+- **Use an API:** We provide APIs that allow you to programmatically update component statuses and post new incidents, integrating your status page into your incident response workflows.
-### Provide Detailed Incident Communication
+### Provide Context-Rich Incident Communication
-When an incident occurs, provide a detailed and structured narrative.
+When an incident occurs, a structured narrative helps users understand the situation.
-- **Start with the "What":** State the problem clearly and concisely.
+- **Start with the Impact:** Clearly and concisely state what the problem is from the user's perspective. For example, "Users are currently unable to log in."
-- **Follow with the "Why":** Briefly explain the root cause, if known.
+- **Explain the Cause (When Known):** Briefly explain the root cause if you've identified it. Transparency here is key.
-- **Conclude with the "How" and "When":** Explain the steps being taken to resolve the issue and provide an estimated time to resolution.
+- **Outline Next Steps and ETA:** Explain what is being done to resolve the issue and provide an estimated time to resolution if possible. It's better to give a conservative estimate or no estimate than to give one you can't meet.
-**Example Incident Update:**
+A typical incident communication lifecycle looks like this:
- **Investigating:** "We're currently investigating an issue affecting user logins."
- **Identified:** "We've identified the root cause as a database connection issue and are working on a fix."
-- **Monitoring:** "A fix has been deployed, and we're monitoring the system's performance."
+- **Monitoring:** "A fix has been deployed, and we're monitoring the system to ensure stability."
-- **Resolved:** "The issue has been resolved, and all services are now operational."
+- **Resolved:** "The issue has been resolved. We will publish a post-mortem within 48 hours."
-### Make it easily accessible
+### Ensure Easy Accessibility
-Your status page should be easy to find.
+Your status page is useless if no one can find it.
-- **Prominent Link:** Place a link to your status page in your application's footer, on your website, and in your support documentation.
+- **Prominent Link:** Link to your status page from your application's footer, your main website, and your support documentation.
-- **Custom Domain:** Use a simple, memorable URL like status.yourcompany.com.
+- **Custom Domain:** Use a simple, memorable URL like `status.yourcompany.com`.
-## Advanced considerations
+## Advanced Considerations for Deeper Trust
-### Scheduled maintenance
+### Scheduled Maintenance
-Communicate planned downtime in advance:
-- Announce maintenance at least 72 hours ahead
-- Show maintenance windows on the status page
-- Send reminders 24 hours before maintenance
+Communicating planned downtime is just as important as communicating unexpected incidents.
+- Announce maintenance well in advance (e.g., at least 72 hours).
+- Display upcoming maintenance windows clearly on the status page.
+- Send reminders to subscribers before maintenance begins.
-### Historical data
+### Historical Data and Post-Mortems
-Show your track record:
-- Display uptime percentages (30/60/90 days)
-- Link to past incidents and post-mortems
-- Be honest about past issues-it builds trust
+Demonstrate your commitment to reliability by being open about your track record.
+- Display historical uptime percentages (e.g., over the last 30/60/90 days).
+- Link to past incidents and their post-mortems. Being honest about past failures and what you've learned from them is a powerful trust-builder.
-### Subscriber notifications
+### Subscriber Notifications
-Let users opt in to updates:
-- Email notifications for incidents
-- SMS for critical alerts (if available)
-- RSS/Atom feeds for automated monitoring
+Allow users to opt-in to the level of communication they want.
+- Email notifications for new incidents and resolutions.
+- SMS for critical alerts (if applicable).
+- RSS/Atom feeds for users who want to integrate your status into their own monitoring.
-## Common mistakes to avoid
+## Common Pitfalls to Avoid
-1. **Over-promising uptime**: Don't claim 100% uptime if you haven't achieved it
-2. **Hiding incidents**: Transparency beats saving face
-3. **Technical jargon**: Write for non-technical audiences
-4. **Infrequent updates**: During incidents, update every 30-60 minutes
-5. **Separate status page hosting**: Your status page should work even when your service is down
+1. **Claiming unrealistic uptime**: Don't claim 100% uptime unless you can back it up. Honesty is better than perfection.
+2. **Hiding or downplaying incidents**: Users will find out anyway. It's better they hear it from you.
+3. **Using technical jargon**: Write for a broad audience, not just other engineers.
+4. **Leaving users in the dark**: During an incident, regular updates are crucial, even if there's no new information. A simple "still investigating" is better than silence.
+5. **Hosting your status page on the same infrastructure**: Your status page must be available even when your main service is down.
## Implementing with openstatus
-openstatus makes following these best practices easy:
+openstatus is designed to make implementing these principles straightforward:
-- **[Create a status page](/tutorial/how-to-create-status-page)** - Quick setup
-- **[Configure your page](/tutorial/how-to-configure-status-page)** - Customize appearance
-- **[Set up notifications](/monitoring/customization/notification)** - Alert your team
-- **[Understand uptime calculations](/concept/uptime-calculation-and-values)** - Transparent metrics
+- **[Create a status page](/tutorial/how-to-create-status-page)** - Get set up in minutes.
+- **[Configure your page](/tutorial/how-to-configure-status-page)** - Customize its appearance to match your brand.
+- **[Understand uptime calculations](/concept/uptime-calculation-and-values)** - Be transparent about how you measure uptime.
## Next steps
-- **[Create your status page](/tutorial/how-to-create-status-page)** - Put these practices into action
-- **[Understanding uptime monitoring](/concept/uptime-monitoring)** - Monitor what you communicate
-- **[Status page reference](/reference/status-page)** - Technical configuration options
+
+- **[Understanding uptime monitoring](/concept/uptime-monitoring)** - Learn more about monitoring what you communicate.
+- **[Status page reference](/reference/status-page)** - Dive into technical configuration options.
diff --git a/apps/docs/src/content/docs/concept/getting-started.mdx b/apps/docs/src/content/docs/concept/getting-started.mdx
index 3ce8834c2..4d2191f82 100644
--- a/apps/docs/src/content/docs/concept/getting-started.mdx
+++ b/apps/docs/src/content/docs/concept/getting-started.mdx
@@ -1,35 +1,32 @@
---
-title: Understanding openstatus
-description: Deep dive into the concepts, architecture, and design decisions behind openstatus
+title: Foundational Concepts
+description: Understand the core ideas, architecture, and design decisions that shape OpenStatus.
sidebar:
label: Getting Started
order: 1
---
-## 💡 Concepts
+## Building a solid foundation
-### What you'll find here
+This section of our documentation is dedicated to explanation. It's not about quick fixes or step-by-step instructions. Instead, it's here to help you build a deep understanding of uptime monitoring and the principles behind OpenStatus.
-Our docs help you:
-- Understand core monitoring concepts
-- Learn best practices and design patterns
-- Make informed decisions about your monitoring strategy
-- Appreciate the reasoning behind openstatus features
+A solid mental model will empower you to use our tools more effectively, make better decisions for your own systems, and communicate with your team and stakeholders with clarity and confidence.
-### Core Concepts
+We'll explore the "why" behind the "what," covering core concepts, best practices, and the design philosophy that guides our development.
-Build a solid foundation:
+### Core Concepts
-- **[Uptime Monitoring](/concept/uptime-monitoring)** - What uptime monitoring is, why it matters, and how it works
-- **[Uptime Calculation and Values](/concept/uptime-calculation-and-values)** - How uptime percentages are calculated and what they really mean
-- **[Latency vs Response Time](/concept/latency-vs-response-time)** - Understanding the difference between these crucial metrics
+Start here to grasp the fundamental building blocks of uptime monitoring.
-### Best Practices
+- **[Uptime Monitoring](/concept/uptime-monitoring)**: What is it, why does it matter, and how does it work?
+- **[Uptime Calculation and Values](/concept/uptime-calculation-and-values)**: A look under the hood at how uptime percentages are calculated and what they truly represent.
+- **[Latency vs Response Time](/concept/latency-vs-response-time)**: Untangle the difference between these two critical performance metrics.
-Learn from experience:
+### Best Practices & Philosophy
-- **[Best Practices for Status Pages](/concept/best-practices-status-page)** - How to communicate effectively during incidents and maintain user trust
-- **[Uptime Monitoring as Code](/concept/uptime-monitoring-as-code)** - Why and how to manage monitoring configuration as code
+Learn from experience and understand our approach to modern monitoring.
+- **[Building Trust with Status Pages](/concept/best-practices-status-page)**: How to communicate effectively during incidents and maintain user trust.
+- **[Uptime Monitoring as Code](/concept/uptime-monitoring-as-code)**: The why and how of managing your monitoring configuration in a GitOps workflow.
Have questions or want to discuss these concepts? [Join our community](/help/support/) and share your thoughts!
diff --git a/apps/docs/src/content/docs/concept/uptime-monitoring.mdx b/apps/docs/src/content/docs/concept/uptime-monitoring.mdx
index 7ca59bef0..ca57f6ff6 100644
--- a/apps/docs/src/content/docs/concept/uptime-monitoring.mdx
+++ b/apps/docs/src/content/docs/concept/uptime-monitoring.mdx
@@ -5,12 +5,14 @@ description: A deep dive into uptime monitoring concepts, architecture, and best
## What is uptime monitoring?
-The concept of **uptime monitoring** refers to the practice of continuously checking the availability of a website, server, or application. It's a proactive measure that alerts you to problems as they happen, helping to minimize downtime and its potential negative impacts.
+Uptime monitoring is the practice of continuously asking a simple question: "Is our service working correctly for our users?" It's a systematic, automated process for checking the availability, performance, and correctness of a website, server, or application.
-Uptime monitoring is fundamentally about answering three questions:
-1. **Is my service available?** Can users reach it?
-2. **Is it performing well?** Are response times acceptable?
-3. **Is it functioning correctly?** Is it returning the expected data?
+Instead of waiting for users to report a problem, uptime monitoring acts as a proactive defense, alerting you the moment an issue arises. This helps you minimize downtime and protect your reputation.
+
+At its core, uptime monitoring answers three critical questions:
+1. **Is my service available?** Can users reach it?
+2. **Is it performing well?** Are response times fast enough?
+3. **Is it functioning correctly?** Is it returning the expected data and behaving as intended?
```
@@ -135,5 +137,5 @@ Now that you understand uptime monitoring concepts:
- **[Get started with a monitor](/tutorial/how-to-create-monitor)** - Apply these concepts in practice
- **[Learn about uptime calculations](/concept/uptime-calculation-and-values)** - Understand how uptime percentages work
-- **[Best practices for status pages](/concept/best-practices-status-page)** - Communicate effectively during incidents
+- **[Building Trust with Status Pages](/concept/best-practices-status-page)** - Communicate effectively during incidents
- **[Monitoring as Code](/concept/uptime-monitoring-as-code)** - Manage monitoring configuration programmatically
diff --git a/apps/docs/src/content/docs/guides/how-deploy-status-page-cf-pages.mdx b/apps/docs/src/content/docs/guides/how-deploy-status-page-cf-pages.mdx
index ab55195ef..b4bad6516 100644
--- a/apps/docs/src/content/docs/guides/how-deploy-status-page-cf-pages.mdx
+++ b/apps/docs/src/content/docs/guides/how-deploy-status-page-cf-pages.mdx
@@ -1,114 +1,79 @@
---
-title: How to deploy your own status page to Cloudflare Pages
-description: Learn how to use openstatus monitoring data and deploy your own Status Page to cloudflare pages.
+title: How to Deploy a Status Page to Cloudflare Pages
+description: Learn how to use openstatus monitoring data to deploy a status page on Cloudflare Pages.
sidebar:
label: Host your status page on Cloudflare Pages
---
import { Image } from 'astro:assets';
import statusPage from '../../../assets/guides/how-deploy-status-page-cf-pages/status-page.png';
-## Introduction
+## Problem
-At openstatus, we believe that monitoring your endpoints should be easy and accessible to everyone.
-We also believe that having a status page is essential for your users to know the status of your services.
-We also think that manually updating your status page is a waste of time. The best way to update your status page is to automate it. That's why we built openstatus.
+You need a fast, reliable, and automated status page, but you don't want to manage the hosting infrastructure. Manually updating a status page during an incident is inefficient and error-prone.
-In this guide, we will show you how to deploy your own status page to Cloudflare Pages using openstatus monitoring data.
+## Solution
-For the Status Page, we will use [Astro](https://astro.build/) a new JavaScript web framework, that allows you to build faster websites with less JavaScript.
+Deploy a custom status page to Cloudflare's global edge network using openstatus as the data source. This guide shows you how to use our Astro-based template to create a status page that automatically reflects your monitoring data.
-The code showcased in this guide is available on [GitHub](https://github.com/openstatusHQ/astro-status-page)
-
-
-
- <Image
- src={statusPage}
- alt="Astro Status Page"
- />
+The code for the template is available on [GitHub](https://github.com/openstatusHQ/astro-status-page).
+<Image
+ src={statusPage}
+ alt="Astro Status Page"
+/>
## Prerequisites
-To follow this guide, you need:
-
-- A Cloudflare Account.
-- An [openstatus](https://www.openstatus.dev) Account.
-
-## Start monitoring your services
-
-To get your monitoring data, you need to create a monitor on openstatus.
-We will monitor the status of your endpoint and get the data to display on your status page.
-
-
-### How to create a monitor
-
-To create a monitor, follow these steps:
-1. Go to the openstatus dashboard.
-2. Click on the `Monitors` tab.
-3. Click on the `Create Monitor` button.
-4. Fill in the form with your endpoint details.
-5. Click on the `Create Monitor` button.
-
+- A Cloudflare account
+- An [openstatus account](https://www.openstatus.dev) with at least one monitor configured.
-### Get your openstatus API key
+## Step-by-step guide
-To get your API key, follow these steps:
+### 1. Get your openstatus API key
-1. Go to the openstatus dashboard.
-2. Click on the `Settings` tab.
-3. Click on the `API Token` tab.
-4. Click on the `Create API Key` button.
-5. Copy your API key.
+First, you need an API key to fetch your monitoring data.
-## Deploy your own status page
+1. Navigate to your openstatus dashboard.
+2. Go to **Settings** → **API Token**.
+3. Click **Create API Key** and copy the key.
-With openstatus monitoring data, you can bring your status page to life. You can really make it your own.
-We are going to deploy a simple status page that shows the status of your endpoint.
+### 2. Set up the Astro project
-For this guide we are going to use our [Astro Status Page](https://github.com/openstatusHQ/astro-status-page) template.
+Clone our status page template and install the dependencies.
-### Customize the Astro Status Page
-
-In the `index.astro` we are fetching the monitor data from openstatus and displaying it on the page.
-
-```ts
-const response = await fetch("https://api.openstatus.dev/v1/monitor", {
- headers: {
- "x-openstatus-key": env.API_KEY,
- },
-});
-
-const data = await response.json();
-
-
-const r = monitorsSchema.parse(data);
-
-// our monitors id
-const monitorIds = [1]
-const result = r.filter((m) => monitorIds.find(id => m.id === id) );
+```bash
+git clone https://github.com/openstatusHQ/astro-status-page.git
+cd astro-status-page
+npm install
```
-In the line `const monitorIds = [1]` you need to replace `1` with the list of monitors id you want to display.
+### 3. Customize the status page
+You need to specify which monitors to display on your page.
-### Deploy the Astro Status Page to Cloudflare Pages
+1. Open the `src/pages/index.astro` file.
+2. Find the following line of code:
+ ```javascript
+ const monitorIds = [1]
+ ```
+3. Replace the `1` with the ID of the monitor you want to display. You can find the monitor ID in the URL when you view a monitor in the openstatus dashboard (`/monitors/[ID]`). You can also add multiple IDs: `[1, 2, 5]`.
-First in your Cloudflare dashboard you need to set the environment variable.
+### 4. Configure your Cloudflare environment variable
-Go to your Cloudflare dashboard and click on the `Workers & Pages`.
+Before deploying, you must provide your openstatus API key to Cloudflare.
-Select your site and click on the `Settings` tab.
+1. Go to your Cloudflare dashboard and click on **Workers & Pages**.
+2. Select your site and go to the **Settings** tab.
+3. Navigate to **Environment variables** and add a new variable:
+ - **Variable name**: `API_KEY`
+ - **Value**: Paste your openstatus API key here.
-You can add your openstatus API key as an environment variable.
-
-```env
-API_KEY=your-api-key
-```
+### 5. Deploy to Cloudflare Pages
-Now you can deploy your Astro Status Page to Cloudflare Pages with the following command:
+Now you can deploy your status page.
```bash
npm run pages:deploy
```
-Your Status Page is now live on Cloudflare Pages. 🎉
+After the command completes, your status page will be live on Cloudflare Pages. 🎉
diff --git a/apps/docs/src/content/docs/guides/how-to-add-svg-status-badge.mdx b/apps/docs/src/content/docs/guides/how-to-add-svg-status-badge.mdx
index 38362822e..4466f92f8 100644
--- a/apps/docs/src/content/docs/guides/how-to-add-svg-status-badge.mdx
+++ b/apps/docs/src/content/docs/guides/how-to-add-svg-status-badge.mdx
@@ -1,78 +1,103 @@
---
-title: How to Add an SVG Status Badge to your GitHub README
+title: How to Add a Status Badge to a GitHub README
+description: A step-by-step guide to adding a real-time SVG or PNG status badge to your GitHub repository.
---
-You want to add an SVG status badge to your GitHub README?
+## Problem
-### PNG Badge
+You want to display the real-time status of your service directly in your GitHub repository's README file. This provides immediate visibility to your users and team members about the health of your application.
-```html
-<img src='https://[slug].openstatus.dev/badge'>
-```
+## Solution
+
+openstatus provides embeddable status badges that you can add to any Markdown file, including your `README.md`. You can choose between a modern SVG badge or a legacy PNG badge.
+
+## Prerequisites
+
+- An openstatus account with a configured status page.
+- The "slug" of your status page (the unique name in its URL, e.g., `https://[slug].openstatus.dev`).
-This will return a PNG image with the status of your page. It will look like this:
-<img src='https://status.openstatus.dev/badge' />
+## Step-by-step guide
-You can customize the theme by adding `?theme=dark` and the size of it by adding `?size=lg`.
+### Step 1: Choose your badge type
-Supported themes:
-- `dark`
-- `light` (default)
+We recommend using the modern SVG badge (v2) as it offers more customization options.
-Supported sizes:
-- `sm` (default)
-- `md`
-- `lg`
-- `xl`
+- **SVG Badge (v2)**: More flexible, better styling, and uses a monospaced font.
+- **PNG Badge (Legacy)**: Simpler, but with fewer customization options.
+
+### Step 2: Add the badge to your README
+
+Copy the Markdown snippet for your chosen badge type and paste it into your `README.md` file. **Remember to replace `[slug]` with your status page slug.**
+
+---
-It will display the following labels based on the current status of the status page:
+#### Option A: Modern SVG Badge (Recommended)
+
+This is the recommended badge for most use cases.
+
+##### Base URL
```
-Operational
-Degraded
-Outage
-Incident
-Maintenance
-Unknown
+https://[slug].openstatus.dev/badge/v2
```
-### SVG Badge (v2)
+##### Markdown Snippet
+
+```
+![Status](https://[slug].openstatus.dev/badge/v2)
+```
+
+**Example:**
+
+![Status](https://status.openstatus.dev/badge/v2)
+
+##### Customization
+
+You can customize the badge by adding query parameters to the URL.
+
+- **Theme**: `?theme=dark` (default is `light`)
+- **Size**: `?size=md` (options: `sm`, `md`, `lg`, `xl`; default is `sm`)
+- **Variant**: `?variant=outline` (adds a border; default has no border)
+
+**Example with all options:**
-```html
-<img src='https://[slug].openstatus.dev/badge/v2'>
+```
+![Status](https://[slug].openstatus.dev/badge/v2?theme=dark&size=lg&variant=outline)
```
-This will return a PNG image with the status of your page. It will look like this:
-<img src='https://status.openstatus.dev/badge/v2' />
+---
-You can customize the theme by adding `?theme=dark`, the size of it by adding `?size=lg` and the variant `?variant=outline` - use what fits best to you!
+#### Option B: Legacy PNG Badge
-Supported themes:
-- `light` (default)
-- `dark`
+Use this badge if you prefer the older style.
-Supported sizes:
-- `sm` (default)
-- `md`
-- `lg`
-- `xl`
+##### Base URL
-Supported variants:
-- `default` (default)
-- `outline`
+```
+https://[slug].openstatus.dev/badge
+```
-The **outline** variant simply adds a slightly rounded border to the svg `rect`. It mainly can be used for GitHub README or Markdown where styling is not supported.
+##### Markdown Snippet
-Compared to the PNG badge, we let you define the `border` and `border-radius` of the SVG badge and the font is mono.
+```markdown
+![Status](https://[slug].openstatus.dev/badge)
+```
+
+**Example:**
+
+![Status](https://status.openstatus.dev/badge)
+
+##### Customization
-It will display the following labels based on the current status of the status page:
+- **Theme**: `?theme=dark` (default is `light`)
+- **Size**: `?size=lg` (options: `sm`, `md`, `lg`, `xl`; default is `sm`)
+
+**Example with all options:**
```
-All Systems Operational
-Degraded Performance
-Partial Outage
-Major Outage
-Ongoing Incident
-Under Maintenance
-Unknown
+![Status](https://[slug].openstatus.dev/badge?theme=dark&size=lg)
```
+
+### Step 3: Commit your changes
+
+Save your `README.md` file and commit it to your repository. The status badge will now be visible to anyone visiting your repository. It will automatically update to reflect the current status of your services.
diff --git a/apps/docs/src/content/docs/guides/how-to-deploy-probes-cloudflare-containers.mdx b/apps/docs/src/content/docs/guides/how-to-deploy-probes-cloudflare-containers.mdx
index 1cda48af2..5455c00a8 100644
--- a/apps/docs/src/content/docs/guides/how-to-deploy-probes-cloudflare-containers.mdx
+++ b/apps/docs/src/content/docs/guides/how-to-deploy-probes-cloudflare-containers.mdx
@@ -1,6 +1,6 @@
---
-title: How to deploy the openstatus probe to Cloudflare Containers
-description: Learn how to use openstatus monitoring data and deploy your own Status Page to cloudflare pages.
+title: How to Deploy a Private Probe on Cloudflare Containers
+description: A step-by-step guide to deploying an openstatus private monitoring probe on Cloudflare Containers.
sidebar:
label: Deploy private probes on Cloudflare Containers
---
@@ -9,120 +9,134 @@ import log from '../../../assets/guides/how-to-deploy-probes-cf-containters/clou
import os from '../../../assets/guides/how-to-deploy-probes-cf-containters/private-location.jpg';
-In this guide we will show you how to deploy the openstatus probe to Cloudflare Containers.
+## Problem
-Cloudflare Containers is a platform that allows you to run serverless containers in the Cloudflare network.
+You need to monitor internal services that are not accessible from the public internet, or you want to run checks from your own infrastructure for compliance or performance reasons. You need a lightweight, serverless way to run these monitoring probes without managing virtual machines.
-Cloudflare containers automatically scales down after a given time. We will push a cron worker that will keep our container alive and running on Cloudflare Containers platform.
+## Solution
-The code showcased in this guide is available on [GitHub](https://github.com/openstatusHQ/private-location-cloudflare-container)
+Deploy the openstatus private location probe as a serverless container using Cloudflare Containers. This allows you to run monitoring checks from within your own network infrastructure, managed by Cloudflare. This guide will walk you through the entire process, from creating the private location in openstatus to deploying the container.
-### Requirements
-- A Cloudflare Account.
-- An [openstatus](https://www.openstatus.dev) Account.
+The code for the Cloudflare Worker template is available on [GitHub](https://github.com/openstatusHQ/private-location-cloudflare-container).
+## Prerequisites
+- A Cloudflare account
+- An [openstatus account](https://www.openstatus.dev)
+- `pnpm` and `docker` installed on your local machine
+## Step-by-step guide
-### Create a private location on openstatus
+### 1. Create a private location in openstatus
-1. Go to the openstatus dashboard.
-2. Click on the `Private locations` in the sidebar.
-3. Click on the `Create Private Location` button.
-4. Give it a human readable name.
-5. Save token.
-6. Click submit to save the newly created private location.
+First, you need to create a private location in your openstatus workspace to get an access key.
-### Create a Cloudflare Container
+1. Go to the openstatus dashboard.
+2. Click on **Private locations** in the sidebar.
+3. Click **Create Private Location**.
+4. Give it a human-readable name (e.g., "Cloudflare-EU").
+5. Copy the generated token and save it somewhere secure.
+6. Click **Submit** to save the new private location.
-1. Create a new cloudflare workers container template using the following command:
+### 2. Set up the Cloudflare project
+
+Next, create a new Cloudflare project using the containers template.
```bash
pnpm create cloudflare@latest --template=cloudflare/templates/containers-template
```
-2. Fetch openstatus private location image from Docker Hub, we need to specify the platform to linux/amd64 because Cloudflare Containers currently only supports amd64 architecture.:
+### 3. Pull and tag the probe Docker image
-```bash
-docker docker pull --platform linux/amd64 ghcr.io/openstatushq/private-location:latest
-```
-
-3. Tag the image, be aware we cannot use the `latest` tag on Cloudflare Containers:
+Pull the official openstatus private location image from Docker Hub. You must specify the `linux/amd64` platform, as this is what Cloudflare Containers supports.
```bash
+# Pull the image
+docker pull --platform linux/amd64 ghcr.io/openstatushq/private-location:latest
+
+# Tag the image for Cloudflare (you cannot use the 'latest' tag)
docker tag ghcr.io/openstatushq/private-location:latest openstatus-private-location:v1
```
-4. Push the image to Cloudflare Container Registry:
+### 4. Push the image to Cloudflare Container Registry
+
+Push the tagged image to your Cloudflare account's container registry.
```bash
pnpm wrangler containers push openstatus-private-location:v1
```
-5. Update the `wrangler.toml` file to use the pushed image:
-
-```toml
-[containers]
- image = "registry.cloudflare.com/GENERATED_ID/openstatus-private-location:cf-1"
-```
-
-6. Update the worker to use a cron trigger to keep the container alive, add the following to your `wrangler.toml` file:
-
-```toml
-triggers = { cron = ["*/2 * * * *"] }
-```
-
-7. Update the `index.ts` file to run a simple command to keep the container alive:
-
-```ts
-sleepAfter = "150s";
-```
-and
-
-```ts
-async scheduled(_controller: any, env: Env) {
- try {
- const container = getContainer(env.MY_CONTAINER);
- await container.start({
- envVars: {
- OPENSTATUS_KEY: env.OPENSTATUS_KEY,
- },
- });
- } catch (e) {
- console.error("Error in scheduled task:", e);
- }
-
- return new Response("ok");
-},
-```
-
-9. Add you openstatus API secret
+### 5. Configure `wrangler.toml`
+
+Now, configure your Cloudflare project to use the container and run it on a schedule.
+
+1. Open the `wrangler.toml` file.
+2. Add a `[containers]` section to link the image you pushed. Replace `GENERATED_ID` with the actual ID from the previous step's output.
+ ```toml
+ [containers]
+ image = "registry.cloudflare.com/GENERATED_ID/openstatus-private-location:v1"
+ ```
+3. Add a `triggers` section to run the worker on a cron schedule. This keeps the container alive, as Cloudflare Containers automatically scales to zero.
+ ```toml
+ triggers = { cron = ["*/2 * * * *"] } # Runs every 2 minutes
+ ```
+
+### 6. Configure the worker
+
+Update the worker script (`index.ts`) to start the container with the correct environment variables.
+
+1. Set the `sleepAfter` value to control how long the container runs after being invoked.
+ ```typescript
+ sleepAfter = "150s";
+ ```
+2. Update the `scheduled` function to pass your openstatus key to the container.
+ ```typescript
+ async scheduled(_controller: any, env: Env) {
+ try {
+ const container = getContainer(env.MY_CONTAINER);
+ await container.start({
+ envVars: {
+ OPENSTATUS_KEY: env.OPENSTATUS_KEY,
+ },
+ });
+ } catch (e) {
+ console.error("Error in scheduled task:", e);
+ }
+
+ return new Response("ok");
+ },
+ ```
+
+### 7. Add your openstatus key as a secret
+
+Securely provide your private location token to the Cloudflare worker.
```bash
+# Paste the token you saved in Step 1 when prompted
pnpm wrangler secret put OPENSTATUS_KEY
```
+### 8. Deploy the application
-10. Deploy the container to Cloudflare Containers:
+Finally, deploy the worker and container to Cloudflare.
```bash
pnpm wrangler deploy
```
+Your private location probe is now running on Cloudflare Containers and will start picking up monitoring jobs from your openstatus workspace.
+## Verify the deployment
+You can check the logs of your Cloudflare Worker to see the probe in action. In your openstatus dashboard, the private location should now show as connected.
-## Conclusion
-
-You have successfully deployed the openstatus private location probe to Cloudflare Containers. Thus you can monitor your endpoint from Cloudflare's global network.
-
-
- <Image
+<Image
src={log}
- alt="openstatus Private Location on Cloudflare Containers"
- caption="Cloudflare Workers Logs showing openstatus Private Location running"
+ alt="Cloudflare Workers Logs showing openstatus Private Location running"
+ caption="Cloudflare Workers logs showing the private probe running."
/>
- <Image
+<Image
src={os}
- alt="openstatus Private Location on Cloudflare Containers"
+ alt="openstatus Private Location connected"
+ caption="The private location showing as 'Connected' in the openstatus dashboard."
/>
diff --git a/apps/docs/src/content/docs/guides/how-to-export-metrics-to-otlp-endpoint.mdx b/apps/docs/src/content/docs/guides/how-to-export-metrics-to-otlp-endpoint.mdx
index d67eafd66..157e9baff 100644
--- a/apps/docs/src/content/docs/guides/how-to-export-metrics-to-otlp-endpoint.mdx
+++ b/apps/docs/src/content/docs/guides/how-to-export-metrics-to-otlp-endpoint.mdx
@@ -1,5 +1,6 @@
---
-title: How to Export Metrics to your OTLP endpoint
+title: How to Export Metrics to an OTLP Endpoint
+description: A step-by-step guide to sending openstatus metrics to your observability platform via OTLP.
---
import { Image } from 'astro:assets';
@@ -8,56 +9,91 @@ import newrelic from '../../../assets/guides/how-to-export-metrics-via-otel/new
import signoz from '../../../assets/guides/how-to-export-metrics-via-otel/signoz.jpg';
import honeycomb from '../../../assets/guides/how-to-export-metrics-via-otel/honeycomb.jpg';
+## Problem
-At openstatus, we believe you should be able to export your metrics to your OTLP endpoint without having to change your existing monitoring platform.
+You want to analyze your openstatus monitoring data alongside other telemetry data in your existing observability platform (like Grafana, New Relic, or Honeycomb). You need a standardized way to export these metrics without building a custom integration.
+## Solution
+openstatus can export monitoring metrics to any OTLP (OpenTelemetry Protocol) compatible endpoint. By adding a simple configuration to your `openstatus.yaml` file, you can have metrics from every check sent directly to your monitoring stack.
-## Export your metrics to your OTLP endpoint
+## Prerequisites
-In your monitoring platform find the configuration section for metrics export.
+- An observability platform that supports OTLP metric ingestion over HTTP.
+- An `openstatus.yaml` file to configure your monitors.
+- The [openstatus CLI](/tutorial/get-started-with-openstatus-cli) to apply your configuration.
-Right now we only support HTTP OTLP endpoint.
+## Step-by-step guide
-In your `openstatus.yaml` file, add the following configuration:
+### 1. Locate your OTLP endpoint URL and headers
+
+First, you need to find the specific URL and any required authentication headers from your observability platform. This is usually found in the documentation under "OTLP," "OpenTelemetry," or "Metrics Export."
+
+- **Endpoint URL**: Look for an HTTP endpoint for OTLP metrics. It will typically end in `/v1/metrics`. For example: `https://otlp.your-provider.com/v1/metrics`.
+- **Headers**: You will likely need an authentication header, such as `Authorization: Bearer YOUR_API_KEY` or `X-API-Key: YOUR_API_KEY`.
+
+### 2. Configure your `openstatus.yaml` file
+
+Open your `openstatus.yaml` file and add the `openTelemetry` block at the top level.
```yaml
+# yaml-language-server: $schema=https://www.openstatus.dev/schema.json
+
openTelemetry:
- endpoint: http://your-otel-endpoint:4318/v1/metrics
+ endpoint: <YOUR_OTLP_ENDPOINT_URL>
headers:
- Authorization: Bearer your-token
+ Authorization: Bearer <YOUR_TOKEN>
+ # Add any other required headers here
+
+# Your monitors are defined below
+my-first-monitor:
+ # ...
```
-After every check we will send you the metrics to your monitoring stack.
+Replace `<YOUR_OTLP_ENDPOINT_URL>` and `<YOUR_TOKEN>` with the values you found in step 1.
+
+**Note**: Currently, we only support OTLP over HTTP.
+
+### 3. Apply the configuration
+
+Use the openstatus CLI to apply the changes to your account.
+
+```bash
+openstatus apply
+```
+After applying the configuration, openstatus will send metrics to your specified endpoint after every check is completed.
-### Grafana
+### 4. Verify in your observability platform
- <Image
- src={grafana}
- alt="openstatus metrics in grafana"
- />
+Go to your observability platform and look for the new metrics coming from openstatus. You should be able to build dashboards and alerts based on this data.
-### honeycomb
+Here are some examples of what it can look like:
- <Image
- src={honeycomb}
- alt="openstatus metrics in honeycomb"
- />
+#### Grafana
+<Image
+ src={grafana}
+ alt="openstatus metrics in grafana"
+/>
-### New Relic
+#### Honeycomb
- <Image
- src={newrelic}
- alt="openstatus metrics in new-relic"
- />
+<Image
+ src={honeycomb}
+ alt="openstatus metrics in honeycomb"
+/>
+#### New Relic
+<Image
+ src={newrelic}
+ alt="openstatus metrics in new-relic"
+/>
-### signoz
+#### SigNoz
- <Image
- src={signoz}
- alt="openstatus metrics in signoz"
- />
+<Image
+ src={signoz}
+ alt="openstatus metrics in signoz"
+/>
diff --git a/apps/docs/src/content/docs/guides/how-to-monitor-mcp-server.mdx b/apps/docs/src/content/docs/guides/how-to-monitor-mcp-server.mdx
index f9e859864..9dc4f7517 100644
--- a/apps/docs/src/content/docs/guides/how-to-monitor-mcp-server.mdx
+++ b/apps/docs/src/content/docs/guides/how-to-monitor-mcp-server.mdx
@@ -28,17 +28,13 @@ A Model Context Provider (MCP) is a crucial component that extends AI models wit
### The MCP Server and JSON-RPC 2.0
-The MCP server is the backend component that hosts these external resources. It processes incoming requests from MCP clients, executes specified actions, and returns information according to the [JSON-RPC 2.0 specification](https://www.jsonrpc.org/specification). JSON-RPC is a lightweight remote procedure call protocol using JSON for data exchange. While transport-independent, MCP servers typically use HTTP/HTTPS, making them readily monitorable by openstatus.
+## Step-by-step guide
-### The Ping Utility: Health Check Standard
+### 1. Create your `openstatus.yaml` file
-For robust monitoring, the official [MCP documentation](https://modelcontextprotocol.io/docs/concepts/architecture#debugging-and-monitoring) recommends implementing a health check using the **ping utility**. This simple request/response mechanism verifies the server's responsiveness and is the foundation for our openstatus monitor.
+openstatus allows you to define and manage your monitors using a YAML configuration file, which is ideal for GitOps workflows. This approach ensures your monitoring setup is version-controlled, auditable, and easily deployable.
-## Create Your openstatus Monitor: YAML Configuration
-
-openstatus allows you to define and manage your monitors using YAML configuration files, a perfect solution for GitOps workflows. This approach ensures your monitoring setup is version-controlled, auditable, and easily deployable via the openstatus CLI.
-
-Here's an example of a monitor configuration for a Hugging Face MCP server, which you can adapt for your own MCP endpoint:
+Create a file named `openstatus.yaml` and add the following configuration, adapting it for your own MCP endpoint. This example targets a Hugging Face MCP server.
```yaml
# yaml-language-server: $schema=https://www.openstatus.dev/schema.json
@@ -73,46 +69,27 @@ mcp-server:
target: '{"result":{},"jsonrpc":"2.0","id":"openstatus"}'
```
-### Understanding the Configuration
+### 2. Understand the configuration
Let's break down the key fields in this YAML configuration:
-- `name`: A human-readable name for your monitor (e.g., "HF MCP Server").
-- `description`: A brief explanation of what this monitor checks.
-- `frequency`: How often openstatus will run the check. Common values include `30s`, `1m`, `5m`, `10m`, `30m`, `1h`. Setting a sensible frequency balances timely alerts with resource usage.
-- `active`: Set to `true` to enable the monitor, `false` to disable it.
-- `regions`: An array of geographic regions from which openstatus will perform the checks (e.g., `["iad", "ams", "lax"]` for North America, Europe, and West US). Monitoring from multiple regions helps detect localized issues.
-- `retry`: The number of times openstatus will retry a failed check before marking it as genuinely down. This helps prevent false positives due to transient network issues.
-- `kind`: Specifies the type of monitor. For MCP servers using HTTP/HTTPS, this will be `http`.
+- `name` & `description`: A human-readable name and explanation for your monitor.
+- `frequency`: How often openstatus will run the check (e.g., `1m`, `5m`, `10m`).
+- `regions`: An array of geographic regions from which to perform checks (e.g., `["iad", "ams", "lax"]`). Monitoring from multiple regions helps detect localized issues.
+- `retry`: The number of times to retry a failed check before marking it as down.
+- `kind`: Must be `http` for MCP servers.
- `request`:
- `url`: The full URL of your MCP server's JSON-RPC endpoint.
- - `method`: The HTTP method, which should be `POST` for JSON-RPC requests.
- - `body`: The JSON-RPC `ping` request payload. The `"method": "ping"` is crucial for triggering the health check on your MCP server.
- ```json
- {
- "jsonrpc": "2.0",
- "id": "openstatus",
- "method": "ping"
- }
- ```
+ - `method`: Must be `POST` for JSON-RPC requests.
+ - `body`: The JSON-RPC `ping` request payload.
- `headers`: Standard HTTP headers for JSON-RPC communication.
-- `assertions`: Rules to validate the response from your MCP server. These are critical for determining if the server is healthy.
- - **Status Code Check**: `statusCode` assertion ensures the HTTP response is `200` (OK).
- ```yaml
- - kind: statusCode
- compare: eq
- target: 200
- ```
- - **Response Body Check**: `textBody` assertion verifies that the response payload matches the expected JSON-RPC `ping` result. The `target` value must precisely match the successful `ping` response from your MCP server.
- ```yaml
- - kind: textBody
- compare: eq
- target: '{"result":{},"jsonrpc":"2.0","id":"openstatus"}'
- ```
-
-### Testing Your MCP Server (Optional)
-
-Before deploying your openstatus monitor, it's a good practice to manually test your MCP server's `ping` endpoint using `curl` to ensure it responds as expected. This helps in debugging and confirming the `target` value for your `textBody` assertion.
+- `assertions`: Rules to validate the server's response.
+ - `statusCode`: Ensures the HTTP response is `200 OK`.
+ - `textBody`: Verifies that the response payload exactly matches the expected JSON-RPC `ping` result.
+
+### 3. Test your MCP server (Optional)
+
+Before deploying your monitor, you can manually test your MCP server's `ping` endpoint with `curl` to confirm it responds as expected. This helps verify the `target` value for your `textBody` assertion.
```bash
curl -X POST \\
@@ -121,17 +98,17 @@ curl -X POST \\
https://hf.co/mcp # Replace with your MCP server URL
```
-This command should return a JSON response similar to `{"result":{},"jsonrpc":"2.0","id":"openstatus"}` if your MCP server is healthy and correctly implements the `ping` utility.
+A healthy server should return a JSON response like `{"result":{},"jsonrpc":"2.0","id":"openstatus"}`.
-### Using openstatus CLI to Create Your Monitor
+### 4. Deploy your monitor
-Once your `openstatus.yaml` file is ready, create your monitor using the openstatus CLI:
+Once your `openstatus.yaml` file is ready, use the openstatus CLI to create the monitor:
```bash
openstatus create openstatus.yaml
```
-This command will upload your monitor configuration to openstatus, and monitoring will begin according to the specified `frequency` and `regions`.
+This command uploads your configuration, and monitoring will begin immediately.
## Conclusion: Comprehensive MCP Server Monitoring Achieved
diff --git a/apps/docs/src/content/docs/tutorial/how-to-configure-status-page.mdx b/apps/docs/src/content/docs/tutorial/how-to-configure-status-page.mdx
index 09add01e1..a33fea28d 100644
--- a/apps/docs/src/content/docs/tutorial/how-to-configure-status-page.mdx
+++ b/apps/docs/src/content/docs/tutorial/how-to-configure-status-page.mdx
@@ -139,14 +139,14 @@ Excellent work! You've successfully:
Now that your status page is configured, you can:
- **[Configure Notifications](/monitoring/customization/notification)** - Alert your team when issues occur
-- **[Best Practices for Status Pages](/concept/best-practices-status-page)** - Learn effective incident communication
+- **[Building Trust with Status Pages](/concept/best-practices-status-page)** - Learn effective incident communication
- **[Add Status Subscribers](/reference/subscriber)** - Let users subscribe to updates
### Learn more
- **[Status Page Reference](/reference/status-page)** - Complete configuration options
- **[Uptime Calculation Values](/concept/uptime-calculation-and-values)** - How uptime percentages work
-- **[See Examples](https://www.openstatus.dev/showcase)** - Browse other status pages for inspiration
+
## Video Tutorial
diff --git a/apps/docs/src/content/docs/tutorial/how-to-create-status-page.mdx b/apps/docs/src/content/docs/tutorial/how-to-create-status-page.mdx
index 5dfee0562..dec59a1c3 100644
--- a/apps/docs/src/content/docs/tutorial/how-to-create-status-page.mdx
+++ b/apps/docs/src/content/docs/tutorial/how-to-create-status-page.mdx
@@ -76,7 +76,7 @@ Now that you have a basic status page, you can:
- **[Configure Your Status Page](/tutorial/how-to-configure-status-page)** - Customize appearance and add more features
- **[Configure Notifications](/monitoring/customization/notification)** - Alert your team when issues occur
-- **[Best Practices for Status Pages](/concept/best-practices-status-page)** - Learn how to communicate effectively
+- **[Building Trust with Status Pages](/concept/best-practices-status-page)** - Learn how to communicate effectively
### Learn more
diff --git a/infra/openstatus.lock b/infra/openstatus.lock
deleted file mode 100644
index a987b68d8..000000000
--- a/infra/openstatus.lock
+++ /dev/null
@@ -1,229 +0,0 @@
-openstat.us:
- ID: 2085
- Monitor:
- active: true
- frequency: 1m
- kind: http
- name: openstat.us
- public: true
- regions:
- - ams
- - iad
- - syd
- - gru
- - sin
- request:
- method: GET
- url: https://openstat.us
- retry: 3
-openstatus:
- ID: 1
- Monitor:
- active: true
- description: "Our website \U0001F310"
- frequency: 10m
- kind: http
- name: 'OpenStatus '
- public: true
- regions:
- - ams
- - iad
- - jnb
- - hkg
- - gru
- - syd
- - mad
- - cdg
- - bom
- - sin
- - fra
- - otp
- - lhr
- - arn
- - waw
- - atl
- - bos
- - den
- - dfw
- - ord
- - gdl
- - lax
- - mia
- - qro
- - phx
- - yul
- - sjc
- - sea
- - ewr
- - yyz
- - bog
- - eze
- - gig
- - scl
- request:
- method: GET
- url: https://www.openstatus.dev
- retry: 3
-openstatus api server:
- ID: 771
- Monitor:
- active: true
- description: "Our API Server \U0001F50C"
- frequency: 10m
- kind: http
- name: OpenStatus API
- public: true
- regions:
- - ams
- - iad
- - jnb
- - hkg
- - gru
- - syd
- - nrt
- - fra
- - lhr
- - bom
- - otp
- - sin
- - cdg
- - mad
- - waw
- - arn
- - atl
- - bos
- - den
- - dfw
- - ord
- - gdl
- - lax
- - mia
- - qro
- - phx
- - yul
- - sjc
- - sea
- - ewr
- - yyz
- - bog
- - eze
- - gig
- - scl
- request:
- method: GET
- url: https://api.openstatus.dev/ping
- retry: 3
-openstatus astro status page:
- ID: 2662
- Monitor:
- active: true
- frequency: 1h
- kind: http
- name: OpenStatus Astro Status Page
- public: true
- regions:
- - ams
- - iad
- - hkg
- - jnb
- - syd
- - gru
- request:
- method: GET
- url: https://astro.openstat.us/
- retry: 3
-openstatus status page:
- ID: 666
- Monitor:
- active: true
- description: "We are monitoring our own Status Page \U0001F4DD"
- frequency: 10m
- kind: http
- name: OpenStatus Status Page
- public: true
- regions:
- - ams
- - iad
- - jnb
- - hkg
- - gru
- - syd
- - bom
- - sin
- - fra
- - otp
- - lhr
- - mad
- - cdg
- - waw
- - arn
- - atl
- - bos
- - den
- - dfw
- - ord
- - gdl
- - lax
- - mia
- - qro
- - phx
- - sjc
- - yul
- - sea
- - ewr
- - yyz
- - bog
- - scl
- - eze
- - gig
- request:
- method: GET
- url: https://status.openstatus.dev/
- retry: 3
-openstatus tcp check:
- ID: 4667
- Monitor:
- active: true
- frequency: 1m
- kind: tcp
- name: OpenStatus TCP
- regions:
- - ams
- - arn
- - atl
- - bog
- - bom
- - bos
- - cdg
- - den
- - dfw
- - ewr
- - eze
- - fra
- - gdl
- - gig
- - gru
- - hkg
- - iad
- - jnb
- - lax
- - lhr
- - mad
- - mia
- - nrt
- - ord
- - otp
- - phx
- - qro
- - scl
- - sea
- - sin
- - sjc
- - syd
- - waw
- - yul
- - yyz
- request:
- host: openstatus.dev
- port: 443
- retry: 3
diff --git a/infra/openstatus.yaml b/infra/openstatus.yaml
deleted file mode 100644
index 58950f1b8..000000000
--- a/infra/openstatus.yaml
+++ /dev/null
@@ -1,194 +0,0 @@
-# yaml-language-server: $schema=https://www.openstatus.dev/schema.json
-
-"openstatus":
- active: true
- description: "Our website \U0001F310"
- frequency: 10m
- kind: http
- name: 'OpenStatus '
- public: true
- regions:
- - ams
- - iad
- - jnb
- - gru
- - syd
- - cdg
- - bom
- - sin
- - fra
- - lhr
- - arn
- - den
- - dfw
- - ord
- - lax
- - sjc
- - ewr
- - yyz
- - koyeb_fra
- - koyeb_par
- - koyeb_sfo
- - koyeb_sin
- - koyeb_tyo
- - koyeb_was
- - railway_asia-southeast1-eqsg3a
- - railway_europe-west4-drams3a
- - railway_us-east4-eqdc4a
- - railway_us-west2
- request:
- method: GET
- url: https://www.openstatus.dev
- retry: 3
-"openstatus status page":
- active: true
- description: "We are monitoring our own Status Page \U0001F4DD"
- frequency: 10m
- kind: http
- name: OpenStatus Status Page
- public: true
- regions:
- - ams
- - iad
- - jnb
- - gru
- - syd
- - bom
- - sin
- - fra
- - lhr
- - cdg
- - arn
- - den
- - dfw
- - ord
- - lax
- - sjc
- - ewr
- - yyz
- - koyeb_fra
- - koyeb_par
- - koyeb_sfo
- - koyeb_sin
- - koyeb_tyo
- - koyeb_was
- - railway_asia-southeast1-eqsg3a
- - railway_europe-west4-drams3a
- - railway_us-east4-eqdc4a
- - railway_us-west2
-
- request:
- method: GET
- url: https://status.openstatus.dev/
- retry: 3
-"openstatus api server":
- active: true
- description: "Our API Server \U0001F50C"
- frequency: 10m
- kind: http
- name: OpenStatus API
- public: true
- regions:
- - ams
- - iad
- - jnb
- - gru
- - syd
- - bom
- - sin
- - fra
- - lhr
- - cdg
- - arn
- - den
- - dfw
- - ord
- - lax
- - sjc
- - ewr
- - yyz
- - koyeb_fra
- - koyeb_par
- - koyeb_sfo
- - koyeb_sin
- - koyeb_tyo
- - koyeb_was
- - railway_asia-southeast1-eqsg3a
- - railway_europe-west4-drams3a
- - railway_us-east4-eqdc4a
- - railway_us-west2
- request:
- method: GET
- url: https://api.openstatus.dev/ping
- retry: 3
-"openstat.us":
- active: true
- frequency: 1m
- kind: http
- name: openstat.us
- public: true
- regions:
- - ams
- - iad
- - syd
- - gru
- - sin
- request:
- method: GET
- url: https://openstat.us
- retry: 3
-"openstatus astro status page":
- active: true
- frequency: 1h
- kind: http
- name: OpenStatus Astro Status Page
- public: true
- regions:
- - ams
- - iad
- - sin
- - jnb
- - syd
- - gru
- request:
- method: GET
- url: https://astro.openstat.us/
- retry: 3
-"openstatus tcp check":
- active: true
- frequency: 1m
- kind: tcp
- name: 'OpenStatus TCP'
- regions:
- - ams
- - iad
- - jnb
- - gru
- - syd
- - bom
- - sin
- - fra
- - lhr
- - cdg
- - arn
- - den
- - dfw
- - ord
- - lax
- - sjc
- - ewr
- - yyz
- - koyeb_fra
- - koyeb_par
- - koyeb_sfo
- - koyeb_sin
- - koyeb_tyo
- - koyeb_was
- - railway_asia-southeast1-eqsg3a
- - railway_europe-west4-drams3a
- - railway_us-east4-eqdc4a
- - railway_us-west2
- request:
- host: openstatus.dev
- port: 443
- retry: 3
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index e4e7c2aba..37680ca07 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -349,50 +349,50 @@ importers:
apps/docs:
dependencies:
'@astrojs/check':
- specifier: 0.9.4
+ specifier: 0.9.6
'@astrojs/react':
- specifier: 4.3.1
+ specifier: 4.4.2
'@astrojs/sitemap':
- specifier: 3.5.1
- version: 3.5.1
+ specifier: 3.6.0
+ version: 3.6.0
'@astrojs/starlight':
- specifier: 0.35.2
+ specifier: 0.37.1
'@astrojs/starlight-tailwind':
- specifier: 4.0.1
+ specifier: 4.0.2
'@fontsource-variable/inter':
specifier: 5.2.8
version: 5.2.8
'@openpanel/astro':
specifier: 1.0.1
'@tailwindcss/vite':
specifier: 4.1.8
astro:
- specifier: 5.13.7
+ specifier: 5.16.6
sharp:
specifier: 0.33.5
version: 0.33.5
starlight-image-zoom:
- specifier: 0.13.0
+ specifier: 0.13.2
starlight-links-validator:
- specifier: 0.17.2
+ specifier: 0.19.2
starlight-llms-txt:
- specifier: 0.5.1
+ specifier: 0.7.0
starlight-showcases:
- specifier: 0.3.0
+ specifier: 0.3.1
starlight-sidebar-topics:
- specifier: 0.6.0
+ specifier: 0.6.2
tailwindcss:
specifier: 4.1.11
version: 4.1.11
@@ -2123,8 +2123,8 @@ packages:
peerDependencies:
astro: ^2.0.0 || ^3.0.0-beta || ^4.0.0-beta || ^5.0.0-beta
- '@astrojs/[email protected]':
- resolution: {integrity: sha512-IOheHwCtpUfvogHHsvu0AbeRZEnjJg3MopdLddkJE70mULItS/Vh37BHcI00mcOJcH1vhD3odbpvWokpxam7xA==}
+ '@astrojs/[email protected]':
+ resolution: {integrity: sha512-jlaEu5SxvSgmfGIFfNgcn5/f+29H61NJzEMfAZ82Xopr4XBchXB1GVlcJsE+elUlsYSbXlptZLX+JMG3b/wZEA==}
hasBin: true
peerDependencies:
typescript: ^5.0.0
@@ -2132,14 +2132,11 @@ packages:
'@astrojs/[email protected]':
resolution: {integrity: sha512-mqVORhUJViA28fwHYaWmsXSzLO9osbdZ5ImUfxBarqsYdMlPbqAqGJCxsNzvppp1BEzc1mJNjOVvQqeDN8Vspw==}
- '@astrojs/[email protected]':
- resolution: {integrity: sha512-KCkCqR3Goym79soqEtbtLzJfqhTWMyVaizUi35FLzgGSzBotSw8DB1qwsu7U96ihOJgYhDk2nVPz+3LnXPeX6g==}
-
'@astrojs/[email protected]':
resolution: {integrity: sha512-vreGnYSSKhAjFJCWAwe/CNhONvoc5lokxtRoZims+0wa3KbHBdPHSSthJsKxPd8d/aic6lWKpRTYGY/hsgK6EA==}
- '@astrojs/[email protected]':
- resolution: {integrity: sha512-oX2KkuIfEEM5d4/+lfuxy6usRDYko0S02YvtHFTrnqW0h9e4ElAfWZRKyqxWlwpuPdciBPKef5YJ7DFH3PPssw==}
+ '@astrojs/[email protected]':
+ resolution: {integrity: sha512-J3hVx/mFi3FwEzKf8ExYXQNERogD6RXswtbU+TyrxoXRBiQoBO5ooo7/lRWJ+rlUKUd7+rziMPI9jYB7TRlh0w==}
hasBin: true
peerDependencies:
prettier: ^3.0.0
@@ -2150,8 +2147,8 @@ packages:
prettier-plugin-astro:
optional: true
- '@astrojs/[email protected]':
- resolution: {integrity: sha512-bwylYktCTsLMVoCOEHbn2GSUA3c5KT/qilekBKA3CBng0bo1TYjNZPr761vxumRk9kJGqTOtU+fgCAp5Vwokug==}
+ '@astrojs/[email protected]':
+ resolution: {integrity: sha512-kk4HeYR6AcnzC4QV8iSlOfh+N8TZ3MEStxPyenyCtemqn8IpEATBFMTJcfrNW32dgpt6MY3oCkMM/Tv3/I4G3A==}
'@astrojs/[email protected]':
resolution: {integrity: sha512-hX2cLC/KW74Io1zIbn92kI482j9J7LleBLGCVU9EP3BeH5MVrnFawOnqD0t/q6D1Z+ZNeQG2gNKMslCcO36wng==}
@@ -2162,12 +2159,18 @@ packages:
peerDependencies:
astro: ^5.0.0
+ '@astrojs/[email protected]':
+ resolution: {integrity: sha512-IHDHVKz0JfKBy3//52JSiyWv089b7GVSChIXLrlUOoTLWowG3wr2/8hkaEgEyd/vysvNQvGk+QhysXpJW5ve6Q==}
+ engines: {node: 18.20.8 || ^20.3.0 || >=22.0.0}
+ peerDependencies:
+ astro: ^5.0.0
+
'@astrojs/[email protected]':
resolution: {integrity: sha512-q8VwfU/fDZNoDOf+r7jUnMC2//H2l0TuQ6FkGJL8vD8nw/q5KiL3DS1KKBI3QhI9UQhpJ5dc7AtqfbXWuOgLCQ==}
engines: {node: 18.20.8 || ^20.3.0 || >=22.0.0}
- '@astrojs/[email protected]':
- resolution: {integrity: sha512-Jhv35TsDHuQLvwof2z10P3g1s9wIR4UN9jE7O4NZBJNXOt/+qk+L0rY9th4SX7VzccKmRltUGxAhI1cXH52gXw==}
+ '@astrojs/[email protected]':
+ resolution: {integrity: sha512-1tl95bpGfuaDMDn8O3x/5Dxii1HPvzjvpL2YTuqOOrQehs60I2DKiDgh1jrKc7G8lv+LQT5H15V6QONQ+9waeQ==}
engines: {node: 18.20.8 || ^20.3.0 || >=22.0.0}
peerDependencies:
'@types/react': ^17.0.50 || ^18.0.21 || ^19.0.0
@@ -2175,17 +2178,17 @@ packages:
react: ^17.0.2 || ^18.0.0 || ^19.0.0
react-dom: ^17.0.2 || ^18.0.0 || ^19.0.0
- '@astrojs/[email protected]':
- resolution: {integrity: sha512-uX5z52GLtQTgOe8r3jeGmFRYrFe52mdpLYJzqjvL1cdy5Kg3MLOZEvaZ/OCH0fSq0t7e50uJQ6oBMZG0ffszBg==}
+ '@astrojs/[email protected]':
+ resolution: {integrity: sha512-4aHkvcOZBWJigRmMIAJwRQXBS+ayoP5z40OklTXYXhUDhwusz+DyDl+nSshY6y9DvkVEavwNcFO8FD81iGhXjg==}
- '@astrojs/[email protected]':
- resolution: {integrity: sha512-AOOEWTGqJ7fG66U04xTmZQZ40oZnUYe4Qljpr+No88ozKywtsD1DiXOrGTeHCnZu0hRtMbRtBGB1fZsf0L62iw==}
+ '@astrojs/[email protected]':
+ resolution: {integrity: sha512-SYN/6zq6hJO5tWqbQ2tWT9/jd8ubUkzkBCcF94vByC/ZJ20Mi5GPjFvAh89Yky/aIM+jXxT6W5q4p6l58GKHiQ==}
peerDependencies:
'@astrojs/starlight': '>=0.34.0'
tailwindcss: ^4.0.0
- '@astrojs/[email protected]':
- resolution: {integrity: sha512-curGghoW4s5pCbW2tINsJPoxEYPan87ptCOv7GZ+S24N3J6AyaOu/OsjZDEMaIpo3ZlObM5DQn+w7iXl3drDhQ==}
+ '@astrojs/[email protected]':
+ resolution: {integrity: sha512-STNsR5PaDoiW4IgcX17Fp42FfyqwuweWPts/EWEMcFPAeg9Nvpu3UvVCorasYrgfJgaJTeydsOV++0ACA1KYDA==}
peerDependencies:
astro: ^5.5.0
@@ -2664,8 +2667,9 @@ packages:
engines: {node: '>=12'}
hasBin: true
- '@capsizecss/[email protected]':
- resolution: {integrity: sha512-GrSU71meACqcmIUxPYOJvGKF0yryjN/L1aCuE9DViCTJI7bfkjgYDPD1zbNDcINJwSSP6UaBZY9GAbYDO7re0Q==}
+ '@capsizecss/[email protected]':
+ resolution: {integrity: sha512-8XqW8xGn++Eqqbz3e9wKuK7mxryeRjs4LOHLxbh2lwKeSbuNR4NFifDZT4KzvjU6HMOPbiNTsWpniK5EJfTWkg==}
+ engines: {node: '>=18'}
'@chronark/[email protected]':
resolution: {integrity: sha512-OWdZt5EULFgDaHTbkxkxN130ohapRxSMaYdaW/fZTcQP3z1c4cYk4izJwbbTPOP4GdQeys18Prls0xz4NpFV0A==}
@@ -2723,9 +2727,8 @@ packages:
'@emmetio/[email protected]':
resolution: {integrity: sha512-s9yjhJ6saOO/uk1V74eifykk2CBYi01STTK3WlXWGOepyKa23ymJ053+DNQjpFcy1ingpaO7AxCcwLvHFY9tuw==}
- '@emmetio/css-parser@https://codeload.github.com/ramya-rao-a/css-parser/tar.gz/370c480ac103bd17c7bcfb34bf5d577dc40d3660':
- resolution: {tarball: https://codeload.github.com/ramya-rao-a/css-parser/tar.gz/370c480ac103bd17c7bcfb34bf5d577dc40d3660}
- version: 0.4.0
+ '@emmetio/[email protected]':
+ resolution: {integrity: sha512-2bC6m0MV/voF4CTZiAbG5MWKbq5EBmDPKu9Sb7s7nVcEzNQlrZP6mFFFlIaISM8X6514H9shWMme1fCm8cWAfQ==}
'@emmetio/[email protected]':
resolution: {integrity: sha512-NTbsvppE5eVyBMuyGfVu2CRrLvo7J4YHb6t9sBFLyY03WYhXET37qA4zOYUjBWFCRHO7pS1B9khERtY0f5JXPQ==}
@@ -5800,21 +5803,39 @@ packages:
'@shikijs/[email protected]':
resolution: {integrity: sha512-8TOG6yG557q+fMsSVa8nkEDOZNTSxjbbR8l6lF2gyr6Np+jrPlslqDxQkN6rMXCECQ3isNPZAGszAfYoJOPGlg==}
+ '@shikijs/[email protected]':
+ resolution: {integrity: sha512-f2ED7HYV4JEk827mtMDwe/yQ25pRiXZmtHjWF8uzZKuKiEsJR7Ce1nuQ+HhV9FzDcbIo4ObBCD9GPTzNuy9S1g==}
+
'@shikijs/[email protected]':
resolution: {integrity: sha512-ZedbOFpopibdLmvTz2sJPJgns8Xvyabe2QbmqMTz07kt1pTzfEvKZc5IqPVO/XFiEbbNyaOpjPBkkr1vlwS+qg==}
+ '@shikijs/[email protected]':
+ resolution: {integrity: sha512-OFx8fHAZuk7I42Z9YAdZ95To6jDePQ9Rnfbw9uSRTSbBhYBp1kEOKv/3jOimcj3VRUKusDYM6DswLauwfhboLg==}
+
'@shikijs/[email protected]':
resolution: {integrity: sha512-HnqFsV11skAHvOArMZdLBZZApRSYS4LSztk2K3016Y9VCyZISnlYUYsL2hzlS7tPqKHvNqmI5JSUJZprXloMvA==}
+ '@shikijs/[email protected]':
+ resolution: {integrity: sha512-Yx3gy7xLzM0ZOjqoxciHjA7dAt5tyzJE3L4uQoM83agahy+PlW244XJSrmJRSBvGYELDhYXPacD4R/cauV5bzQ==}
+
'@shikijs/[email protected]':
resolution: {integrity: sha512-WpRvEFvkVvO65uKYW4Rzxs+IG0gToyM8SARQMtGGsH4GDMNZrr60qdggXrFOsdfOVssG/QQGEl3FnJ3EZ+8w8A==}
+ '@shikijs/[email protected]':
+ resolution: {integrity: sha512-le+bssCxcSHrygCWuOrYJHvjus6zhQ2K7q/0mgjiffRbkhM4o1EWu2m+29l0yEsHDbWaWPNnDUTRVVBvBBeKaA==}
+
'@shikijs/[email protected]':
resolution: {integrity: sha512-8ow2zWb1IDvCKjYb0KiLNrK4offFdkfNVPXb1OZykpLCzRU6j+efkY+Y7VQjNlNFXonSw+4AOdGYtmqykDbRiQ==}
+ '@shikijs/[email protected]':
+ resolution: {integrity: sha512-U1NSU7Sl26Q7ErRvJUouArxfM2euWqq1xaSrbqMu2iqa+tSp0D1Yah8216sDYbdDHw4C8b75UpE65eWorm2erQ==}
+
'@shikijs/[email protected]':
resolution: {integrity: sha512-BnP+y/EQnhihgHy4oIAN+6FFtmfTekwOLsQbRw9hOKwqgNy8Bdsjq8B05oAt/ZgvIWWFrshV71ytOrlPfYjIJw==}
+ '@shikijs/[email protected]':
+ resolution: {integrity: sha512-lhYAATn10nkZcBQ0BlzSbJA3wcmL5MXUUF8d2Zzon6saZDlToKaiRX60n2+ZaHJCmXEcZRWNzn+k9vplr8Jhsw==}
+
'@shikijs/[email protected]':
resolution: {integrity: sha512-83yeghZ2xxin3Nj8z1NMd/NCuca+gsYXswywDy5bHvwlWL8tpTQmzGeUuHd9FC3E/SBEMvzJRwWEOz5gGes9Qg==}
@@ -6772,6 +6793,10 @@ packages:
resolution: {integrity: sha512-gKXj5ALrKWQLsYG9jlTRmR/xKluxHV+Z9QEwNIgCfM1/uwPMCuzVVnh5mwTd+OuBZcwSIMbqssNWRm1lE51QaQ==}
engines: {node: '>=8'}
+ resolution: {integrity: sha512-g6LhBsl+GBPRWGWsBtutpzBYuIIdBkLEvad5C/va/74Db018+5TZiyA26cZJAr3Rft5lprVqOIPxf5Vid6tqAw==}
+ engines: {node: '>=18'}
+
resolution: {integrity: sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==}
engines: {node: '>=8'}
@@ -6843,8 +6868,8 @@ packages:
peerDependencies:
astro: ^4.0.0-beta || ^5.0.0-beta || ^3.3.0
- resolution: {integrity: sha512-Of2tST7ErbE4y1dVb4aWDXaQSIRBAfraJ4jDqaA3PzPRJOn6Ina36+tQ+8BezjYqiWwRRJdOEE07PRAJXnsddw==}
+ resolution: {integrity: sha512-6mF/YrvwwRxLTu+aMEa5pwzKUNl5ZetWbTyZCs9Um0F12HUmxUiF5UHiZPy4rifzU3gtpM3xP2DfdmkNX9eZRg==}
engines: {node: 18.20.8 || ^20.3.0 || >=22.0.0, npm: '>=9.6.5', pnpm: '>=7.1.0'}
hasBin: true
@@ -6908,9 +6933,6 @@ packages:
resolution: {integrity: sha512-tv1ZJHLfTDnXE6tMHv73YgSJaWR2AFuPwMntBe7XL/GBFHnT0CLnsHMogfk5+GzCDC5ZWarSCYaIGATZt9dNsQ==}
- resolution: {integrity: sha512-BF033y5fN6OCofD3vgHmNtwZWRcq9NLyyxyILx9hfMy1sXYy4ojFl765hJ2lP0YaN2fuxPaLO2Vzzoxy0FLFFA==}
-
resolution: {integrity: sha512-nfDwkulwiZYQIGwxdy0RUmowMhKcFVcYXUU7m4QlKYim1rUtg83xm2yjZ40QjDuc291AJjjeSc9b++AWHSgSHw==}
engines: {node: '>=18'}
@@ -7168,6 +7190,10 @@ packages:
resolution: {integrity: sha512-y4Mg2tXshplEbSGzx7amzPwKKOCGuoSRP/CjEdwwk0FOGlUbq6lKuoyDZTNZkmxHdJtp54hdfY/JUrdL7Xfdug==}
engines: {node: '>=14'}
+ resolution: {integrity: sha512-yPVavfyCcRhmorC7rWlkHn15b4wDVgVmBA7kV4QVBsF7kv/9TKJAbAXVTxvTnwP8HHKjRCJDClKbciiYS7p0DQ==}
+ engines: {node: '>=16'}
+
resolution: {integrity: sha512-/rFeCpNJQbhSZjGVwO9RFV3xPqbnERS8MmIQzCtD/zl6gpJuV/bMLuN92oG3F7d8oDEHHRrujSXNUr8fpjntKw==}
engines: {node: '>=18'}
@@ -7261,9 +7287,6 @@ packages:
resolution: {integrity: sha512-dcKFX3jn0MpIaXjisoRvexIJVEKzaq7z2rZKxf+MSr9TkdmHmsU4m2lcLojrj/FHl8mk5VxMmYA+ftRkP/3oKQ==}
- resolution: {integrity: sha512-Q+xVJLoGOeIMXZmbUK4HYk+69cQH6LudR0Vu/pRm2YlU/hDV9CiS0gKUMaWY5f2NeUH9C1nV3bsTlCo0FsTV1Q==}
-
resolution: {integrity: sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==}
engines: {node: '>= 8'}
@@ -7280,6 +7303,10 @@ packages:
resolution: {integrity: sha512-L1bdkNKUP5WYxiW5dW6vA2hd3sL8BdRNLy2FCX0rLVise4eNw9nBdeBuJHxlELieSE2H1f6bYQFfwVUwWCV9rQ==}
+ resolution: {integrity: sha512-OA0mILzGc1kCOCSJerOeqDxDQ4HOh+G8NbOJFOTgOCzpw7fCBubk0fEyxp8AgOL/jvLgYA/uV0cMbe43ElF1JA==}
+ engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0, npm: '>=7.0.0'}
+
resolution: {integrity: sha512-0eW44TGN5SQXU1mWSkKwFstI/22X2bG1nYzZTYMAWjylYURhse752YgbE4Cx46AC+bAvI+/dYTPRk1LqSUnu6w==}
engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0}
@@ -7293,6 +7320,10 @@ packages:
engines: {node: '>=4'}
hasBin: true
+ resolution: {integrity: sha512-0LrrStPOdJj+SPCCrGhzryycLjwcgUSHBtxNA8aIDxf0GLsRh1cKYhB00Gd1lDOS4yGH69+SNn13+TWbVHETFQ==}
+ engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0, npm: '>=7.0.0'}
+
resolution: {integrity: sha512-iKuQcq+NdHqlAcwUY0o/HL69XQrUaQdMjmStJ8JFmUaiiQErlhrmuigkg/CU4E2J0IyUKUrMAgl36TvN67MqTw==}
@@ -7675,6 +7706,10 @@ packages:
resolution: {integrity: sha512-dtJUTepzMW3Lm/NPxRf3wP4642UWhjL2sQxc+ym2YMj1m/H2zDNQOlezafzkHwn6sMstjHTwG6iQQsctDW/b1A==}
engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
+ resolution: {integrity: sha512-xUtoPkMggbz0MPyPiIWr1Kp4aeWJjDZ6SMvURhimjdZgsRuDplF5/s9hcgGhyXMhs+6vpnuoiZ2kFiu3FMnS8Q==}
+ engines: {node: '>=18'}
+
resolution: {integrity: sha512-sqQamAnR14VgCr1A618A3sGrygcpK+HEbenA/HiEAkkUwcZIIB/tgWqHFxWgOyDh4nB4JCRimh79dR5Ywc9MDQ==}
@@ -8109,6 +8144,10 @@ packages:
resolution: {integrity: sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==}
engines: {node: '>=8'}
+ resolution: {integrity: sha512-CsNUt5x9LUdx6hnk/E2SZLsDyvfqANZSUq4+D3D8RzDJ2M+HDTIkF60ibS1vHaK55vzgiZw1bEPFG9yH7l33wA==}
+ engines: {node: '>=12'}
+
resolution: {integrity: sha512-1cDNdwJ2Jaohmb3sg4OmKaMBwuC48sYni5HUw2DvsC8LjGTLK9h+eb1X6RyuOHe4hT0ULCW68iomhjUoKUqlPQ==}
engines: {node: '>= 0.4'}
@@ -8789,8 +8828,8 @@ packages:
resolution: {integrity: sha512-ISQTe55T2ao7XtlAStud6qwYPZjE4GK1S/BeVPus4jrq6JuOnQ00YKQC581RWhR122W7msZV263KzVeLoqidyQ==}
engines: {node: '>=12'}
- resolution: {integrity: sha512-L0WhttDl+2BOsybvEOLK7fW3UA0OQ0IQ2d6Zl2x/a6vVRs3bAY0ECOSHHeL5jD+SbOpOCUEi0y1DgHEn9Qn1AQ==}
+ resolution: {integrity: sha512-xrHS24IxaLrvuo613F719wvOIv9xPHFWQHuvGUBmPnCA/3MQxKI3b+r7n1jAoDHmsbC5bRhTZYR77invLAxVnw==}
resolution: {integrity: sha512-s8UhlNe7vPKomQhC1qFelMokr/Sc3AgNbso3n74mVPA5LTZwkB9NlXf4XPamLxJE8h0gh73rM94xvwRT2CVInw==}
@@ -8865,6 +8904,9 @@ packages:
resolution: {integrity: sha512-0H44vDimn51F0YwvxSJSm0eCDOJTRlmN0R1yBh4HLj9wiV1Dn0QoXGbvFAWj2hSItVTlCmBF1hqKlIyUBVFLPg==}
+ resolution: {integrity: sha512-aylIc7Z9y4yzHYAJNuESG3hfhC+0Ibp/MAMiaOZgNv4pmEdFyfZhhhny4MNiAfWdBQ1RQ2mfDWmM1x8SvGyp8g==}
+
resolution: {integrity: sha512-IEn+pegP1aManZuckezWCO+XZQDplx1366JoVhTpMpBB1sPey/SbveZQUosKiKiGYjg1wH4pMlNgXbCiYgihQA==}
@@ -10128,6 +10170,9 @@ packages:
resolution: {integrity: sha512-kLdkY6iV3dYbtPwS9KXU7mjfmDm25f5m0IPNFnaXO7TBPcvbUOY72PYXSuSqDzwp+vlH/d7MXpHlKO/x+QoLXw==}
+ resolution: {integrity: sha512-kgCOlsnyWb+p0WU+01RjkCH+eBVsjL1jOwUYWv0YDWkM2/A46+LDKVs5yZCUXjJG6bj4ndFoAg5iLIIue6dulg==}
+
resolution: {integrity: sha512-FCLHtRD/gnpCiCHEiJLOwdmFP+wzCmDEkc9y7NsYxeF4u7Btsn1ZuwgwJGxImImHicJArLP4R0yX4c2KCrMrTA==}
engines: {node: '>= 0.4'}
@@ -10243,33 +10288,34 @@ packages:
resolution: {integrity: sha512-WjlahMgHmCJpqzU8bIBy4qtsZdU9lRlcZE3Lvyej6t4tuOuv1vk57OW3MBrj6hXBFx/nNoC9MPMTcr5YA7NQbg==}
engines: {node: '>=6'}
- resolution: {integrity: sha512-7K/7gshnKooYd4ePy5vtyv1jFoFVNUb8IoXWDcnY69+nxvmLATNrmOzD2M4TJ/aKynPSBSM6j9ia4s/PPy/JGA==}
+ resolution: {integrity: sha512-fDJrx+UZXhkbhEeXKoRogTKAYtrYVJPw6wmSUI3nHUTA0vuRM6EI//2Z8bzv3Ecvz0pHKD1vAxtS01mLyessBA==}
engines: {node: '>=18'}
peerDependencies:
'@astrojs/starlight': '>=0.32.0'
- resolution: {integrity: sha512-d2SRWu04HPiUzrzntuv/uzuXnIu4reJwzX1c+7uvcnqOCuzgpv+tmlUC+dp3VYpmfxQy8RX+xcWtfcEkx905VA==}
+ resolution: {integrity: sha512-IHeK3R78fsmv53VfRkGbXkwK1CQEUBHM9QPzBEyoAxjZ/ssi5gjV+F4oNNUppTR48iPp+lEY0MTAmvkX7yNnkw==}
engines: {node: '>=18.17.1'}
peerDependencies:
'@astrojs/starlight': '>=0.32.0'
+ astro: '>=5.1.5'
- resolution: {integrity: sha512-EPhTZ7jOhMxp6BBSpYNWuaJezzI+4eRgkwlFGV/XNNGSjNibo9JHrCvCbJO6BDk4znXcTWi0x8N7FO7ckNXLGQ==}
+ resolution: {integrity: sha512-KAay6JLXqB0GiNQ481z3Z/h/y4xeAU55TUGLz+npjxcRvN3h/7rDxjmyLiphZF8xfoqqSTduQPanl5Ct4Je6kA==}
engines: {node: ^18.17.1 || ^20.3.0 || >=21.0.0}
peerDependencies:
'@astrojs/starlight': '>=0.31'
- astro: ^5.1.6
+ astro: ^5.15.9
- resolution: {integrity: sha512-jxKVE5IM0TZgRIni4YK1oKDh6C9pBh94oj2pKuhzg2/Cg1wjCrWy39U3i1bXkh6rL+Ly+ypQBPH3AD9cP6TLXA==}
+ resolution: {integrity: sha512-czM+aZVnOCb8tVrPFoLND5D6vTKo+xVeQmI4G+whA/vzytL8SXIKT7Evt1TzqTsdQXAFbqSlGjg630/gB063ww==}
engines: {node: '>=18'}
peerDependencies:
'@astrojs/starlight': '>=0.30.0'
- resolution: {integrity: sha512-ysmOR7zaHYKtk18/mpW4MbEMDioR/ZBsisu9bdQrq0v9BlHWpW7gAdWlqFWO9zdv1P7l0Mo1WKd0wJ0UtqOVEQ==}
+ resolution: {integrity: sha512-SNCTUZS/hcVor0ZcaXbaSVU37+V+qtvzNirkvnOg3Mqu/awuGpthkH5+uKpiZqWxLffp6TrOlsv5E5QsxrndNg==}
engines: {node: '>=18'}
peerDependencies:
'@astrojs/starlight': '>=0.32.0'
@@ -10398,6 +10444,10 @@ packages:
resolution: {integrity: sha512-5JRxVqC8I8NuOUjzBbvVJAKNM8qoVuH0O77h4WInc/qC2q5IreqKxYwgkga3PfA22OayK2ikceb/B26dztPl+Q==}
engines: {node: '>=16'}
+ resolution: {integrity: sha512-SS+jx45GF1QjgEXQx4NJZV9ImqmO2NPz5FNsIHrsDjh2YsHnawpan7SNQ1o8NuhrbHZy9AZhIoCUiCeaW/C80g==}
+ engines: {node: '>=18'}
+
resolution: {integrity: sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==}
engines: {node: '>=4'}
@@ -10410,10 +10460,19 @@ packages:
resolution: {integrity: sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==}
engines: {node: '>=10'}
+ resolution: {integrity: sha512-UKbpT93hN5Nr9go5UY7bopIB9YQlMz9nm/ct4IXt/irb5YRkn9WaqrOBJGZ5Pwvsd5FQzSVeYlGdXoCAPQZrPg==}
+ engines: {node: '>=20'}
+
resolution: {integrity: sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==}
engines: {node: '>= 0.4'}
+ resolution: {integrity: sha512-VvrHQ+9uniE+Mvx3+C9IEe/lWasXCU0nXMY2kZeLrHNICuRiC8uMPyM14UEaMOFA5mhyQqEkB02VoQ16n3DLaw==}
+ engines: {node: '>=16'}
+ hasBin: true
+
resolution: {integrity: sha512-CRuDWBTgYfDnBLRaZdKp9VuoPcNUq9An14c/k+4YJ15Qc5Grvf66vp0jvTltd4t7OIRj+8lM1DAgvSgvf7hdLw==}
@@ -10461,6 +10520,10 @@ packages:
resolution: {integrity: sha512-resvxdc6Mgb7YEThw6G6bExlXKkv6+YbuzGg9xuXxSgxJF7Ozs+o8Y9+2R3sArdWdW8nOokoQb1yrpFB0pQK2g==}
engines: {node: '>=14'}
+ resolution: {integrity: sha512-qFAy10MTMwjzjU8U16YS4YoZD+NQLHzLssFMNqgravjbvIPNiqkGFR4yjhJfmY9R5OFU7+yHxc6y+uGHkKwLRA==}
+ engines: {node: '>=20'}
+
resolution: {integrity: sha512-vkZjpUjb6OMS7dhV+tILUW6BhpDR7P2L/aQSAv+Uwk+m8KATX9EccViHTJR2qDtACKPIYndLGCyl3FMo+r2LMw==}
engines: {node: '>= 10.13.0'}
@@ -10501,9 +10564,6 @@ packages:
resolution: {integrity: sha512-XPaBkWQJdsf3pLKJV9p4qN/S+fm2Oj8AIPo1BTUhg5oxkvm9+SVEGFdhyOz7tTdUTfvxMiAs4sp6/eZO2Ew+pw==}
- resolution: {integrity: sha512-KQQR9yN7R5+OSwaK0XQoj22pwHoTlgYqmUscPYoknOoWCWfj/5/ABTMRi69FrKU5ffPVh5QcFikpWJI/P1ocHA==}
-
resolution: {integrity: sha512-W/KYk+NFhkmsYpuHq5JykngiOCnxeVL8v8dFnqxSD8qEEdRfXk1SDM6JzNqcERbcGYj9tMrDQBYV9cjgnunFIg==}
engines: {node: '>=18'}
@@ -10737,8 +10797,8 @@ packages:
resolution: {integrity: sha512-xKvGhPWw3k84Qjh8bI3ZeJjqnyadK+GEFtazSfZv/rKeTkTjOJho6mFqh2SM96iIcZokxiOpg78GazTSg8+KHA==}
- resolution: {integrity: sha512-LzR4WUqzH9ILFvjLAUU7dK3Lnou/qd5kD+IakBtBK4S15/+x2y9VX+DcWQv6s551R6W+vzwgVS6tFg3XggGBgg==}
+ resolution: {integrity: sha512-5Fx50fFQMQL5aeHyWnZX9122sSLckcDvcfFiBf3QYeHa7a1MKJooUy52b67moi2MJYkrfo/TWY+CoLdr/w0tTA==}
resolution: {integrity: sha512-amQa0Ep2m6hE2g72AugUItjbuM8X8cGQnFoHk0pGfrFeT9GZhzN5SW8nRsiGKK7Aif4CrACPENkA6P/Lw6fHGQ==}
@@ -11039,32 +11099,32 @@ packages:
vite:
optional: true
- resolution: {integrity: sha512-XrL1V9LEAHnunglYdDf/7shJbQXqKsHB+P69zPmJTqHx6hqvM9GWNbn2h7M0P/oElW8p/MTVHdfjl6C8cxdsBQ==}
+ resolution: {integrity: sha512-zV7C6enn9T9tuvQ6iSUyYEs34iPXR69Pf9YYWpbFYPWzVs22w96BtE8p04XYXbmjU6unt5oFt+iLL77bMB5fhA==}
peerDependencies:
'@volar/language-service': ~2.4.0
peerDependenciesMeta:
'@volar/language-service':
optional: true
- resolution: {integrity: sha512-BMPSpm6mk0DAEVdI2haxYIOt1Z2oaIZvCGtXuRu95x50a5pOSRPjdeHv2uGp1rQsq1Izigx+VR/bZUf2HcSnVQ==}
+ resolution: {integrity: sha512-UDBL5x7KptmuJZNCCXMlCndMhFult/tj+9jXq3FH1ZGS1E4M/1U5hC06pg1c6e4kn+vnR6bqmvX0vIhL4f98+A==}
peerDependencies:
'@volar/language-service': ~2.4.0
peerDependenciesMeta:
'@volar/language-service':
optional: true
- resolution: {integrity: sha512-MKKD2qM8qVZvBKBIugt00+Bm8j1ehgeX7Cm5XwgeEgdW/3PhUEEe/aeTxQGon1WJIGf2MM/cHPjZxPJOQN4WfQ==}
+ resolution: {integrity: sha512-ljREMF79JbcjNvObiv69HK2HCl5UT7WTD10zi6CRFUHMbPfiF2UZ42HGLsEGSzaHGZz6H4IFjSS/qfENRLUviQ==}
peerDependencies:
'@volar/language-service': ~2.4.0
peerDependenciesMeta:
'@volar/language-service':
optional: true
- resolution: {integrity: sha512-CVaQEyfmFWoq3NhNVExoyDKonPqdacmb/07w7OfTZljxLgZpDRygiHAvzBKIcenb7rKtJNHqfQJv99ULOinJBA==}
+ resolution: {integrity: sha512-B4KnPJPNWFTkEDa6Fn08i5PpO6T1CecmLLTFZoXz2eI4Fxwba/3nDaaVSsEP7e/vEe+U5YqV9fBzayJT71G5xg==}
peerDependencies:
'@volar/language-service': ~2.4.0
prettier: ^2.2 || ^3.0
@@ -11074,24 +11134,24 @@ packages:
prettier:
optional: true
- resolution: {integrity: sha512-PA3CyvEaBrkxJcBq+HFdks1TF1oJ8H+jTOTQUurLDRkVjmUFg8bfdya6U/dWfTsPaDSRM4m/2chwgew5zoQXfg==}
+ resolution: {integrity: sha512-LD2R7WivDYp1SPgZrxx/0222xVTitDjm36oKo5+bfYG5kEgnw+BOPVHdwmvpJKg/RfssfxDI1ouwD4XkEDEfbA==}
peerDependencies:
'@volar/language-service': ~2.4.0
peerDependenciesMeta:
'@volar/language-service':
optional: true
- resolution: {integrity: sha512-8irsfCEf86R1RqPijrU6p5NCqKDNzyJNWKM6ZXmCcJqhebtl7Hr/a0bnlr59AzqkS3Ym4PbbJZs1K/92CXTDsw==}
+ resolution: {integrity: sha512-rfQBy36Rm1PU9vLWHk8BYJ4r2j/CI024vocJcH4Nb6K2RTc2Irmw6UOVY5DdGiPRV5r+e10wLMK5njj/EcL8sA==}
peerDependencies:
'@volar/language-service': ~2.4.0
peerDependenciesMeta:
'@volar/language-service':
optional: true
- resolution: {integrity: sha512-q6oTKD6EMEu1ws1FDjRw+cfCF69Gu51IEGM9jVbtmSZS1qQHKxMqlt2+wBInKl2D+xILtjzkWbfkjQyBYQMw7g==}
+ resolution: {integrity: sha512-jkdP/RF6wPIXEE3Ktnd81oJPn7aAvnVSiaqQHThC2Hrvo6xd9pEcqtbBUI+YfqVgvcMtXAkbtNO61K2GPhAiuA==}
peerDependencies:
'@volar/language-service': ~2.4.0
peerDependenciesMeta:
@@ -11380,10 +11440,10 @@ snapshots:
openapi3-ts: 4.5.0
zod: 4.1.13
dependencies:
'@astro-community/astro-embed-utils': 0.1.5
transitivePeerDependencies:
- canvas
@@ -11393,14 +11453,14 @@ snapshots:
transitivePeerDependencies:
- canvas
dependencies:
lite-youtube-embed: 0.3.4
dependencies:
- '@astrojs/language-server': 2.16.0([email protected])([email protected])
+ '@astrojs/language-server': 2.16.2([email protected])([email protected])
chokidar: 4.0.3
kleur: 4.1.5
typescript: 5.9.3
@@ -11411,11 +11471,9 @@ snapshots:
'@astrojs/[email protected]': {}
- '@astrojs/[email protected]': {}
-
'@astrojs/[email protected]': {}
dependencies:
'@astrojs/compiler': 2.13.0
'@astrojs/yaml2ts': 0.2.2
@@ -11426,13 +11484,13 @@ snapshots:
'@volar/language-service': 2.4.26
fast-glob: 3.3.3
muggle-string: 0.4.1
- volar-service-css: 0.0.66(@volar/[email protected])
- volar-service-emmet: 0.0.66(@volar/[email protected])
- volar-service-html: 0.0.66(@volar/[email protected])
- volar-service-prettier: 0.0.66(@volar/[email protected])([email protected])
- volar-service-typescript: 0.0.66(@volar/[email protected])
- volar-service-typescript-twoslash-queries: 0.0.66(@volar/[email protected])
- volar-service-yaml: 0.0.66(@volar/[email protected])
+ volar-service-css: 0.0.67(@volar/[email protected])
+ volar-service-emmet: 0.0.67(@volar/[email protected])
+ volar-service-html: 0.0.67(@volar/[email protected])
+ volar-service-prettier: 0.0.67(@volar/[email protected])([email protected])
+ volar-service-typescript: 0.0.67(@volar/[email protected])
+ volar-service-typescript-twoslash-queries: 0.0.67(@volar/[email protected])
+ volar-service-yaml: 0.0.67(@volar/[email protected])
vscode-html-languageservice: 5.6.0
vscode-uri: 3.1.0
optionalDependencies:
@@ -11440,9 +11498,9 @@ snapshots:
transitivePeerDependencies:
- typescript
- '@astrojs/[email protected]':
+ '@astrojs/[email protected]':
dependencies:
- '@astrojs/internal-helpers': 0.7.2
+ '@astrojs/internal-helpers': 0.7.5
'@astrojs/prism': 3.3.0
github-slugger: 2.0.0
hast-util-from-html: 2.0.3
@@ -11456,7 +11514,7 @@ snapshots:
remark-parse: 11.0.0
remark-rehype: 11.1.2
remark-smartypants: 3.0.2
- shiki: 3.15.0
+ shiki: 3.20.0
smol-toml: 1.5.2
unified: 11.0.5
unist-util-remove-position: 5.0.0
@@ -11492,12 +11550,31 @@ snapshots:
transitivePeerDependencies:
- supports-color
dependencies:
'@astrojs/markdown-remark': 6.3.9
'@mdx-js/mdx': 3.1.1
acorn: 8.15.0
+ es-module-lexer: 1.7.0
+ estree-util-visit: 2.0.0
+ hast-util-to-html: 9.0.5
+ piccolore: 0.1.3
+ rehype-raw: 7.0.0
+ remark-gfm: 4.0.1
+ remark-smartypants: 3.0.2
+ source-map: 0.7.6
+ unist-util-visit: 5.0.0
+ vfile: 6.0.3
+ transitivePeerDependencies:
+ - supports-color
+
+ dependencies:
+ '@astrojs/markdown-remark': 6.3.10
+ '@mdx-js/mdx': 3.1.1
+ acorn: 8.15.0
es-module-lexer: 1.7.0
estree-util-visit: 2.0.0
hast-util-to-html: 9.0.5
@@ -11515,7 +11592,7 @@ snapshots:
dependencies:
prismjs: 1.30.0
dependencies:
'@types/react': 19.2.2
'@types/react-dom': 19.2.2(@types/[email protected])
@@ -11538,28 +11615,28 @@ snapshots:
- tsx
- yaml
- '@astrojs/[email protected]':
+ '@astrojs/[email protected]':
dependencies:
sitemap: 8.0.2
stream-replace-string: 2.0.0
zod: 3.25.76
dependencies:
tailwindcss: 4.1.11
dependencies:
'@astrojs/markdown-remark': 6.3.9
- '@astrojs/sitemap': 3.5.1
+ '@astrojs/sitemap': 3.6.0
'@pagefind/default-ui': 1.4.0
'@types/hast': 3.0.4
'@types/js-yaml': 4.0.9
'@types/mdast': 4.0.4
bcp-47: 2.1.0
hast-util-from-html: 2.0.3
hast-util-select: 6.0.4
@@ -11568,6 +11645,7 @@ snapshots:
i18next: 23.16.8
js-yaml: 4.1.1
klona: 2.0.6
+ magic-string: 0.30.21
mdast-util-directive: 3.1.0
mdast-util-to-markdown: 2.1.2
mdast-util-to-string: 4.0.0
@@ -12398,13 +12476,9 @@ snapshots:
'@bufbuild/buf-win32-arm64': 1.57.2
'@bufbuild/buf-win32-x64': 1.57.2
- '@capsizecss/[email protected]':
+ '@capsizecss/[email protected]':
dependencies:
- blob-to-buffer: 1.2.9
- cross-fetch: 3.2.0
fontkit: 2.0.4
- transitivePeerDependencies:
- - encoding
dependencies:
@@ -12462,7 +12536,7 @@ snapshots:
dependencies:
'@emmetio/scanner': 1.0.4
- '@emmetio/css-parser@https://codeload.github.com/ramya-rao-a/css-parser/tar.gz/370c480ac103bd17c7bcfb34bf5d577dc40d3660':
+ '@emmetio/[email protected]':
dependencies:
'@emmetio/stream-reader': 2.2.0
'@emmetio/stream-reader-utils': 0.1.0
@@ -13315,10 +13389,10 @@ snapshots:
'@open-draft/[email protected]': {}
dependencies:
'@openpanel/web': 1.0.1
dependencies:
@@ -15395,30 +15469,61 @@ snapshots:
'@types/hast': 3.0.4
hast-util-to-html: 9.0.5
+ '@shikijs/[email protected]':
+ dependencies:
+ '@shikijs/types': 3.20.0
+ '@shikijs/vscode-textmate': 10.0.2
+ '@types/hast': 3.0.4
+ hast-util-to-html: 9.0.5
+
'@shikijs/[email protected]':
dependencies:
'@shikijs/types': 3.15.0
'@shikijs/vscode-textmate': 10.0.2
oniguruma-to-es: 4.3.4
+ '@shikijs/[email protected]':
+ dependencies:
+ '@shikijs/types': 3.20.0
+ '@shikijs/vscode-textmate': 10.0.2
+ oniguruma-to-es: 4.3.4
+
'@shikijs/[email protected]':
dependencies:
'@shikijs/types': 3.15.0
'@shikijs/vscode-textmate': 10.0.2
+ '@shikijs/[email protected]':
+ dependencies:
+ '@shikijs/types': 3.20.0
+ '@shikijs/vscode-textmate': 10.0.2
+
'@shikijs/[email protected]':
dependencies:
'@shikijs/types': 3.15.0
+ '@shikijs/[email protected]':
+ dependencies:
+ '@shikijs/types': 3.20.0
+
'@shikijs/[email protected]':
dependencies:
'@shikijs/types': 3.15.0
+ '@shikijs/[email protected]':
+ dependencies:
+ '@shikijs/types': 3.20.0
+
'@shikijs/[email protected]':
dependencies:
'@shikijs/vscode-textmate': 10.0.2
'@types/hast': 3.0.4
+ '@shikijs/[email protected]':
+ dependencies:
+ '@shikijs/vscode-textmate': 10.0.2
+ '@types/hast': 3.0.4
+
'@shikijs/[email protected]': {}
'@smithy/[email protected]':
@@ -16551,6 +16656,10 @@ snapshots:
dependencies:
type-fest: 0.21.3
+ dependencies:
+ environment: 1.1.0
+
@@ -16600,18 +16709,18 @@ snapshots:
dependencies:
rehype-expressive-code: 0.41.3
dependencies:
'@astrojs/compiler': 2.13.0
- '@astrojs/internal-helpers': 0.7.2
- '@astrojs/markdown-remark': 6.3.6
+ '@astrojs/internal-helpers': 0.7.5
+ '@astrojs/markdown-remark': 6.3.10
'@astrojs/telemetry': 3.3.0
- '@capsizecss/unpack': 2.4.0
+ '@capsizecss/unpack': 3.0.1
'@oslojs/encoding': 1.1.0
'@rollup/pluginutils': 5.3.0([email protected])
acorn: 8.15.0
@@ -16639,25 +16748,26 @@ snapshots:
http-cache-semantics: 4.2.0
import-meta-resolve: 4.2.0
js-yaml: 4.1.1
- kleur: 4.1.5
magic-string: 0.30.21
- magicast: 0.3.5
+ magicast: 0.5.1
mrmime: 2.0.1
neotraverse: 0.6.18
p-limit: 6.2.0
p-queue: 8.1.1
package-manager-detector: 1.5.0
+ piccolore: 0.1.3
picomatch: 4.0.3
prompts: 2.4.2
rehype: 13.0.2
semver: 7.7.3
shiki: 3.15.0
smol-toml: 1.5.2
- tinyexec: 0.3.2
+ svgo: 4.0.0
+ tinyexec: 1.0.2
tinyglobby: 0.2.15
tsconfck: 3.1.6([email protected])
ultrahtml: 1.6.0
- unifont: 0.5.2
+ unifont: 0.6.0
unist-util-visit: 5.0.0
unstorage: 1.17.3
vfile: 6.0.3
@@ -16689,7 +16799,6 @@ snapshots:
- '@vercel/kv'
- aws4fetch
- db0
- - encoding
- idb-keyval
- ioredis
- jiti
@@ -16764,8 +16873,6 @@ snapshots:
inherits: 2.0.4
readable-stream: 3.6.2
-
dependencies:
bytes: 3.1.2
@@ -17046,6 +17153,8 @@ snapshots:
+
@@ -17127,12 +17236,6 @@ snapshots:
- dependencies:
- node-fetch: 2.7.0
- transitivePeerDependencies:
- - encoding
-
dependencies:
path-key: 3.1.1
@@ -17155,6 +17258,11 @@ snapshots:
+ dependencies:
+ mdn-data: 2.0.28
+ source-map-js: 1.2.1
+
dependencies:
mdn-data: 2.12.2
@@ -17164,6 +17272,10 @@ snapshots:
+ dependencies:
+ css-tree: 2.2.1
+
@@ -17435,6 +17547,8 @@ snapshots:
+
dependencies:
is-arrayish: 0.2.1
@@ -18031,6 +18145,8 @@ snapshots:
+
@@ -18813,7 +18929,7 @@ snapshots:
dependencies:
'@jridgewell/sourcemap-codec': 1.5.5
dependencies:
'@babel/parser': 7.28.5
'@babel/types': 7.28.5
@@ -19012,6 +19128,8 @@ snapshots:
dependencies:
'@types/mdast': 4.0.4
+
@@ -20745,6 +20863,17 @@ snapshots:
'@shikijs/vscode-textmate': 10.0.2
'@types/hast': 3.0.4
+ dependencies:
+ '@shikijs/core': 3.20.0
+ '@shikijs/engine-javascript': 3.20.0
+ '@shikijs/engine-oniguruma': 3.20.0
+ '@shikijs/langs': 3.20.0
+ '@shikijs/themes': 3.20.0
+ '@shikijs/types': 3.20.0
+ '@shikijs/vscode-textmate': 10.0.2
+ '@types/hast': 3.0.4
+
dependencies:
es-errors: 1.3.0
@@ -20878,9 +21007,9 @@ snapshots:
dependencies:
type-fest: 0.7.1
dependencies:
mdast-util-mdx-jsx: 3.2.0
rehype-raw: 7.0.0
unist-util-visit: 5.0.0
@@ -20888,10 +21017,11 @@ snapshots:
transitivePeerDependencies:
- supports-color
dependencies:
'@types/picomatch': 3.0.2
github-slugger: 2.0.0
hast-util-from-html: 2.0.3
hast-util-has-property: 3.0.0
@@ -20900,17 +21030,18 @@ snapshots:
mdast-util-mdx-jsx: 3.2.0
mdast-util-to-string: 4.0.0
picomatch: 4.0.3
+ terminal-link: 5.0.0
unist-util-visit: 5.0.0
transitivePeerDependencies:
- supports-color
dependencies:
'@types/hast': 3.0.4
'@types/micromatch': 4.0.10
github-slugger: 2.0.0
hast-util-select: 6.0.4
micromatch: 4.0.8
@@ -20923,18 +21054,18 @@ snapshots:
transitivePeerDependencies:
- supports-color
dependencies:
transitivePeerDependencies:
- astro
- canvas
dependencies:
picomatch: 4.0.3
@@ -21054,6 +21185,8 @@ snapshots:
dependencies:
copy-anything: 3.0.5
+
dependencies:
has-flag: 3.0.0
@@ -21066,8 +21199,23 @@ snapshots:
dependencies:
has-flag: 4.0.0
+ dependencies:
+ has-flag: 5.0.1
+ supports-color: 10.2.2
+
+ dependencies:
+ commander: 11.1.0
+ css-select: 5.2.2
+ css-tree: 3.1.0
+ css-what: 6.2.2
+ csso: 5.0.5
+ picocolors: 1.1.1
+ sax: 1.4.3
+
dependencies:
'@stablelib/base64': 1.0.1
@@ -21129,6 +21277,11 @@ snapshots:
- encoding
- supports-color
+ dependencies:
+ ansi-escapes: 7.2.0
+ supports-hyperlinks: 4.4.0
+
dependencies:
'@jridgewell/trace-mapping': 0.3.31
@@ -21161,8 +21314,6 @@ snapshots:
-
@@ -21452,7 +21603,7 @@ snapshots:
trough: 2.2.0
vfile: 6.0.3
dependencies:
css-tree: 3.1.0
ofetch: 1.5.1
@@ -21708,7 +21859,7 @@ snapshots:
optionalDependencies:
dependencies:
vscode-css-languageservice: 6.3.8
vscode-languageserver-textdocument: 1.0.12
@@ -21716,16 +21867,16 @@ snapshots:
optionalDependencies:
'@volar/language-service': 2.4.26
dependencies:
- '@emmetio/css-parser': https://codeload.github.com/ramya-rao-a/css-parser/tar.gz/370c480ac103bd17c7bcfb34bf5d577dc40d3660
+ '@emmetio/css-parser': 0.4.1
'@emmetio/html-matcher': 1.3.0
'@vscode/emmet-helper': 2.11.0
vscode-uri: 3.1.0
optionalDependencies:
'@volar/language-service': 2.4.26
dependencies:
vscode-html-languageservice: 5.6.0
vscode-languageserver-textdocument: 1.0.12
@@ -21733,20 +21884,20 @@ snapshots:
optionalDependencies:
'@volar/language-service': 2.4.26
dependencies:
vscode-uri: 3.1.0
optionalDependencies:
'@volar/language-service': 2.4.26
prettier: 3.6.2
dependencies:
vscode-uri: 3.1.0
optionalDependencies:
'@volar/language-service': 2.4.26
dependencies:
path-browserify: 1.0.1
semver: 7.7.3
@@ -21757,7 +21908,7 @@ snapshots:
optionalDependencies:
'@volar/language-service': 2.4.26
dependencies:
vscode-uri: 3.1.0
yaml-language-server: 1.19.2