chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features
  • Introduced updated community discussions highlighting topics on governance and user testing engagement.
• Documentation
  • Added updated entries to showcase recent updates in community documentation.
• Chores
  • Refreshed the content board by reorganizing discussions and issue listings to better reflect current community priorities.

[coderabbitai]

Walkthrough

The pull request updates the dashboard.json file. In the hotDiscussions section, several discussion entries have been updated with changes to fields such as id, title, author, resourcePath, repo, and score. Some older entries were removed while new ones, featuring updated labels, were added. The goodFirstIssues section also saw new entries added and one removed, reflecting refreshed priorities.

Changes

File	Change Summary
dashboard.json	hotDiscussions: Updated several entries by changing id, title, author, resourcePath, repo, and score; removed outdated discussions and introduced new topics with revised labels (e.g., "Epic", "keep-open"). goodFirstIssues: Added two new issues (a bug and a docs update) and removed one obsolete feature issue.

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #3580: Involves similar modifications to the dashboard.json file, particularly within the discussion and issues sections.
• chore: update meetings.json and newsrooom_videos.json #3656: Focuses on updating entry details and scores within the dashboard.json file.
• chore: update meetings.json and newsrooom_videos.json #3688: Includes changes that update, add, and remove entries in the dashboard’s discussion and issue sections.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

• derberg
• akshatnema
• magicmatatjahu
• sambhavgupta0705
• anshgoyalevil
• Mayaleeeee
• devilkiller-ag
• asyncapi-bot-eve

Poem

I’m a rabbit with hops so light,
Pouncing through JSON changes bright,
New titles and scores wink in the code,
Old entries gone, new themes in mode.
With each refresh, my heart does dart—
A burrow of updates, a joyful art!
Hoppy code, forever smart!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2561b52 and c4b0e3c.

📒 Files selected for processing (1)

• dashboard.json (5 hunks)

⏰ Context from checks skipped due to timeout of 180000ms (5)

• GitHub Check: Redirect rules - asyncapi-website
• GitHub Check: Header rules - asyncapi-website
• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Pages changed - asyncapi-website
• GitHub Check: Lighthouse CI

🔇 Additional comments (31)

dashboard.json (31)

4-12: Review of Governance Board Entry Update:
This entry’s fields—such as "id", "title", "author", "resourcePath", "repo", and "score"—have been updated as intended to reflect the new governance board focus. Verify that these values align with downstream expectations.

---

15-45: Review of User Testing Participants Entry:
The record now uses updated values for "id", "title", "author", "resourcePath", "repo", and "score". In addition, the labels array has been enhanced (adding entries such as "Epic", "keep-open", and area-specific tags). Please confirm that these labels and values correctly match your content and routing logic.

---

57-67: Review of Historical Finance Data Feature Entry:
This record—for enabling historical finance data viewing—includes modifications to "id", "title", "author", and "resourcePath". The changes appear consistent with the new functionality.

---

91-109: Review of File References Entry:
The entry now reflects the updated details (with "isAssigned" set to true) and is intended to support file references. Please ensure this aligns with the expectations for error handling and issue tracking in the studio’s board.

---

359-373: Review of Voting Summary Bug Entry:
The entry detailing issues with isVotedInLast3Months appears well formed. Confirm that the details here and in related issue trackers consistently report the bug.

---

375-388: Review of “Return to Top Arrow” Feature Entry:
This update is straightforward. The fields and labels look appropriate for tracking a UI enhancement.

---

389-398: Review of Custom LogService Entry:
The record for creating a custom log service using Winston is updated correctly, with all expected fields present.

---

399-413: Review of Fragment Redundancy Entry:
The entry titled “A fragment with only one child is redundant” is formatted correctly. Ensure that downstream consumers (or UI components) react appropriately to this information.

---

414-428: Review of Redundant “undefined” Removal Entry:
The updated entry for removing the redundant "undefined" value appears clear and consistent with the project’s Hacktoberfest tagging.

---

429-447: Review of Ticket Section Rendering Fix Entry:
The record regarding fixing the ticket section rendering includes multiple labels and updated fields. Verify that no styling or functional conflicts arise from these changes.

---

448-462: Review of Member Spotlight Graphic Design Entry:
This entry for designing a graphic for the Member Spotlight Post is well structured and includes a design-specific label.

---

463-477: Review of “Did You Know?” Social Media Posts Entry:
The entry proposing “Did You Know?” social media posts is correctly updated. Confirm that the intended content and design guidelines are met downstream.

