Hayden Bleasel

This commit performs a routine **maintenance** task by **bumping the project version** to `6.0.2`. This update primarily affects the project's **versioning metadata**, signaling a new release or development iteration. While not introducing new features or bug fixes directly, it provides a clear identifier for the current state of the codebase, impacting users and downstream dependencies tracking specific versions.

This commit performs routine **maintenance** by updating the project's **`CHANGELOG.md`** file. It incorporates recent changes, bug fixes, and new features into the official **release notes**, ensuring the documentation accurately reflects the current state of the codebase. This update provides users and contributors with an up-to-date and comprehensive record of modifications, improving transparency and understanding of project evolution.

This commit **refactors** the project's **linting and formatting toolchain**, replacing the JavaScript-based ESLint and Prettier with the Rust-based `oxlint` and `oxfmt`, managed by `Ultracite`. This significant **maintenance** update impacts **CI/CD workflows**, pre-commit hooks, and all package configurations across the monorepo. The change results in a **6x speedup** for linting and formatting tasks in CI, reducing combined execution time from 3m 27s to 36s. It also streamlines developer experience by consolidating configuration and aligning the project with Vercel's internal tooling standards.

This commit **updates the project's version number** to `6.0.1`, reflecting a minor release or patch. This **maintenance** task primarily affects the **project metadata and build configuration**, ensuring that all subsequent builds and deployments are correctly identified with the new version. This change is crucial for **release management and dependency tracking**, signifying a small, non-breaking update to the software.

This commit performs routine **maintenance** by updating the project's **`CHANGELOG.md`** file. It incorporates recent changes, bug fixes, and new features into the official **release notes**, ensuring the documentation accurately reflects the current state of the codebase. This update provides users and contributors with an up-to-date and comprehensive record of modifications, improving transparency and understanding of project evolution.

This commit performs routine **maintenance** by updating the project's **`CHANGELOG.md`** file. It incorporates recent changes, bug fixes, and new features into the official **release notes**, ensuring the documentation accurately reflects the current state of the codebase. This update provides users and contributors with an up-to-date and comprehensive record of modifications, improving transparency and understanding of project evolution.

This commit performs a **major version bump** for the entire project, updating the official version number to **6.0.0**. This **maintenance** task signifies a new official release, likely introducing **breaking changes** or substantial new features that warrant a major version increment. The update impacts all **downstream consumers** of the project, requiring them to review potential **API incompatibilities** when upgrading. This action sets the new baseline for future development and releases.

This commit **refactors** the **OIDC authentication setup** by eliminating a custom `sed` command from the workflow. It now leverages the built-in capabilities of the `setup-node` action to handle the OIDC exchange process directly. This change **simplifies the CI/CD pipeline** for Node.js projects, making the authentication configuration more robust and easier to maintain. The **authentication mechanism** for Node.js environments is streamlined, reducing reliance on manual string manipulation and improving overall reliability.

This commit performs **maintenance** on the **GitHub Actions release workflow** (`.github/workflows/release.yml`) to enhance the automated publishing process. It reintroduces the `registry-url` for the Node.js setup and **updates the npm package manager** within the CI/CD pipeline. Crucially, this change **configures npm for OpenID Connect (OIDC) authentication** by removing the explicit `authToken`, thereby improving security and streamlining the package publishing mechanism. This ensures a more robust and secure automated release process for the project.

This commit **removes the explicit `registry-url` configuration** from the project's settings, specifically the `registry-url` entry. This **configuration adjustment** is a **critical enabler** for the **`npm` package manager** to directly leverage **OpenID Connect (OIDC)** for authenticating with package registries. By eliminating this hardcoded URL, the system can now dynamically resolve registry access via OIDC, streamlining authentication workflows and enhancing security posture. This change primarily impacts the **CI/CD pipeline** and local development environments by simplifying credential management for `npm` operations.

This commit performs **maintenance** by **normalizing the format of repository URLs** across the system. The change ensures that all stored or processed repository links adhere to a consistent standard, improving data integrity and reliability. This standardization primarily affects components responsible for managing and interacting with code repositories, such as those handling cloning, fetching, or displaying repository information. The overall impact is a more robust and predictable handling of repository links, preventing potential inconsistencies in external integrations or internal processing.

