Skip to content

docs: add monthly release notes #4358

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Conversation

mldangelo
Copy link
Member

No description provided.

mldangelo added 3 commits June 6, 2025 10:53
- Add dedicated release notes blog at /releases/ route

- Configure Docusaurus blog plugin for release notes

- Add navigation links in navbar and footer

- Include comprehensive monthly roundups for March, April, and May 2025

- Set up RSS feed and SEO optimization for release notes

- Add author configuration and publishing guidelines
@mldangelo mldangelo requested a review from ladyofcode June 6, 2025 18:37
@mldangelo mldangelo requested a review from Copilot June 6, 2025 18:52
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR sets up the infrastructure and guidelines for monthly release roundups and adds new author metadata.

  • Introduce authors.yml to list team members eligible to author release roundups
  • Add site/releases/README.md with comprehensive guidelines for writing and structuring monthly roundups
  • Configure Docusaurus with a new “Release Notes” blog plugin and include March–May 2025 roundup posts

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
site/releases/authors.yml New author metadata for monthly release roundups
site/releases/README.md Guidelines for naming, structure, tone, and publishing process
site/releases/2025-03-31-march-roundup.md Added March 2025 roundup
site/releases/2025-04-30-april-roundup.md Added April 2025 roundup
site/releases/2025-05-31-may-roundup.md Added May 2025 roundup
site/docusaurus.config.ts Added “Release Notes” nav links and configured blog plugin id releases
Comments suppressed due to low confidence (1)

site/releases/README.md:190

  • The '## Authors' section currently has no entries. Consider listing the available author keys and names (from authors.yml) so contributors know which IDs to use.
## Authors

name: Will Holley
title: Senior Engineer
url: https://github.com/promptfoo
image_url: /img/team/will.jpg
Copy link
Preview

Copilot AI Jun 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The file extension for Will Holley’s image is '.jpg' while others use '.jpeg'. Standardize on one extension to prevent broken image links or confusion.

Suggested change
image_url: /img/team/will.jpg
image_url: /img/team/will.jpeg

Copilot uses AI. Check for mistakes.

@mldangelo mldangelo changed the title docs: update release notes guidelines and authors docs: add monthly release notes Jun 6, 2025
@mldangelo
Copy link
Member Author

Handing this off to @ladyofcode to make it her own.

@mldangelo mldangelo marked this pull request as ready for review June 11, 2025 01:27
Copy link
Contributor

use-tusk bot commented Jun 11, 2025

⏩ No test scenarios generated (18780f6) View output ↗

View output in GitHub ↗

Tip

New to Tusk? Learn more here.

View check history

Commit Status Output Created (UTC)
18780f6 ⏩ No test scenarios generated Output Jun 11, 2025 1:27AM

Copy link
Contributor

coderabbitai bot commented Jun 11, 2025

Walkthrough

A dedicated "Release Notes" blog section was added to the Docusaurus site configuration, including navigation links in the navbar and footer. New markdown documents were introduced for March, April, and May 2025 release roundups, along with a README for release roundup authoring guidelines and an authors metadata YAML file for the release notes section.

Changes

Files/Paths Change Summary
site/docusaurus.config.ts Added a new blog plugin instance for "Release Notes" and updated navbar/footer to link to this section.
site/releases/2025-03-31-march-roundup.md Added March 2025 release roundup markdown documenting major features and improvements.
site/releases/2025-04-30-april-roundup.md Added April 2025 release roundup markdown summarizing five major releases and new features.
site/releases/2025-05-31-may-roundup.md Added May 2025 release roundup markdown covering six releases and key updates.
site/releases/README.md Added guidelines for creating monthly release roundups, including templates and best practices.
site/releases/authors.yml Introduced authors metadata YAML file listing individuals and teams for release note attribution.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /.npm/_logs/2025-06-11T01_29_02_665Z-debug-0.log

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Commit Unit Tests in branch feat/release-notes-section
  • Post Copyable Unit Tests in Comment

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

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

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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

CodeRabbit Commands (Invoked using PR comments)

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

Other keywords and placeholders

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

CodeRabbit Configuration File (.coderabbit.yaml)

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

Documentation and Community

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 6

♻️ Duplicate comments (1)
site/releases/authors.yml (1)

61-65: 🛠️ Refactor suggestion

Standardize image file extensions.

Will Holley’s image uses .jpg while all other author images use .jpeg. To prevent broken links and maintain consistency, update to .jpeg:

