chore(blog): add October community summary #4512
Conversation
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including You can disable this status message by setting the WalkthroughAdds a new adopters JSON dataset, creates an October 2025 community summary blog post, removes Changes
Sequence Diagram(s)(Skipped — changes are content/data additions and metadata edits; no control-flow or runtime behavior modified.) Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (2 passed)
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. Comment |
thulieblack
requested review from
Mayaleeeee,
TRohit20,
akshatnema,
anshgoyalevil,
asyncapi-bot-eve,
derberg and
sambhavgupta0705
as code owners
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4512--asyncapi-website.netlify.app/ |
|
@derberg your review, missed anything? |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
config/adopters.json (1)
1-1: Valid JSON structure; consider pretty-printing for maintainability.The adopter data is correctly structured with consistent schema across 14 records. However, the minified single-line format makes git diffs harder to review and complicates future maintenance. Consider reformatting with indentation, especially if this file is frequently updated.
Example format:
[ { "companyName": "Reiffeisen Bank", "useCase": "...", "resources": [ { "title": "...", "link": "..." } ] }, ... ]
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (4)
config/adopters.json(1 hunks)markdown/blog/2025-october-summary.md(1 hunks)markdown/blog/2025-september-summary.md(0 hunks)next-env.d.ts(1 hunks)
💤 Files with no reviewable changes (1)
- markdown/blog/2025-september-summary.md
🧰 Additional context used
🧠 Learnings (5)
📓 Common learnings
Learnt from: iambami
Repo: asyncapi/website PR: 4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
📚 Learning: 2025-04-20T16:05:16.482Z
Learnt from: anshgoyalevil
Repo: asyncapi/website PR: 3950
File: scripts/utils/check-locales.ts:122-129
Timestamp: 2025-04-20T16:05:16.482Z
Learning: In the AsyncAPI website project, Next.js throws errors at runtime when locale files are missing, making additional validation for missing files unnecessary in the check-locales script.
Applied to files:
next-env.d.ts
📚 Learning: 2025-01-18T08:44:43.614Z
Learnt from: akshatnema
Repo: asyncapi/website PR: 3423
File: tests/index.test.js:2-7
Timestamp: 2025-01-18T08:44:43.614Z
Learning: In the AsyncAPI website project, JavaScript test files must include the .ts extension when importing TypeScript files (e.g., `require('../scripts/build-rss.ts')`). This is enforced by the project's configuration which uses `moduleResolution: "bundler"` in tsconfig.json and TypeScript-aware ESLint plugins. The .ts extensions are required even though the files are imported using CommonJS require statements.
Applied to files:
next-env.d.ts
📚 Learning: 2025-01-18T08:44:43.614Z
Learnt from: akshatnema
Repo: asyncapi/website PR: 3423
File: tests/index.test.js:2-7
Timestamp: 2025-01-18T08:44:43.614Z
Learning: In the AsyncAPI website project, JavaScript test files must include the .ts extension when importing TypeScript files (e.g., `require('../scripts/build-rss.ts')`). This is a project-specific requirement enforced by the linting rules and build setup, even though it differs from typical Node.js behavior.
Applied to files:
next-env.d.ts
📚 Learning: 2025-06-03T06:48:09.304Z
Learnt from: iambami
Repo: asyncapi/website PR: 4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Applied to files:
markdown/blog/2025-october-summary.md
🔇 Additional comments (5)
next-env.d.ts (1)
1-7: Standard Next.js TypeScript setup—approved.The triple-slash directives and reference path are correctly configured for Next.js TypeScript integration. No changes required.
markdown/blog/2025-october-summary.md (4)
1-15: Frontmatter is well-structured; date correctly reflects publication date per community guidelines.The frontmatter includes all required fields (title, date, type, tags, cover, author, excerpt, featured). The publication date of November 5th for an October summary aligns with AsyncAPI's documented practice of dating posts by actual publication date rather than the month being covered. Based on learnings from prior community spotlights.
17-56: Content sections are comprehensive and well-organized; links are descriptive.The blog post covers all major October events (Bangalore and Online conferences), upcoming initiatives (Paris, Developer Week 2026), and community highlights. Sponsorship acknowledgments and volunteer recognition are appropriately included. External links are contextualized with descriptive anchor text, improving SEO and user experience.
31-35: Verify<Figure>component is properly defined and accepts these props.The component is used with props
src,caption, andclassName. Ensure the component definition exists in the codebase and accepts these exact prop names.
73-79: Verify<Profiles>component accepts theprofilesarray structure.The component is called with a
profilesprop containing objects withname,avatar, andlinkfields. Ensure the component definition accepts this array structure and renders profiles correctly. Additionally, confirm that GitHub avatar URLs (e.g.,https://avatars.githubusercontent.com/...) are handled correctly if the component applies image optimization or CDN rewriting.Also applies to: 85-132
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
markdown/blog/2025-october-summary.md (1)
29-29: Optional: Consider refining word choices for formality and conciseness.LanguageTool suggests minor style improvements in your blog post:
- Lines 29, 37, 83: "amazing" is used frequently; consider varying with alternatives like "exceptional," "remarkable," or "memorable" for a more formal tone
- Line 50: "a variety of topics" could be more concise as "varied topics" or "diverse topics"
These are optional refinements to enhance the post's polish, especially if it's a featured piece.
Also applies to: 37-37, 50-50, 83-83
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
markdown/blog/2025-october-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-11-03T08:14:22.695Z
Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.695Z
Learning: In AsyncAPI community blog posts, specifically for conference recaps, the phrase "building boats" is used intentionally and is not a typo. This appeared in the October 2025 community summary blog post (markdown/blog/2025-october-summary.md) in the context of networking at the API Standards booth.
Applied to files:
markdown/blog/2025-october-summary.md
📚 Learning: 2025-06-03T06:48:09.304Z
Learnt from: iambami
Repo: asyncapi/website PR: 4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Applied to files:
markdown/blog/2025-october-summary.md
🪛 LanguageTool
markdown/blog/2025-october-summary.md
[style] ~29-~29: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...had taken place two years prior. It was an amazing experience to finally put faces to the ...
(AWESOME)
[style] ~37-~37: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...className="text-center" /> We also had amazing conversations at the API Standards bo...
(AWESOME)
[style] ~50-~50: Consider using a more concise synonym.
Context: ...e is an exciting lineup of speakers and a variety of topics being covered; [be sure to check...
(A_VARIETY_OF)
[style] ~83-~83: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...would like to highlight and thank these amazing volunteers who dedicated their skills a...
(AWESOME)
🔇 Additional comments (2)
markdown/blog/2025-october-summary.md (2)
1-19: Frontmatter structure and content publication date look good.The November 5th publication date is correct for an October summary per established patterns. Metadata is complete and properly formatted.
21-67: Content sections are well-organized and comprehensive.Conference recaps, community goals, and spec updates are clearly structured with appropriate links and references. The link to
https://api.asyncapi.com/v1/help(line 66) properly addresses previous feedback.
There was a problem hiding this comment.
Just a few minor ones.
It was a pleasure to read it. Thank you @thulieblack !
|
|
||
| ## AsyncAPI Conferences 2025 | ||
|
|
||
| The AsyncAPI Conference this year couldn't have been a major success without the support of our event financial sponsors. We were able to cover most of the logistical aspects that come with conference planning, such as supporting travels, printing cheat sheets for the booth, and shipping swags through their support. |
There was a problem hiding this comment.
I feel like this sound a bit better
| The AsyncAPI Conference this year couldn't have been a major success without the support of our event financial sponsors. We were able to cover most of the logistical aspects that come with conference planning, such as supporting travels, printing cheat sheets for the booth, and shipping swags through their support. | |
| The AsyncAPI Conference this year couldn't have been a major success without the support of our event financial sponsors. Through their support, we were able to cover most of the logistical aspects that come with conference planning, such as supporting travels, printing cheat sheets for the booth, and shipping swags . |
|
|
||
| We also had amazing conversations at the `API Standards` booth, together with our friends from JSON Schema, who were also present with us. It was a great time of networking and building boats! | ||
|
|
||
| [Recordings from the conference are now available on YouTube; head over and watch](https://conference.asyncapi.com/venue/Bangalore#recordings). |
There was a problem hiding this comment.
| [Recordings from the conference are now available on YouTube; head over and watch](https://conference.asyncapi.com/venue/Bangalore#recordings). | |
| [Recordings from the conference are now available on YouTube](https://conference.asyncapi.com/venue/Bangalore#recordings); head over and watch |
| ### Online Conference Recap | ||
| This year marked the 5th anniversary of the AsyncAPI Online Conference, and it was interesting to see how much the community has grown. We had attendees and speakers engage with us during the conference, and we garnered over **350 views** from YouTube. | ||
|
|
||
| The event wouldn't have been a success without our volunteers, who worked on various aspects, from design to on-stage and off-stage support, and the speakers who took the time to share their knowledge. [If you missed the conference, you can watch the recorded sessions](https://www.youtube.com/watch?v=KbT7Pw6j46E). |
There was a problem hiding this comment.
| The event wouldn't have been a success without our volunteers, who worked on various aspects, from design to on-stage and off-stage support, and the speakers who took the time to share their knowledge. [If you missed the conference, you can watch the recorded sessions](https://www.youtube.com/watch?v=KbT7Pw6j46E). | |
| The event wouldn't have been a success without our volunteers, who worked on various aspects, from design to on-stage and off-stage support, and the speakers who took the time to share their knowledge. If you missed the conference, you can [watch the recorded sessions](https://www.youtube.com/watch?v=KbT7Pw6j46E). |
|
|
||
|
|
||
| ### Paris | ||
| We are heading to Paris **on December 11th** for the AsyncAPI track, and preparations are underway. There is an exciting lineup of speakers and a variety of topics being covered; [be sure to check the agenda once it's out in the coming week](https://conference.asyncapi.com/venue/Paris). |
There was a problem hiding this comment.
| We are heading to Paris **on December 11th** for the AsyncAPI track, and preparations are underway. There is an exciting lineup of speakers and a variety of topics being covered; [be sure to check the agenda once it's out in the coming week](https://conference.asyncapi.com/venue/Paris). | |
| We are heading to Paris **on December 11th** for the AsyncAPI track, and preparations are underway. There is an exciting lineup of speakers and a variety of topics being covered; [be sure to check the agenda](https://conference.asyncapi.com/venue/Paris) once it's out in the coming week |
| ### Paris | ||
| We are heading to Paris **on December 11th** for the AsyncAPI track, and preparations are underway. There is an exciting lineup of speakers and a variety of topics being covered; [be sure to check the agenda once it's out in the coming week](https://conference.asyncapi.com/venue/Paris). | ||
|
|
||
| [We still have free tickets and discounts available. Be sure also to grab one before they run out!](https://ticket.apidays.global/event/apidays-paris-2025/3cccd07f-acb2-466e-8d91-cb1f208ecf42/asyncapi-conference-at-apidays-paris-2025/cart?coupon=ASYNCAPIVIP) |
There was a problem hiding this comment.
| [We still have free tickets and discounts available. Be sure also to grab one before they run out!](https://ticket.apidays.global/event/apidays-paris-2025/3cccd07f-acb2-466e-8d91-cb1f208ecf42/asyncapi-conference-at-apidays-paris-2025/cart?coupon=ASYNCAPIVIP) | |
| [We still have free tickets and discounts available](https://ticket.apidays.global/event/apidays-paris-2025/3cccd07f-acb2-466e-8d91-cb1f208ecf42/asyncapi-conference-at-apidays-paris-2025/cart?coupon=ASYNCAPIVIP). Be sure also to grab one before they run out! |
There was a problem hiding this comment.
Other than the issues @bandantonio pointed out, it looks pretty good 😊
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
markdown/blog/2025-october-summary.md (2)
29-29: Consider more formal alternatives to "amazing" for polished community communication.The word "amazing" appears in three places (lines 29, 37, 83). While appropriate for a friendly tone, more formal alternatives might strengthen the professional presentation: "remarkable experience," "engaging conversations," and "dedicated volunteers." This is a minor style polish—feel free to keep as-is if the casual tone aligns with your brand voice.
Also applies to: 37-37, 83-83
50-50: Consider condensing "a variety of topics" for conciseness.The phrase "a variety of topics being covered" could be tightened to "diverse topics being covered" or similar. Optional polish.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-october-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-11-03T08:14:22.695Z
Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.695Z
Learning: In AsyncAPI community blog posts, specifically for conference recaps, the phrase "building boats" is used intentionally and is not a typo. This appeared in the October 2025 community summary blog post (markdown/blog/2025-october-summary.md) in the context of networking at the API Standards booth.
Applied to files:
markdown/blog/2025-october-summary.md
📚 Learning: 2025-06-03T06:48:09.304Z
Learnt from: iambami
Repo: asyncapi/website PR: 4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Applied to files:
markdown/blog/2025-october-summary.md
🪛 LanguageTool
markdown/blog/2025-october-summary.md
[style] ~29-~29: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...had taken place two years prior. It was an amazing experience to finally put faces to the ...
(AWESOME)
[style] ~37-~37: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...className="text-center" /> We also had amazing conversations at the API Standards bo...
(AWESOME)
[style] ~50-~50: Consider using a more concise synonym.
Context: ...e is an exciting lineup of speakers and a variety of topics being covered; [be sure to check...
(A_VARIETY_OF)
[style] ~83-~83: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...would like to highlight and thank these amazing volunteers who dedicated their skills a...
(AWESOME)
🔇 Additional comments (3)
markdown/blog/2025-october-summary.md (3)
14-14: Verify thefeatured: truedesign intent.Both the September and October community summaries now have
featured: trueset. Confirm whether this is intentional—if only one post should be featured at a time, consider whether the October post should remain featured or if the September post should be re-featured. Based on the AI summary, the September post had this flag removed earlier.
66-66: Verify the API documentation link.Past review comments from Shurtu-gal explicitly requested changing this link to
https://api.asyncapi.com/v1/help, and you confirmed the change was made. However, the current code shows/docsinstead of/help. Please verify this is the correct endpoint for the server-api v3 documentation reference.
1-135: Excellent community update—comprehensive, well-structured, and engaging.The post covers all major October developments: both conferences (Bangalore and Online), upcoming Paris track, community goals proposal, v3 server-api support, new ambassador, and contributor recognition. The structure is clear, components are properly embedded, and calls-to-action are well-placed. Past suggestions from bandantonio appear to have been successfully incorporated.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
markdown/blog/2025-october-summary.md (1)
29-29: Consider more formal language for optional style polish.Static analysis suggests these optional style refinements for professional tone:
- Line 29: "amazing experience" → consider "rewarding experience" or "invaluable experience"
- Line 37: "amazing conversations" → consider "meaningful conversations" or "valuable conversations"
- Line 50: "a variety of topics being covered" → consider "diverse topics being covered"
- Line 93: "amazing volunteers" → consider "dedicated volunteers" or "exceptional volunteers"
These are minor and optional improvements; incorporate only if you'd like to elevate the formality of the post.
Also applies to: 37-37, 50-50, 93-93
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-october-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-11-03T08:14:22.695Z
Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.695Z
Learning: In AsyncAPI community blog posts, specifically for conference recaps, the phrase "building boats" is used intentionally and is not a typo. This appeared in the October 2025 community summary blog post (markdown/blog/2025-october-summary.md) in the context of networking at the API Standards booth.
Applied to files:
markdown/blog/2025-october-summary.md
📚 Learning: 2025-06-03T06:48:09.304Z
Learnt from: iambami
Repo: asyncapi/website PR: 4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Applied to files:
markdown/blog/2025-october-summary.md
🪛 LanguageTool
markdown/blog/2025-october-summary.md
[style] ~29-~29: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...had taken place two years prior. It was an amazing experience to finally put faces to the ...
(AWESOME)
[style] ~37-~37: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...className="text-center" /> We also had amazing conversations at the API Standards bo...
(AWESOME)
[style] ~50-~50: Consider using a more concise synonym.
Context: ...e is an exciting lineup of speakers and a variety of topics being covered; [be sure to check...
(A_VARIETY_OF)
[style] ~93-~93: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...would like to highlight and thank these amazing volunteers who dedicated their skills a...
(AWESOME)
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
🔇 Additional comments (4)
markdown/blog/2025-october-summary.md (4)
1-15: Frontmatter structure looks good; date follows publication-date convention.The frontmatter is properly structured with all required fields, and the publication date (2025-11-05) correctly follows the practice of using actual publication date rather than the content month, consistent with prior community blog posts.
66-66: Verify API endpoint link matches previous feedback.Line 66 references
https://api.asyncapi.com/v1/docs, but a previous review comment from Shurtu-gal requested changing a link tohttps://api.asyncapi.com/v1/help. Please confirm this is the correct endpoint or if it should be updated to/helpper that earlier feedback.
37-37: "Building boats" phrase is intentional—no action needed.Per prior clarification in this PR, the phrase "building boats" on line 37 is intentional and not a typo. The post is approved as-is regarding this phrasing.
17-145: Content structure, links, and embedded components look solid.The post is well-organized across all sections (conferences, community goals, spec updates, TSC/Ambassadors, Hall of Fame, and coming events). JSX components (
<Figure>,<Profiles>) are used appropriately, links are current, and the overall tone and flow align with the AsyncAPI community blog style.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
markdown/blog/2025-october-summary.md (1)
37-37: Optional: Vary word choices for stronger prose.LanguageTool flags a few stylistic opportunities:
- Lines 37, 45, 101: "Amazing" appears three times. Consider substituting with more formal or varied alternatives like "remarkable," "exceptional," or "impressive" depending on context.
- Line 58: "A variety of topics" could be more concise as "diverse topics" or simply "various topics."
These are minor refinements and won't affect clarity, but they can elevate the formality and precision of the post.
Also applies to: 45-45, 58-58, 101-101
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2025-october-summary.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-11-03T08:14:22.695Z
Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.695Z
Learning: In AsyncAPI community blog posts, specifically for conference recaps, the phrase "building boats" is used intentionally and is not a typo. This appeared in the October 2025 community summary blog post (markdown/blog/2025-october-summary.md) in the context of networking at the API Standards booth.
Applied to files:
markdown/blog/2025-october-summary.md
📚 Learning: 2025-06-03T06:48:09.304Z
Learnt from: iambami
Repo: asyncapi/website PR: 4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
Applied to files:
markdown/blog/2025-october-summary.md
🪛 LanguageTool
markdown/blog/2025-october-summary.md
[style] ~37-~37: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...had taken place two years prior. It was an amazing experience to finally put faces to the ...
(AWESOME)
[style] ~45-~45: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...className="text-center" /> We also had amazing conversations at the API Standards bo...
(AWESOME)
[style] ~58-~58: Consider using a more concise synonym.
Context: ...e is an exciting lineup of speakers and a variety of topics being covered; [be sure to check...
(A_VARIETY_OF)
[style] ~101-~101: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...would like to highlight and thank these amazing volunteers who dedicated their skills a...
(AWESOME)
🔇 Additional comments (2)
markdown/blog/2025-october-summary.md (2)
1-154: Overall: Strong community update with clear structure and engaging content.The October summary is well-organized, celebrates key achievements (Bangalore and Online conferences, new ambassadors/TSC member), and includes concrete calls-to-action (Paris tickets, Developer Week CFP, community goals review). The frontmatter is correct with the publication date set to November 5, 2025, which aligns with standard practice for monthly summaries. Interactive components (Figure, Profiles) are used effectively. The intentional phrase "building boats" at line 45 is confirmed from prior review and adds character to the networking section.
74-74: The review comment incorrectly flags the current URL endpoint.The current code at line 74 shows
https://api.asyncapi.com/v1/docs, which is the correct and standard AsyncAPI documentation endpoint. /docs serves the API's AsyncAPI document or rendered documentation, while /help is not defined by the AsyncAPI spec and would be an application-specific endpoint.Additionally, no evidence of the past review conversation cited in the comment (requesting a change to
/helpwith a "Done" acknowledgment) could be found in the repository or PR history. The current code is correct as-is.Likely an incorrect or invalid review comment.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4512 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 780 780
Branches 144 144
=========================================
Hits 780 780 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@derberg @TRohit20 @bandantonio your final review and approvals please and thank you |
5 participants
Community summary for the month of October
Summary by CodeRabbit
New Features
Bug Fixes / Content
Chores