2025 august release notes #233
Conversation
chris-absmartly
requested review from
bmsilva,
calthejuggler,
marcio-absmartly and
mario-silva
as code owners
|
Caution Review failedThe pull request is closed. WalkthroughEdits are confined to documentation across multiple release notes and one web console doc. Several 2025 monthly release notes were revised for grammar, terminology, and phrasing; some sections were added or clarified (e.g., Decisions Timeline, export steps, hierarchical teams). New release notes were added for August 2025 and September 2025, detailing UX improvements, owner filter flexibility, performance tweaks, and bug fixes. The web console events doc was updated to accurately reference the ellipsis (…) menu. No code, API, or exported declarations were modified. Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 💡 Knowledge Base configuration:
You can enable these sources in your CodeRabbit configuration. 📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for absmartly-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
docs/web-console-docs/Interpreting-metrics-in-experiment-results.mdx (1)
100-108: Fix boundary label inconsistency and remove stray comma
- Line 94: change “Efficiency Boundary (Green Region)” → “Efficacy Boundary (Green Region)”
- Line 89: remove the comma after “Group Sequential Testing”
docs/platform-release-notes/2025/02.mdx (1)
12-25: Ensure feature name matches the doc page title
The page at/docs/web-console-docs/Experiment-reportsis titled “Experiment Velocity Report”, so update the release notes to read Experiment Velocity Report (Beta) instead of “Velocity Report (Beta)”.
[docs/platform-release-notes/2025/02.mdx:12-25]
🧹 Nitpick comments (19)
docs/web-console-docs/events.mdx (1)
14-15: Typo fix looks good; minor wording nit for the menu label.Consider standardising the menu name to match UI copy (e.g., “ellipsis (…) menu” or “More actions”). Optional edit below.
-... menu +ellipsis (…) menudocs/platform-release-notes/2025/05.mdx (1)
10-12: Tighten phrasing.“Most requested feature request” is redundant. Suggest:
-**View the list of experiments:** The most requested feature request for the velocity report. You can now click on any graph on the Velocity Report to get the list of experiments included. +**View the list of experiments:** Our most‑requested Velocity Report enhancement. You can now click any chart in the Velocity Report to view the underlying experiments.docs/platform-release-notes/2025/08.mdx (4)
3-5: Minor grammar polish in the Overview.-This release includes a number of small but meaningful improvements and bug fixes. While the team continues work on major backend updates coming soon, this update focuses on performance optimisations and fixes that improve clarity and usability. +This release includes a number of small but meaningful improvements and bug fixes. While the team continues to work on major backend updates, this update focuses on performance optimisations and fixes that improve clarity and usability.
11-13: Clarify scope/timeframes (optional).If feasible, specify where the 30‑day default applies (e.g., dashboards, API) and define “experiments running longer than 60 days” as “for longer than 60 days.”
-- **Feature flag**: We no longer fetch data older than 30 days by default -**Long-running experiments**: We have reduced how frequently data is updated for experiments running longer than 60 days +- **Feature flag**: By default, dashboards no longer fetch data older than 30 days +- **Long‑running experiments**: We have reduced how frequently data is updated for experiments running for longer than 60 days
20-24: Tidy phrasing and maintain product terminology.“Add to favorite fixed” reads awkwardly. Suggest:
-- **Add to favorite fixed**: We fixed an issue where adding experiments to the list of favorites did not always work. +- **Add to favourites: fixed**: Resolved an issue where adding experiments to favourites did not always work.If your house style is US English, keep “favorites” accordingly.
27-28: Tone/wording tweak.-Let us know if you have any questions or feedback — and stay tuned for bigger changes coming soon! +Please let us know if you have any questions or feedback — and stay tuned for more substantial changes coming soon.docs/platform-release-notes/2025/04.mdx (1)
5-5: Tighten grammar and formatting in the Overview sentence.
- Pluralise “improvement” → “improvements”.
- Add comma before “so”.
- Fix stray space inside bold “Velocity”.
- Ensure singular/plural consistency for “Decisions Report(s)”.
-In this new release we mainly focused on improvement to the **Velocity **and **Decisions Reports**. All those improvements are driven by feedback we received from you so keep them coming. Here are some of the most important updates. +In this release, we focused mainly on improvements to the **Velocity** and **Decisions Report**. All those improvements are driven by feedback we received from you, so keep them coming. Here are some of the most important updates.docs/platform-release-notes/2025/06.mdx (5)
10-10: Resolve comma splice and tighten phrasing.-Teams become much more than just metadata, you can now properly define and manage teams within the platform. This update allows you to map your internal organizational structure directly into the product by: +Teams are now much more than just metadata. You can properly define and manage teams within the platform. This update allows you to map your internal organisational structure directly into the product by:
24-26: Hyphenate compound modifier and minor wording.-- No need to navigate through events page or APIs -- Directly download all experiment related data with a single click +- No need to navigate through the events page or APIs +- Directly download all experiment-related data with a single click
35-35: Permission phrasing.Use singular “permission” and surface the exact permission name clearly.
-Only users with the Events:List permissions will be able to trigger the export and download the file. +Only users with the “Events:List” permission can trigger the export and download the file.
41-45: Minor style: add full stop after “vs.” and parallelism.-- Improve searchability and filtering (archived vs unarchived) +- Improve searchability and filtering (archived vs. unarchived)
56-56: Comma before coordinating “so”.-As always we value your feedback so please share with us what you would like to see improve in the future. +As always, we value your feedback, so please share with us what you would like to see improve in the future.docs/platform-release-notes/2025/03.mdx (4)
22-24: Past tense and missing word “toggle”.-- **Unique Experiments toggle:** We replace the old 'Show iterations' - toggle with a new 'Unique Experiments'. The report now defaults to +- **Unique Experiments toggle:** We replaced the old 'Show iterations' + toggle with a new 'Unique Experiments' toggle. The report now defaults to
36-41: Fix sentence fragment and ensure consistent capitalisation of report names and decisions.
- Merge the fragment beginning “While the velocity report…” into a single sentence.
- Capitalise “Velocity Report” and “Decisions Report”.
- Standardise decision names.
-While the velocity report focused on the experiments you and your -colleagues run. The decisions report focuses on the decisions you make as -a result of those experiments. Those decisions include ***Full on***, -***Keep current*** and ***Abort***. This report also includes a +While the **Velocity Report** focuses on the experiments you and your +colleagues run, the **Decisions Report** focuses on the choices you make as +a result of those experiments. Those decisions include ***Full On***, +***Keep Current***, and ***Abort***. This report also includes a
74-76: Minor tone and concision (optional).-We want to build the best possible experimentation platform for you so if -you have any thoughts on this release or on any other features please +We want to build the best possible experimentation platform for you, so if +you have any thoughts on this release or other features, please
79-83: Reduce repetition (“specific”).-In the next few weeks we will start working on improving our -**Feature Flags** capabilities and while we already have a good idea of -which problems we want to solve and which features we want to bring to -you, we want to hear what specific use cases you might have so if you have -specific needs, requirements or wishes make sure to let us know so we can -set some time to have a chat with you. +In the next few weeks, we will start improving our **Feature Flags** capabilities. While we have a good idea of the problems to solve and features to deliver, we would love to hear your use cases. If you have particular needs or requirements, let us know and we can schedule time to chat.docs/platform-release-notes/2025/07.mdx (3)
12-14: Fix prepositions and product term capitalisation.-- **Team assignments**: Get notified when you're added/removed to a team -- **Experiment/feature lifecycle updates**: Get alerts when an experiment starts, stops, is put full-on or when a feature is turned on/off. +- **Team assignments**: Get notified when you're added to or removed from a team +- **Experiment/feature lifecycle updates**: Get alerts when an experiment starts, stops, is put Full On, or when a feature is turned on/off.
28-31: Capitalisation consistency for “Impact per Day”.-- Display impact per day for all relevant metrics +- Display **Impact per Day** for all relevant metrics
37-37: Polish closing sentence (optional).-Let us know if you have any questions or if you would like to discuss future features with us. +Please let us know if you have any questions or would like to discuss future features with us.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (9)
docs/platform-release-notes/2025/02.mdx(3 hunks)docs/platform-release-notes/2025/03.mdx(4 hunks)docs/platform-release-notes/2025/04.mdx(2 hunks)docs/platform-release-notes/2025/05.mdx(1 hunks)docs/platform-release-notes/2025/06.mdx(3 hunks)docs/platform-release-notes/2025/07.mdx(1 hunks)docs/platform-release-notes/2025/08.mdx(1 hunks)docs/web-console-docs/Interpreting-metrics-in-experiment-results.mdx(1 hunks)docs/web-console-docs/events.mdx(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/platform-release-notes/2025/07.mdx
[uncategorized] ~10-~10: It appears that hyphens are missing in the adjective “up-to-date”.
Context: ...tification system ensures you're always up to date with what's happening on the platform. ...
(UP_TO_DATE_HYPHEN)
[style] ~36-~36: Consider using polite language here.
Context: ...hen reviewing experiment results. --- Let us know if you have any questions or if you wou...
(INSERT_PLEASE)
docs/platform-release-notes/2025/08.mdx
[uncategorized] ~4-~4: Possible missing preposition found.
Context: ...and bug fixes. While the team continues work on major backend updates coming soon, t...
(AI_HYDRA_LEO_MISSING_TO)
[style] ~23-~23: Consider using a different verb for a more formal wording.
Context: ...reshed. - Add to favorite fixed: We fixed an issue where adding experiments to th...
(FIX_RESOLVE)
[style] ~26-~26: Consider using polite language here.
Context: ...of favorites did not always work. --- Let us know if you have any questions or feedback —...
(INSERT_PLEASE)
[style] ~27-~27: The word ‘bigger’ tends to be overused. Consider an alternative.
Context: ...stions or feedback — and stay tuned for bigger changes coming soon!
(BIG_DIFFERENCE)
docs/platform-release-notes/2025/04.mdx
[typographical] ~5-~5: It appears that a comma is missing.
Context: ... April 2025 ## Overview In this new release we mainly focused on improvement to the...
(DURING_THAT_TIME_COMMA)
[uncategorized] ~5-~5: Possible missing comma found.
Context: ...are driven by feedback we received from you so keep them coming. Here are some of t...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~21-~21: Possible missing comma found.
Context: ... --- ## Decisions Report Earlier this month we launched the new [Decisions Reports ...
(AI_HYDRA_LEO_MISSING_COMMA)
[typographical] ~21-~21: It appears that a comma is missing.
Context: ...t-reports/#decisions-overview). In this release we are introducing a few improvements t...
(DURING_THAT_TIME_COMMA)
docs/platform-release-notes/2025/05.mdx
[uncategorized] ~11-~11: It seems likely that a singular genitive (’s) apostrophe is missing.
Context: ... - Early stop vs Early full-on: The Experiments not completed graph now shows the break...
(AI_HYDRA_LEO_APOSTROPHE_S_XS)
[typographical] ~17-~17: It appears that a comma is missing.
Context: ...yone to make quality decisions. In this release we added GST data to the metric's table...
(DURING_THAT_TIME_COMMA)
[typographical] ~20-~20: The word ‘What’ starts a question. Add a question mark (“?”) at the end of the sentence.
Context: ...artly.com](mailto:[email protected]). --- ## Feedback and Next Steps As al...
(WP_APOSTROPHE_VERB_QUESTION_MARK)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: Redirect rules - absmartly-docs
- GitHub Check: Header rules - absmartly-docs
- GitHub Check: Pages changed - absmartly-docs
- GitHub Check: Yarn Build
🔇 Additional comments (2)
docs/platform-release-notes/2025/05.mdx (1)
19-21: Confirm UI label casing.Double‑check the exact button text in the product (“Load new UI” vs “Load New UI”), and mirror it here for consistency.
docs/platform-release-notes/2025/04.mdx (1)
21-24: Fix punctuation, remove stray bold marker and correct link case
- Add a comma after “In this release”.
- Remove the trailing
**after “decision.”- Update the health-checks link to lowercase:
/docs/web-console-docs/experiment-health-checks
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (1)
docs/platform-release-notes/2025/07.mdx (1)
20-21: Fix number agreement and placement for “Impact per Day”.Pluralise “types”, remove “a”, and move the prepositional phrase.
-We've added a new **Impact per Day estimates** on all relevant metric type inside the experiment overview to help you better understand the real-world significance of your experiment results. +We've added new **Impact per Day** estimates to all relevant metric types in the experiment overview to help you better understand the real‑world significance of your experiment results.
🧹 Nitpick comments (17)
docs/platform-release-notes/2025/08.mdx (3)
10-13: Tighten the opening sentence and align “Owner” terminology/punctuation.The sentence reads awkwardly and the bullet punctuation is inconsistent. Suggest rewording and using “Owner filter” consistently.
- Managing ownership is now easier and more consistent across the platform and allowing us to improve in the future who has access to what: -- An owner can now be either a single user or a team -- The Owner field now accepts both single users and teams when filtering, making results more inclusive. + Managing ownership is now easier and more consistent across the platform, enabling future improvements to access control: + - An owner can now be a single user or a team. + - The Owner filter now accepts both users and teams when filtering, making results more inclusive.
18-18: Use active wording for the refresh trigger.“is changed” → “changes”.
- - **MDE and Max Runtime Automatic Estimation Refresh**: Estimates now update automatically when the standard deviation is changed. We also improved our estimation precision. + - **MDE and Max Runtime Automatic Estimation Refresh**: Estimates now update automatically when the standard deviation changes. We have also improved estimation precision.
24-24: Slightly more polite closing.Add “Please”.
- Let us know if you have any questions or feedback — we're always happy to hear from you. + Please let us know if you have any questions or feedback — we're always happy to hear from you.docs/platform-release-notes/2025/05.mdx (2)
10-10: Streamline the bullet for flow.Merge the fragment into one sentence after the colon.
- - **View the list of experiments:** Our most‑requested Velocity Report enhancement. You can now click any chart in the Velocity Report to view the underlying experiments. + - **View the list of experiments:** Our most‑requested Velocity Report enhancement: you can now click any chart in the Velocity Report to view the underlying experiments.
21-21: Add commas for readability.Insert commas after the introductory clauses.
-Earlier this month we launched the new [Decisions Reports (Beta)](/docs/web-console-docs/experiment-reports/#decisions-overview). In this release we are introducing a few improvements to provide better insights into each decision. +Earlier this month, we launched the new [Decisions Reports (Beta)](/docs/web-console-docs/experiment-reports/#decisions-overview). In this release, we are introducing a few improvements to provide better insights into each decision.docs/platform-release-notes/2025/09.mdx (2)
19-19: Punctuation after “e.g.”Add a comma after “e.g.” per style guides.
- - **Table sorting restored**: Sorting on list tables (e.g. experiments, metrics) has been re-enabled after being unintentionally removed in a previous release + - **Table sorting restored**: Sorting on list tables (e.g., experiments, metrics) has been re‑enabled after being unintentionally removed in a previous release
26-26: Polish the closing sentence.Slightly more formal and specific.
-Let us know if you have any questions or feedback — and stay tuned for bigger changes coming soon! +Please let us know if you have any questions or feedback — and stay tuned for more significant changes coming soon!docs/platform-release-notes/2025/04.mdx (2)
5-5: Tighten wording and avoid repetition.Minor style polish.
-In this release, we focused mainly on improvements to the **Velocity** and **Decisions Report**. All those improvements are driven by feedback we received from you, so keep them coming. Here are some of the most important updates. +In this release, we focused mainly on improvements to the **Velocity** and **Decisions Report**. These improvements are driven by your feedback—keep it coming. Here are some of the most important updates.
21-21: Add commas after introductory clauses.Improves readability.
-Earlier this month we launched the new [Decisions Reports (Beta)](/docs/web-console-docs/experiment-reports/#decisions-overview). In this release we are introducing a few improvements to provide better insights into each decision. +Earlier this month, we launched the new [Decisions Reports (Beta)](/docs/web-console-docs/experiment-reports/#decisions-overview). In this release, we are introducing a few improvements to provide better insights into each decision.docs/platform-release-notes/2025/06.mdx (5)
3-4: Tidy up heading spacing and keep style consistent.Remove the trailing double spaces after the “## Overview” heading. Also confirm we’re standardising on en‑GB throughout the release notes (matches “organisational” below).
-## Overview·· +## Overview
10-16: Team Management wording and link naming.
- “organisational” is fine for en‑GB; just ensure this spelling is consistent across all 2025 notes.
- Consider replacing “wiki page” with “documentation page” unless the destination is truly a wiki.
-Check our [wiki page](/docs/web-console-docs/creating-and-managing-teams) for more information +See our [documentation page](/docs/web-console-docs/creating-and-managing-teams) for more information
22-26: UI term capitalisation and parallel bullet style.Capitalise named pages/features and keep bullets parallel.
-- No need to navigate through the events page or APIs - - Directly download all experiment-related data with a single click +- No need to navigate through the Events page or APIs +- Directly download all experiment data with a single click
30-33: Step copy: concise phrasing and consistent UI styling.Use bold for UI labels (matches “Export data” earlier) and tighten phrasing. Also consider capitalising page names.
-- Click on `...` and select `Export data`. -- You will get a confirmation that the request is in progress. The process might take a while depending on the size of the experiment. -- You will get a notification on the experiment activity page once the export file is ready. - - The export file will be available for 30 days once it has been created. +- Click the … menu and select **Export data**. +- You’ll receive a confirmation that the request is in progress. Processing time depends on the experiment size. +- You’ll receive a notification on the Experiment Activity page once the export file is ready. +- The export file will be available for 30 days after it’s created.
35-36: Permission name formatting and accuracy.Format permission names as code and please verify the exact permission key and scope.
-Only users with the “Events:List” permission can trigger the export and download the file. +Only users with the `Events:List` permission can trigger the export and download the file.Would you like me to scan the docs to ensure this permission name is used consistently?
docs/platform-release-notes/2025/03.mdx (3)
33-38: Singular/plural consistency for Decisions Report.Use singular “Decisions Report (Beta)” to match surrounding text.
-[Decisions Reports (Beta)](/docs/web-console-docs/experiment-reports/#decisions-overview). +[Decisions Report (Beta)](/docs/web-console-docs/experiment-reports/#decisions-overview).Please also verify the anchor
#decisions-overviewstill resolves after recent docs changes.
64-66: UI label styling and currency of the toggle.Style the alert text as UI and confirm it still appears in current builds.
- will have a *'Load new UI' alert* which will enable you to toggle + will have a **Load new UI** alert that enables you to toggle
74-80: Polish closing copy; add “please” and tighten phrasing.Minor tone/grammar tweaks per LanguageTool hint.
-We want to build the best possible experimentation platform for you, so if -you have any thoughts on this release or other features, please +We want to build the best possible experimentation platform for you. If +you have thoughts on this release or other features, please let us know @@ -In the next few weeks, we will start improving our **Feature Flags** capabilities. While we have a good idea of the problems to solve and features to deliver, we would love to hear your use cases. -If you have particular needs or requirements, let us know and we can schedule time to chat. +In the next few weeks, we will start improving our **Feature Flags** capabilities. While we have a good idea of the problems to solve and features to deliver, we’d love to hear your use cases. +If you have particular needs or requirements, please let us know and we can schedule time to chat.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (8)
docs/platform-release-notes/2025/03.mdx(4 hunks)docs/platform-release-notes/2025/04.mdx(2 hunks)docs/platform-release-notes/2025/05.mdx(1 hunks)docs/platform-release-notes/2025/06.mdx(2 hunks)docs/platform-release-notes/2025/07.mdx(1 hunks)docs/platform-release-notes/2025/08.mdx(1 hunks)docs/platform-release-notes/2025/09.mdx(1 hunks)docs/web-console-docs/events.mdx(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- docs/web-console-docs/events.mdx
🧰 Additional context used
🪛 LanguageTool
docs/platform-release-notes/2025/09.mdx
[style] ~4-~4: Would you like to use the Oxford spelling “optimizations”? The spelling ‘optimisations’ is also correct.
Context: ...tes, this update focuses on performance optimisations and fixes that improve clarity and usab...
(OXFORD_SPELLING_Z_NOT_S)
[style] ~25-~25: Consider using polite language here.
Context: ...o favourites did not always work. --- Let us know if you have any questions or feedback —...
(INSERT_PLEASE)
[style] ~26-~26: The word ‘bigger’ tends to be overused. Consider an alternative.
Context: ...stions or feedback — and stay tuned for bigger changes coming soon!
(BIG_DIFFERENCE)
docs/platform-release-notes/2025/08.mdx
[style] ~23-~23: Consider using polite language here.
Context: ...he minimum time between analyses. --- Let us know if you have any questions or feedback —...
(INSERT_PLEASE)
docs/platform-release-notes/2025/06.mdx
[style] ~10-~10: Would you like to use the Oxford spelling “organizational”? The spelling ‘organisational’ is also correct.
Context: ... update allows you to map your internal organisational structure directly into the product by:...
(OXFORD_SPELLING_Z_NOT_S)
docs/platform-release-notes/2025/03.mdx
[style] ~79-~79: Consider using polite language here.
Context: ... have particular needs or requirements, let us know and we can schedule time to chat.
(INSERT_PLEASE)
docs/platform-release-notes/2025/04.mdx
[uncategorized] ~21-~21: Possible missing comma found.
Context: ... --- ## Decisions Report Earlier this month we launched the new [Decisions Reports ...
(AI_HYDRA_LEO_MISSING_COMMA)
[typographical] ~21-~21: It appears that a comma is missing.
Context: ...t-reports/#decisions-overview). In this release we are introducing a few improvements t...
(DURING_THAT_TIME_COMMA)
docs/platform-release-notes/2025/05.mdx
[uncategorized] ~11-~11: It seems likely that a singular genitive (’s) apostrophe is missing.
Context: ... - Early stop vs Early full-on: The Experiments not completed graph now shows the break...
(AI_HYDRA_LEO_APOSTROPHE_S_XS)
[typographical] ~17-~17: It appears that a comma is missing.
Context: ...yone to make quality decisions. In this release we added GST data to the metric's table...
(DURING_THAT_TIME_COMMA)
[typographical] ~20-~20: The word ‘What’ starts a question. Add a question mark (“?”) at the end of the sentence.
Context: ...artly.com](mailto:[email protected]). --- ## Feedback and Next Steps As al...
(WP_APOSTROPHE_VERB_QUESTION_MARK)
docs/platform-release-notes/2025/07.mdx
[uncategorized] ~10-~10: It appears that hyphens are missing in the adjective “up-to-date”.
Context: ...tification system ensures you're always up to date with what's happening on the platform. ...
(UP_TO_DATE_HYPHEN)
| - **Unique Experiments toggle:** We replace the old 'Show iterations' | ||
| toggle with a new 'Unique Experiments'. The report now defaults to | ||
| reporting on all experiment iterations. | ||
| - **Unique Experiments toggle:** We replaced the old 'Show iterations' toggle with a new 'Unique Experiments' toggle. The report now defaults to |
There was a problem hiding this comment.
Incomplete sentence in the “Unique Experiments toggle” bullet.
The bullet ends with “defaults to” and is missing the rest of the sentence.
-- **Unique Experiments toggle:** We replaced the old 'Show iterations' toggle with a new 'Unique Experiments' toggle. The report now defaults to
+- **Unique Experiments toggle:** We replaced the old “Show iterations” toggle with a new “Unique Experiments” toggle. The report now defaults to reporting unique experiments across iterations (one row per experiment).📝 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.
| - **Unique Experiments toggle:** We replaced the old 'Show iterations' toggle with a new 'Unique Experiments' toggle. The report now defaults to | |
| **Unique Experiments toggle:** We replaced the old “Show iterations” toggle with a new “Unique Experiments” toggle. The report now defaults to reporting unique experiments across iterations (one row per experiment). |
🤖 Prompt for AI Agents
docs/platform-release-notes/2025/03.mdx around line 22: the "Unique Experiments
toggle" bullet contains an incomplete sentence ending with "defaults to";
complete the sentence by specifying what the report now defaults to (for
example: "defaults to showing only the latest run of each experiment" or the
correct project-specific behavior). Update the bullet so it reads as a full
sentence and matches the product behavior and terminology used elsewhere in the
document.
| Improve searchability and filtering (archived vs. unarchived) | ||
|
|
||
| - Improve searchability and filtering (archived vs unarchived) | ||
| - Help you quickly identify and select the metrics and goals that matter | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Duplicate/fragmented content in “Improved Metrics & Goals List Pages”.
Line 41 repeats line 43 and mixes punctuation. Remove the fragment and keep a single clear bullet.
-Improve searchability and filtering (archived vs. unarchived)
-
-- Improve searchability and filtering (archived vs unarchived)
+- Improved searchability and filtering (archived vs. unarchived)📝 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.
| Improve searchability and filtering (archived vs. unarchived) | |
| - Improve searchability and filtering (archived vs unarchived) | |
| - Help you quickly identify and select the metrics and goals that matter | |
| - Improved searchability and filtering (archived vs. unarchived) | |
| - Help you quickly identify and select the metrics and goals that matter |
🤖 Prompt for AI Agents
In docs/platform-release-notes/2025/06.mdx around lines 41 to 45, there is a
duplicated/fragmented bullet: line 41 repeats line 43 and mixes punctuation;
remove the duplicate fragment (delete the repeated "Improve searchability and
filtering (archived vs unarchived)" line), keep a single clear bullet "Improve
searchability and filtering (archived vs. unarchived)" and ensure consistent
punctuation/spacing across the bullets so the list reads cleanly.
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
docs/platform-release-notes/2025/05.mdx (1)
17-17: Fix incomplete sentence, comma, and “metric's table” phrasing.Replaces the fragment, adds the missing comma, and pluralises “metrics”.
-Our new Experiment Dashboard redesign is still in progress and you can see. The main reason behind this redesign is to consolidate how *Fixed Horizon* and *Group Sequential* experiments are shown and to make it easier for everyone to make quality decisions. In this release we added GST data to the metric's table. Please have a look and let us know what you think. +Our new Experiment Dashboard redesign is still in progress and available for preview. The main goal is to consolidate how *Fixed Horizon* and *Group Sequential* experiments are shown and to make it easier for everyone to make quality decisions. In this release, we added GST data to the metrics table. Please have a look and let us know what you think.
🧹 Nitpick comments (6)
docs/platform-release-notes/2025/05.mdx (4)
3-7: Tighten Overview phrasing.Minor clarity/style tweak.
-This release focuses on backend improvements and foundational work to support future features. While there are few visible changes for you today, these updates improve platform stability and pave the way for upcoming capabilities. We still managed to squeeze a few improvements to the Velocity report and to the Experiment Dashboard redesign. +This release focuses on backend improvements and foundational work to support future features. While there are few visible changes today, these updates improve platform stability and pave the way for upcoming capabilities. We also squeezed in a few improvements to the Velocity Report and the Experiment Dashboard redesign.
11-11: Quote the graph name and fix hyphenation/capitalisation.Improves readability and matches UI labels.
-- **Early stop vs Early full-on:** The Experiments not completed graph now shows the breakdown between the early full-on and early stops. +- **Early stop vs early full‑on:** The "Experiments not completed" graph now shows the breakdown between early full‑on and early stops.
19-20: Streamline “How to see it?” bullet and add commas.Light polish for flow.
-- **How to see it?** Within the dashboard of any existing experiment you will have a *'Load new UI'* button which will enable you to toggle between the old and the new view. +- **How to see it?** In the dashboard of any existing experiment, use the *Load new UI* button to toggle between the old and new views.
26-26: Grammar and concision in closing paragraph.Add the introductory comma, fix verb form, and tighten phrasing.
-As always we value your feedback so please share with us what you would like to see improve in the future. We have some really exciting new features coming your way in the next few releases so stay tuned. +As always, we value your feedback, so please tell us what you would like to see improved. We have exciting new features coming in the next few releases—stay tuned.docs/platform-release-notes/2025/07.mdx (1)
10-10: Hyphenate “up‑to‑date”.Standard compound adjective form.
-Never miss a key event again. Our new built-in notification system ensures you're always up to date with what's happening on the platform. +Never miss a key event again. Our new built‑in notification system ensures you're always up‑to‑date with what's happening on the platform.docs/platform-release-notes/2025/09.mdx (1)
21-21: Capitalise repeated tab name.Use “Activity tab” consistently.
-- **Caching issues on the Activity tab fixed**: We addressed some caching issues on the activity tab where data would not update until the page was refreshed. +- **Caching issues on the Activity tab fixed**: We addressed some caching issues on the Activity tab where data would not update until the page was refreshed.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (4)
docs/platform-release-notes/2025/05.mdx(1 hunks)docs/platform-release-notes/2025/07.mdx(1 hunks)docs/platform-release-notes/2025/08.mdx(1 hunks)docs/platform-release-notes/2025/09.mdx(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- docs/platform-release-notes/2025/08.mdx
🧰 Additional context used
🪛 LanguageTool
docs/platform-release-notes/2025/05.mdx
[uncategorized] ~11-~11: It seems likely that a singular genitive (’s) apostrophe is missing.
Context: ... - Early stop vs Early full-on: The Experiments not completed graph now shows the break...
(AI_HYDRA_LEO_APOSTROPHE_S_XS)
[typographical] ~17-~17: It appears that a comma is missing.
Context: ...yone to make quality decisions. In this release we added GST data to the metric's table...
(DURING_THAT_TIME_COMMA)
[typographical] ~20-~20: The word ‘What’ starts a question. Add a question mark (“?”) at the end of the sentence.
Context: ...artly.com](mailto:[email protected]). --- ## Feedback and Next Steps As al...
(WP_APOSTROPHE_VERB_QUESTION_MARK)
docs/platform-release-notes/2025/07.mdx
[uncategorized] ~10-~10: It appears that hyphens are missing in the adjective “up-to-date”.
Context: ...tification system ensures you're always up to date with what's happening on the platform. ...
(UP_TO_DATE_HYPHEN)
docs/platform-release-notes/2025/09.mdx
[style] ~4-~4: Would you like to use the Oxford spelling “optimizations”? The spelling ‘optimisations’ is also correct.
Context: ...tes, this update focuses on performance optimisations and fixes that improve clarity and usab...
(OXFORD_SPELLING_Z_NOT_S)
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
docs/platform-release-notes/2025/05.mdx (1)
17-18: Nice fix to the previously flagged sentence fragment and phrasing.The preview wording and “metrics table” correction resolve the earlier issue.
🧹 Nitpick comments (2)
docs/platform-release-notes/2025/05.mdx (2)
3-4: Polish the overview phrasing and capitalisation.Tighten wording and make “Velocity Report” capitalisation consistent.
-This release focuses on backend improvements and foundational work to support future features. While there are few visible changes for you today, these updates improve platform stability and pave the way for upcoming capabilities. We still managed to squeeze a few improvements to the Velocity report and to the Experiment Dashboard redesign. +This release focuses on backend improvements and foundational work to support future features. While there are few visible changes for you today, these updates improve platform stability and pave the way for upcoming capabilities. We still managed to ship a few improvements to the Velocity Report and the Experiment Dashboard redesign.
10-12: Tighten repetition and clarify graph name.Avoid repeating “Velocity Report” and quote the graph name; also use title case for the graph.
-- **View the list of experiments:** Our most‑requested Velocity Report enhancement: you can now click any chart in the Velocity Report to view the underlying experiments. +- **View the list of experiments:** Our most‑requested enhancement: you can now click any chart to view its underlying experiments. -**Early stop vs Early full-on:** The Experiments not completed graph now shows the breakdown between the early full-on and early stops. +**Early stop vs early full‑on:** The “Experiments Not Completed” graph now shows the breakdown between early full‑on and early stops.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
docs/platform-release-notes/2025/05.mdx(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/platform-release-notes/2025/05.mdx
[uncategorized] ~11-~11: It seems likely that a singular genitive (’s) apostrophe is missing.
Context: ... - Early stop vs Early full-on: The Experiments not completed graph now shows the break...
(AI_HYDRA_LEO_APOSTROPHE_S_XS)
[typographical] ~21-~21: The word ‘What’ starts a question. Add a question mark (“?”) at the end of the sentence.
Context: ...artly.com](mailto:[email protected]). --- ## Feedback and Next Steps As al...
(WP_APOSTROPHE_VERB_QUESTION_MARK)
🔇 Additional comments (3)
docs/platform-release-notes/2025/05.mdx (3)
6-7: Section separators look good.The horizontal rule placement reads well between sections.
13-14: Separator placement approved.Consistent with earlier sections.
23-24: Final separator LGTM.Keeps the page scannable.
calthejuggler
force-pushed
the
2025-August-release-notes
branch
from
90e0b48 to
9223fad
Compare
Co-authored-by: Cal Courtney <[email protected]>
Added August release notes
Summary by CodeRabbit