- image_url: /img/team/will.jpg
+ image_url: /img/team/will.jpeg
📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 61b0303 and 18780f6.

📒 Files selected for processing (6)
  • site/docusaurus.config.ts (3 hunks)
  • site/releases/2025-03-31-march-roundup.md (1 hunks)
  • site/releases/2025-04-30-april-roundup.md (1 hunks)
  • site/releases/2025-05-31-may-roundup.md (1 hunks)
  • site/releases/README.md (1 hunks)
  • site/releases/authors.yml (1 hunks)
🧰 Additional context used
🪛 LanguageTool
site/releases/README.md

[uncategorized] ~111-~111: When ‘Reference-specific’ is used as a modifier, it is usually spelled with a hyphen.
Context: ...bers for major features when relevant - Reference specific version numbers within the roundup text...

(SPECIFIC_HYPHEN)


[style] ~136-~136: This phrase is redundant (‘O’ stands for ‘Optimization’). Use simply “SEO”.
Context: ...ays" statistics ## Best Practices ### SEO Optimization - Write descriptive titles with clear ...

(ACRONYM_TAUTOLOGY)

site/releases/2025-03-31-march-roundup.md

[uncategorized] ~193-~193: A determiner appears to be missing. Consider inserting it.
Context: ...ver Environment Enhancement (v0.107.0) Server now automatically loads .env files on s...

(AI_EN_LECTOR_MISSING_DETERMINER)

site/releases/2025-04-30-april-roundup.md

[uncategorized] ~73-~73: You might be missing the article “the” here.
Context: ... ### 📋 Enhanced LLM Rubric (v0.111.0) Modified LLM Rubric now supports arbitrary objec...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)


[uncategorized] ~201-~201: Possible missing comma found.
Context: ... functionality to specific rows in eval results with automatic scroll-to-top behavior f...

(AI_HYDRA_LEO_MISSING_COMMA)

site/releases/2025-05-31-may-roundup.md

[misspelling] ~121-~121: Did you mean the verb “intend” instead of the noun ‘intent’?
Context: ...g (v0.113.2, v0.113.3) Improvements to intent grading and gender bias detection for m...

(INTENT_INTEND)


[uncategorized] ~127-~127: Possible missing comma found.
Context: ...Side Pagination (v0.113.4) Performance improvement enabling handling of thousands of eval ...

(AI_HYDRA_LEO_MISSING_COMMA)

🪛 markdownlint-cli2 (0.17.2)
site/releases/README.md

9-9: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

site/releases/2025-04-30-april-roundup.md

12-12: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)

⏰ Context from checks skipped due to timeout of 90000ms (24)
  • GitHub Check: Tusk Test Runner
  • GitHub Check: Tusk Tester
  • GitHub Check: Build Docs
  • GitHub Check: Redteam Custom Enterprise Server
  • GitHub Check: webui tests
  • GitHub Check: Run Integration Tests
  • GitHub Check: Share Test
  • GitHub Check: Test on Node 24.x and ubuntu-latest
  • GitHub Check: Test on Node 20.x and ubuntu-latest
  • GitHub Check: Test on Node 24.x and macOS-latest
  • GitHub Check: Test on Node 22.x and ubuntu-latest
  • GitHub Check: Redteam
  • GitHub Check: Test on Node 20.x and windows-latest
  • GitHub Check: Test on Node 22.x and macOS-latest
  • GitHub Check: Test on Node 20.x and macOS-latest
  • GitHub Check: Test on Node 18.x and macOS-latest
  • GitHub Check: Test on Node 18.x and windows-latest
  • GitHub Check: Test on Node 18.x and ubuntu-latest
  • GitHub Check: Build on Node 22.x
  • GitHub Check: Build on Node 24.x
  • GitHub Check: Build on Node 18.x
  • GitHub Check: Build on Node 20.x
  • GitHub Check: Style Check
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (5)
site/releases/2025-05-31-may-roundup.md (1)

1-236: Well-structured May 2025 roundup.

This document adheres to the release notes guidelines: front matter, metadata, admonitions, sections, code examples, and navigation links are all formatted correctly and consistently. No issues detected.

🧰 Tools
🪛 LanguageTool

[misspelling] ~121-~121: Did you mean the verb “intend” instead of the noun ‘intent’?
Context: ...g (v0.113.2, v0.113.3) Improvements to intent grading and gender bias detection for m...