This commit introduces a **maintenance update** by configuring the `publishConfig` within the `package.json` file. This change specifically enables **npm OIDC provenance** for the package publishing process, enhancing the security and verifiability of released artifacts. The primary impact is an improvement to the **supply chain security** of the package, allowing consumers to verify the origin and build process through OpenID Connect. This ensures that future package releases will include cryptographic proof of their build environment, bolstering trust in the published software.

This commit provides a **maintenance fix** to the **release CI pipeline** by updating the `.autorc` configuration. Specifically, it **disables the `setRcToken` option** within the `npm` plugin, which is crucial for enabling **OIDC trusted publishing** for npm packages. This change ensures that the automated release process correctly handles npm authentication without relying on the `auto` tool to set the token directly. The adjustment streamlines the **npm package publishing** mechanism, preventing potential CI failures related to modern OIDC-based publishing workflows.

This commit **updates the CI/CD release pipeline configuration** defined in `release.yml`. The changes primarily involve **maintenance** and **workflow improvements** to the project's **release automation system**. This ensures a more robust and efficient **release process**, directly impacting how new versions are built, tagged, and deployed to production.

This commit performs a **maintenance update** to the **GitHub Actions release workflow** defined in `.github/workflows/release.yml`. It upgrades the Node.js version used in the CI/CD pipeline to **Node.js v22**, adds explicit permissions for workflow jobs, and clears the `NPM_TOKEN` environment variable for enhanced security. These changes ensure the project's automated release process is up-to-date and secure, aligning with current best practices for CI/CD environments.

This commit performs **maintenance** on the **CMS package** by updating its TypeScript configuration. It adds a reference path directive for `basehub-types.d.ts` to `packages/cms/index.ts`. This ensures that the necessary **type definitions** are correctly recognized and available within the module, improving **developer experience**. The change facilitates better type checking and autocompletion, preventing potential type-related issues during development within the CMS.

This commit **refactors** the **EdgeDB example** by migrating its Markdown rendering from `react-markdown` to our internal `streamdown` library in static mode. This change primarily affects the blog post display in `Post.tsx` and `[id].tsx`, improving the rendering mechanism. Additionally, it introduces a **new styling capability** by integrating **Tailwind CSS** and **PostCSS** into the example, setting up `postcss.config.js`, `tailwind.config.js`, and a new `global.css` stylesheet. The `package.json` is updated to reflect these dependency changes, providing a more modern and efficient styling solution for the example application.

This commit **updates the documentation system** by **enhancing SEO and discoverability** for documentation pages. It achieves this by adding alternate link metadata through the `generateMetadata` function in `docs/app/[lang]/docs/[[...slug]]/page.tsx`. Additionally, it **streamlines the AI message rendering component** by **removing the math and mermaid markdown plugins** from `MessageResponse` in `docs/components/ai-elements/message.tsx`, simplifying its markdown processing. This work combines **feature enhancement** for documentation with **maintenance** for the AI UI, improving both content reach and component efficiency.

This commit delivers a **documentation update** by **enhancing the metadata of documentation pages** within `apps/docs` to include alternate markdown links, improving SEO and navigation. Simultaneously, it **refactors** the **AI message response component** (`MessageResponse`) by removing the `math` and `mermaid` plugins from its `MDXContent` rendering. This optimization streamlines the display of AI-generated content, ensuring a more focused and efficient presentation within the documentation application.

This commit delivers a comprehensive update to the **documentation platform**, encompassing new features, refactoring, and content enhancements. It introduces **SEO improvements** by generating `robots.txt` and `sitemap.xml`, and adds **markdown page request tracking** via a refactored proxy middleware. The **AI chat interface** sees significant refactoring, particularly in the `PromptInput` component for improved attachment handling and submission logic, alongside updates to message rendering and metadata display. Furthermore, the **documentation content** is enriched with new frontmatter properties, supported by an **extended frontmatter schema** and an enhanced `getLLMText` function for better LLM integration. Minor styling adjustments and a **hydration mismatch fix** in the `ThemeToggle` component round out these improvements.