Weekly GitHub Report for Mermaid: February 16, 2026 - February 23, 2026 (17:35:02)
Weekly GitHub Report for Mermaid
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is @mermaid-js/parser@0.4.0
1.2 Version Information:
On March 25, 2025, a minor update was released that introduced the addition of a Radar Chart, enhancing the charting capabilities of the platform. This update reflects ongoing efforts to expand visualization options.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
[TYPE: ENHANCEMENT] [STATUS: TRIAGE] Extend until keyword to support duration for backward scheduling in Gantt charts: This issue proposes extending the
untilkeyword in Gantt charts to support duration-based backward scheduling, allowing users to specify a task duration and an end reference (either a task ID or a date) so that the start date is automatically calculated. This enhancement aims to simplify defining tasks that work backward from deadlines, such as code sprints or exam preparations, eliminating the need for manual start date calculations when deadlines shift.- The comments reveal that the feature was quickly implemented and merged, initially supporting only
duration, until <taskId>. Users requested support forduration, until <endDate>, which was then added to keep the syntax consistent. The final implementation supports both task ID and end date references, and users expressed satisfaction with the new functionality. - Number of comments this week: 13
- The comments reveal that the feature was quickly implemented and merged, initially supporting only
-
[TYPE: BUG / ERROR] [STATUS: APPROVED] [GRAPH: ARCHITECTURE] Crash with node name conflict while editing Architecture diagram: This issue describes a crash occurring in the Mermaid architecture-beta diagram feature when a junction is added to a group whose name prefix conflicts with a service name, causing the library to fail, particularly in the Mermaid Live Editor. The reporter suggests adding validation to the
addJunctionfunction similar to existing checks inaddServiceto prevent this node name conflict and ensure only group-type nodes are accepted as parents.- The comments confirm the issue and clarify the cause related to missing validation in
addJunction. A contributor added the necessary validation checks and unit tests, successfully reproducing and fixing the problem, with the fix submitted in a pull request. - Number of comments this week: 4
- The comments confirm the issue and clarify the cause related to missing validation in
Since there were fewer than 5 open issues, all of the open issues have been listed above.
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
As of our latest update, there are no stale issues for the project this week.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 3
Summarized Issues:
- Conceptual Framework and Philosophy of Science: This topic covers the proposal of a detailed conceptual diagram that outlines the philosophy of science, including its object of study, nature as a second-order knowledge, main functions, dimensions of metascientific research, and distinctions from other disciplines. The issue aims to clarify the foundational aspects and scope of philosophy of science through a structured visual representation.
- issues/7401
- Gantt Chart Scheduling Enhancements: This topic involves extending the
untilkeyword in Gantt charts to support specifying task durations for backward scheduling, allowing syntax likeduration, until <taskId | endDate>. The enhancement enables automatic calculation of task start dates based on deadlines or milestones, improving scheduling flexibility. - issues/7407
- Crash Bug in Architecture-Beta Diagram Editor: This topic addresses a crash occurring in the Mermaid architecture-beta diagram editor when adding a junction to a group with a name prefix conflicting with a service name. The conflict causes the library to fail during live preview and reopening sessions, impacting usability and stability.
- issues/7408
2.4 Closed Issues
This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.
Issues Closed This Week: 0
Summarized Issues:
As of our latest update, there were no issues closed in the project this week.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.
III. Pull Requests
3.1 Open Pull Requests
This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 8
Key Open Pull Requests
1. Bug/5741 fix duplicate svg element ids: This pull request fixes the issue of duplicate SVG element IDs across multiple Mermaid diagrams on the same page by comprehensively prefixing all internally generated SVG element IDs with each diagram’s unique SVG container ID, thereby preventing ID collisions that caused broken event handlers, missing arrow markers, and corrupted styling, and includes extensive tests and updates to rendering, CSS selectors, and click handlers to support this namespacing approach.
- URL: pull/7410
- Associated Commits: 0fe25, 0f281, c2a2b, d2205, 72455, 2773d, c41bf, 10002, f0b57, ee5e9, 9beed, 04e43, f43a6, b8ab2, e5d07, 52559, 69800, 291fe, e0b67, 8f478, 98636, 3142c, 7fb25, 28733, 58b58, 79a19, 36a9e, 9090c, b632b, 1c371, 14a60, 1326f, 107ed, 15012
2. feat(timeline): implement neo look: This pull request implements Neo look support for Timeline Diagrams by extending the Neo look styling system to timeline visualizations with modern design elements, comprehensive theming across six new themes including light and dark variants, and thorough end-to-end testing to ensure consistent and backward-compatible rendering.
- URL: pull/7406
3. Allow Gantt tasks to use "duration, until
- URL: pull/7409
Other Open Pull Requests
- Theme-aware treemap text color fixes: Multiple pull requests address the issue of hardcoded black text colors in the treemap diagram, replacing them with dynamic colors derived from the active theme's variables. These changes ensure that the treemap title, labels, and values remain readable across different themes, including dark backgrounds, while still supporting user-provided style overrides.
- [pull/7404, pull/7403]
- Documentation update with Langium parser links: One pull request updates the documentation by adding links to the Langium parser information and playground, aiming to assist contributors in understanding and using the parser more effectively.
- [pull/7402]
- Validation improvements in addJunction function: A pull request adds validation checks to the
addJunctionfunction to prevent crashes caused by invalid parent assignments, ensuring duplicate IDs, self-references, parent existence, and parent type are properly validated. This aligns the function's behavior withaddServiceandaddGroupand includes comprehensive unit and integration tests to cover these cases. - [pull/7411]
- New "neo look" feature for gitgraph component: One pull request implements a new "neo look" feature for the gitgraph component, enhancing its visual style as indicated by the commit and title.
- [pull/7413]
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 2
Key Closed Pull Requests
1. chore: Update banner with coupon: This pull request updates the promotional banner logic in the TopBar.vue component for the Mermaid Advanced Editor campaign by simplifying tagline variants, adding support for custom URL parameters like coupon codes, and enhancing the checkout URL to improve tracking and user experience.
- URL: pull/7399
2. chore: add Claude Code automation template configuration: This pull request proposes adding a Claude Code automation template configuration to the mermaid-js/mermaid project, integrating session hooks, pre-push checks, CI verification, and GitHub workflows adapted from an existing template to fit mermaid's toolchain and monorepo architecture, although it was ultimately not merged.
- URL: pull/7412
- Associated Commits: a0d87
- Associated Commits: a0d87
3.3 Pull Request Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.
IV. Contributors
4.1 Contributors
Active Contributors:
We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.
If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| lee-treehouse | 36 | 3 | 0 | 1 |
| claude | 28 | 0 | 0 | 0 |
| omkarht | 17 | 5 | 0 | 0 |
| aloisklink | 18 | 0 | 0 | 0 |
| sidharthv96 | 14 | 1 | 0 | 0 |
| darshanr0107 | 10 | 2 | 0 | 0 |
| Shahir-47 | 3 | 1 | 0 | 7 |
| alexander-turner | 6 | 2 | 0 | 0 |
| No author found | 7 | 0 | 0 | 0 |
| veeceey | 4 | 3 | 0 | 0 |