(INTENT_INTEND)


[uncategorized] ~127-~127: Possible missing comma found.
Context: ...Side Pagination (v0.113.4) Performance improvement enabling handling of thousands of eval ...

(AI_HYDRA_LEO_MISSING_COMMA)

site/releases/2025-03-31-march-roundup.md (1)

1-191: Well-structured March 2025 roundup.

Also applies to: 196-267

site/releases/2025-04-30-april-roundup.md (1)

1-71: Well-structured April 2025 roundup.

Also applies to: 75-269

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

12-12: Multiple top-level headings in the same document
null

(MD025, single-title, single-h1)

site/releases/README.md (1)

112-112: 🧹 Nitpick (assertive)

Compound adjective needs hyphen.

Under "Link to Resources," hyphenate "Reference-specific":

- Reference specific version numbers within the roundup text
+ Reference-specific version numbers within the roundup text

Likely an incorrect or invalid review comment.

site/docusaurus.config.ts (1)

300-303: 🧹 Nitpick (assertive)

Keep footer link style consistent with navbar

Same reasoning as above – use to so Docusaurus treats the link as an internal route and keep styling consistent with the other footer items.

-            {
-              label: 'Release Notes',
-              to: '/releases/',
-            },
+            {
+              label: 'Release Notes',
+              to: '/releases/',
+            },

Likely an incorrect or invalid review comment.

Comment on lines +192 to +195
### 🌐 Server Environment Enhancement (v0.107.0)

Server now automatically loads .env files on startup:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Add missing article for clarity.

In the "Server Environment Enhancement" section, prepend "the" before ".env files" for grammatical correctness:

- Server now automatically loads .env files on startup:
+ Server now automatically loads the .env files on startup:
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### 🌐 Server Environment Enhancement (v0.107.0)
Server now automatically loads .env files on startup:
### 🌐 Server Environment Enhancement (v0.107.0)
Server now automatically loads the .env files on startup:
🧰 Tools
🪛 LanguageTool

[uncategorized] ~193-~193: A determiner appears to be missing. Consider inserting it.
Context: ...ver Environment Enhancement (v0.107.0) Server now automatically loads .env files on s...

(AI_EN_LECTOR_MISSING_DETERMINER)

🤖 Prompt for AI Agents
In site/releases/2025-03-31-march-roundup.md around lines 192 to 195, add the
article "the" before ".env files" in the sentence "Server now automatically
loads .env files on startup" to improve grammatical clarity. Change the phrase
to "Server now automatically loads the .env files on startup."

Comment on lines +72 to +74
### 📋 Enhanced LLM Rubric (v0.111.0)

Modified LLM Rubric now supports arbitrary objects for flexible eval criteria:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Add definite article for clarity.

Modify the rubric intro sentence to include "The":

- Modified LLM Rubric now supports arbitrary objects for flexible eval criteria:
+ The modified LLM Rubric now supports arbitrary objects for flexible eval criteria:
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### 📋 Enhanced LLM Rubric (v0.111.0)
Modified LLM Rubric now supports arbitrary objects for flexible eval criteria:
### 📋 Enhanced LLM Rubric (v0.111.0)
The modified LLM Rubric now supports arbitrary objects for flexible eval criteria:
🧰 Tools
🪛 LanguageTool

[uncategorized] ~73-~73: You might be missing the article “the” here.
Context: ... ### 📋 Enhanced LLM Rubric (v0.111.0) Modified LLM Rubric now supports arbitrary objec...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🤖 Prompt for AI Agents
In site/releases/2025-04-30-april-roundup.md around lines 72 to 74, the
introductory sentence for the LLM Rubric section is missing the definite article
"The" at the beginning. Edit the sentence to start with "The Modified LLM Rubric
now supports arbitrary objects for flexible eval criteria:" to improve clarity.