---

478-492: Review of AMA Session Announcement Graphic Entry:
The new entry for the “Ask Me Anything” session announcement has been added as expected. Verify that the resource path and labels are accurate.

---

493-502: Review of Mentorship Program Announcement Entry:
The record for announcing the mentorship program graphic is clear and well formatted.

---

503-512: Review of Newsletter Promo Design Entry:
The updated entry for the Newsletter Promo is consistent with the other design-related records in the file.

---

185-203: Review of Good First Issue Entry – AsyncAPI/generator Upgrade:
The record with "id": "I_kwDOFDnrNc6tHvh5" introduces a bug report about AsyncAPI/generator needing an upgrade. The labels ("bug" and "gsoc") are appropriately set. Verify that the resource path and repository are correct.

---

204-218: Review of Good First Issue Entry – Community Readme Update:
The entry [📑 Docs]: update Community Readme.md is added properly with a documentation label. Double-check that the community issue number and resource path match your tracking system.

---

219-233: Review of Good First Issue Entry – Docs Bug Report:
The new bug report concerning outdated info on /tools/generator and /tools/cli appears clear. Ensure that this issue has not been duplicated elsewhere and the labels accurately reflect a docs bug.

---

234-243: Review of Good First Issue Entry – Octokit Update:
The entry "id": "I_kwDOBW5R_c6qPG7g" for updating code to support @octokit/request v9 and @octokit/graphql v8 is well formatted. Please verify the repository and resource path are targeting the correct project.

---

244-253: Review of Good First Issue Entry – Search History Consistency:
The bug report regarding inconsistent search history behavior is clearly communicated. Confirm that the linked issue exists and is not redundant.

---

254-268: Review of Good First Issue Entry – Social Sharing Buttons Feature:
The record for introducing social sharing buttons on blogs includes the necessary enhancement label. Verify that this proposal aligns with the latest design requirements.

---

269-283: Review of Good First Issue Entry – Search Modal Transition Feature:
The new feature request to add a smooth transition to the search modal opening is clearly documented. Ensure that its impact on user experience has been evaluated.

---

284-298: Review of Good First Issue Entry – Missing server.summary() Function:
This bug report targeting the AsyncAPI/parser-js repo is complete with appropriate labeling. Confirm that this bug has not already been addressed in other parts of the system.

---

299-313: Review of Good First Issue Entry – Missing server.title() Function:
The entry reporting the absence of the server.title() function is added correctly. All fields appear consistent with project standards.

---

344-358: Review of Good First Issue Entry – Voting Summary Bug:
The record for a bug detailing errors in the voting summary (i.e. in isVotedInLast3Months) appears correctly formed.

---

359-373: Review of Good First Issue Entry – Voting Summary Error (Alternate Report):
This entry (with "id": "I_kwDODwv8N86ihL5I") also details voting summary issues. Verify whether this duplicates the previous report or if it captures a distinct aspect of the bug.

---

374-388: Review of Good First Issue Entry – Ticket Section Rendering Fix:
The issue report concerning the ticket section rendering is complete and uses dual labels ("enhancement" and "Hacktoberfest").

---

389-397: Review of Good First Issue Entry – Member Spotlight Graphic Design:
The entry for designing a graphic for the Member Spotlight Post is clearly specified and well labeled.

---

400-408: Review of Good First Issue Entry – Redundant Undefined Removal:
The record addressing the removal of a redundant "undefined" value is added correctly. Please verify that similar entries are not duplicated elsewhere.

---

414-512: Review of Design-Related Good First Issues (Multiple Entries):
The entries for design improvements—including the removal of redundant "undefined", fixing ticket section rendering, and new graphic design proposals for member spotlight, “Did You Know?” posts, and AMA session announcements—are all well structured. Ensure that they align with the intended design roadmap and that any duplicate or redundant entries are eliminated.

---

1-764: PR Objective Mismatch Notice:
The pull request summary indicates automated updates to meetings.json and newsrooom_videos.json; however, the file under review is dashboard.json. Please verify that this file is part of the intended changes for the PR.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.

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.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	c4b0e3c
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67cce24a7822b90008eac76a
😎 Deploy Preview	https://deploy-preview-3849--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (2561b52) to head (c4b0e3c).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3849   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          667       667           
  Branches       113       113           
=========================================
  Hits           667       667           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.