Comment on lines +9 to +11
```
YYYY-MM-DD-month-roundup.md
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Specify language for code fence.

Add a language identifier to this code block for improved readability and lint compliance:

- ```
+ ```text
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

9-9: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
In site/releases/README.md around lines 9 to 11, the code block lacks a language
identifier, which affects readability and linting. Add the language identifier
"text" immediately after the opening triple backticks to specify the code block
language as plain text.

Comment on lines +135 to +136

### SEO Optimization
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Simplify heading for brevity.

"SEO Optimization" is redundant; consider using "SEO":

- ### SEO Optimization
+ ### SEO
🧰 Tools
🪛 LanguageTool

[style] ~136-~136: This phrase is redundant (‘O’ stands for ‘Optimization’). Use simply “SEO”.
Context: ...ays" statistics ## Best Practices ### SEO Optimization - Write descriptive titles with clear ...

(ACRONYM_TAUTOLOGY)

🤖 Prompt for AI Agents
In site/releases/README.md at lines 135 to 136, the heading "SEO Optimization"
is redundant. Change the heading to simply "SEO" to make it more concise and
clear.

Comment on lines +150 to +153
{
href: '/releases/',
label: 'Release Notes',
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick (assertive)

Prefer to over href for internal routes

Within Docusaurus config objects, to is the canonical field for internal navigation, while href is intended for external URLs.
Using href here will still work, but it bypasses Docusaurus’ internal link handling (trailing-slash normalization, baseUrl prefixing, i18n, etc.) and is easy to forget when refactoring.

-            {
-              href: '/releases/',
-              label: 'Release Notes',
-            },
+            {
+              to: '/releases/',
+              label: 'Release Notes',
+            },
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
{
href: '/releases/',
label: 'Release Notes',
},
{
to: '/releases/',
label: 'Release Notes',
},
🤖 Prompt for AI Agents
In site/docusaurus.config.ts around lines 150 to 153, replace the `href`
property with `to` for the internal route '/releases/'. This change ensures
Docusaurus handles the link correctly with features like trailing-slash
normalization and baseUrl prefixing. Update the object key from `href` to `to`
while keeping the same path string.

Comment on lines +636 to +657
[
'@docusaurus/plugin-content-blog',
{
id: 'releases',
routeBasePath: 'releases',
path: './releases',
blogTitle: 'Release Notes',
blogDescription: 'promptfoo release notes and updates',
blogSidebarCount: 10,
blogSidebarTitle: 'Recent Releases',
postsPerPage: 10,
showReadingTime: false,
feedOptions: {
type: 'all',
title: 'promptfoo Release Notes',
description: 'Stay updated with the latest promptfoo releases',
copyright: `© ${new Date().getFullYear()} promptfoo`,
language: 'en',
},
editUrl: 'https://github.com/promptfoo/promptfoo/tree/main/site',
},
],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Add authors map & tighten path resolution for the new blog instance

  1. If you intend to use the authors.yml introduced in site/releases, wire it into the plugin via authorsMapPath; otherwise author data will be ignored.
  2. Resolving the content path with path.resolve(__dirname, 'releases') is slightly safer (no chance of accidental CWD changes during builds).
-      {
-        id: 'releases',
-        routeBasePath: 'releases',
-        path: './releases',
+      {
+        id: 'releases',
+        routeBasePath: 'releases',
+        path: path.resolve(__dirname, 'releases'),
+        authorsMapPath: path.resolve(__dirname, 'releases', 'authors.yml'),

Everything else in the block looks solid (pagination, feed options, etc.).
Ensure the build can locate authors.yml after this change.


🏁 Script executed:

#!/bin/bash
# Locate authors.yml anywhere in the repository
find . -type f -name "authors.yml"

# Verify that `path` is imported in the Docusaurus config
grep -n "import path" site/docusaurus.config.ts || echo "No 'import path' found in site/docusaurus.config.ts"

Length of output: 255


Add authorsMapPath & tighten path resolution for the releases blog plugin

To wire in your authors.yml and guard against CWD changes, update site/docusaurus.config.ts as follows:

  1. At the top of the file, add the path import:
    import path from 'path';
  2. In the @docusaurus/plugin-content-blog block for id: 'releases', replace:
    - path: './releases',
    + path: path.resolve(__dirname, 'releases'),
    + authorsMapPath: path.resolve(__dirname, 'releases', 'authors.yml'),

This ensures the build will reliably locate site/releases/authors.yml during plugin initialization.

🤖 Prompt for AI Agents
In site/docusaurus.config.ts around lines 636 to 657, import the 'path' module
at the top of the file if not already imported. Then, in the
'@docusaurus/plugin-content-blog' configuration for the 'releases' blog, update
the 'path' property to use path.resolve(__dirname, 'releases') instead of a
relative string. Also, add the 'authorsMapPath' property pointing to
path.resolve(__dirname, 'releases/authors.yml') to ensure the authors.yml file
is correctly wired into the plugin. This will make the content path resolution
more robust and enable author data usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants