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.
bandantonio
left a comment
bandantonio
left a comment
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! |
CBID2
left a comment
CBID2
left a comment
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.
CBID2
left a comment
CBID2
left a comment
There was a problem hiding this comment.
Looks better now @thulieblack! LGTM :)
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 |
TRohit20
left a comment
TRohit20
left a comment
There was a problem hiding this comment.
LGTM!
Note: I wish someone gemini-shopped me into the images :)
|
/rtm |
commit 785c358 Author: Abhishek <abhiifour@gmail.com> Date: Fri Dec 26 18:24:01 2025 +0530 fix: horizontal scrollbar appearing in Tools flyout menu (asyncapi#4653) Co-authored-by: abhi <abhiifour@gmail.com> Co-authored-by: Prince Rajpoot <prince.rajpoot.20@gmail.com> commit 6521774 Author: DuskWarden <pawar96sameer@gmail.com> Date: Fri Dec 26 12:38:06 2025 +0530 fix: remove deprecated AddThis script and styles (asyncapi#4781) Co-authored-by: DuskWarden <pawar96sameer@gmail.com> commit a2fae36 Author: Chan <bot+chan@asyncapi.io> Date: Thu Dec 25 01:45:34 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4772) commit e917b0d Author: Chan <bot+chan@asyncapi.io> Date: Tue Dec 23 14:23:54 2025 +0100 docs(generator): update latest generator documentation (asyncapi#4719) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> commit ced4c27 Author: Chan <bot+chan@asyncapi.io> Date: Tue Dec 23 14:16:40 2025 +0100 docs(generator): update latest generator documentation (asyncapi#4718) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 6676a43 Author: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Date: Tue Dec 23 15:02:03 2025 +0200 chore(blog): add last summary (asyncapi#4699) Co-authored-by: thulieblack <sibanda.thulie@gmail.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com> commit 65c10bb Author: Vishvamsinh Vaghela <90895835+vishvamsinh28@users.noreply.github.com> Date: Mon Dec 22 10:19:06 2025 +0530 feat: replace bitly urls with netlify redirect (asyncapi#4647) Co-authored-by: Vishvamsinh Vaghela <vaghelavishvamsinh11111@gmail.com> Co-authored-by: Prince Rajpoot <prince.rajpoot.20@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> commit f604d92 Author: Chan <bot+chan@asyncapi.io> Date: Mon Dec 22 01:47:53 2025 +0100 chore: update tools.json (asyncapi#4754) commit 624747e Author: DuskWarden <pawar96sameer@gmail.com> Date: Sun Dec 21 22:35:40 2025 +0530 fix: prevent background scroll when roadmap modal is open (asyncapi#4710) Co-authored-by: DuskWarden <pawar96sameer@gmail.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> commit 52eca18 Author: Shriya Chauhan <78415084+Shriya-Chauhan@users.noreply.github.com> Date: Sun Dec 21 21:59:40 2025 +0530 fix: fixes the failing CI/CD test in .github/workflows/if-nodejs-pr-testing.yml across all platforms (asyncapi#4735) Co-authored-by: Shriya-Chauhan <auroralflower@gmail.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> commit 3a1ca24 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 19 01:45:53 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4742) commit 98637a0 Author: Chan <bot+chan@asyncapi.io> Date: Thu Dec 18 17:58:38 2025 +0100 docs(community): update latest community documentation (asyncapi#4733) commit a293c4f Author: Ashmit JaiSarita Gupta <43639341+devilkiller-ag@users.noreply.github.com> Date: Thu Dec 18 18:51:08 2025 +0530 feat: updated filters dropdown and created stories for it (asyncapi#3174) Co-authored-by: devilkiller-ag <ashmitgupta.official@gmail.com> Co-authored-by: asyncapi-bot <bot+chan@asyncapi.io> Co-authored-by: Rohit <108233235+TRohit20@users.noreply.github.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> Co-authored-by: Miles Porter <milesxporter@gmail.com> commit 1a97aff Author: Chan <bot+chan@asyncapi.io> Date: Thu Dec 18 10:23:59 2025 +0100 docs(community): update latest community documentation (asyncapi#4731) commit bc768aa Author: Chan <bot+chan@asyncapi.io> Date: Thu Dec 18 10:23:57 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4721) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 25a3892 Author: Chan <bot+chan@asyncapi.io> Date: Thu Dec 18 01:44:36 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4730) commit b927d5d Author: Chan <bot+chan@asyncapi.io> Date: Wed Dec 17 17:05:08 2025 +0100 docs(cli): update latest cli documentation (asyncapi#4728) commit 83e282a Author: Chan <bot+chan@asyncapi.io> Date: Tue Dec 16 06:03:54 2025 +0100 chore: update tools.json (asyncapi#4715) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 3c04219 Author: Chan <bot+chan@asyncapi.io> Date: Mon Dec 15 18:53:51 2025 +0100 docs(community): update latest community documentation (asyncapi#4716) commit 3d2ec88 Author: DuskWarden <pawar96sameer@gmail.com> Date: Mon Dec 15 09:46:16 2025 +0530 docs: fix broken community repository links (asyncapi#4600) Co-authored-by: DuskWarden <pawar96sameer@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Co-authored-by: Chan <bot+chan@asyncapi.io> Co-authored-by: Prince Rajpoot <prince.rajpoot.20@gmail.com> commit 9c3dcd6 Author: Chan <bot+chan@asyncapi.io> Date: Sat Dec 13 01:45:08 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4707) commit eeed68c Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 12 01:45:00 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4696) commit 1e63086 Author: Chan <bot+chan@asyncapi.io> Date: Mon Dec 8 01:47:51 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4695) commit f6d7df5 Author: Chan <bot+chan@asyncapi.io> Date: Mon Dec 8 01:47:46 2025 +0100 chore: update tools.json (asyncapi#4692) commit 0dafc8b Author: Souryavardhan singh <144201791+Sourya07@users.noreply.github.com> Date: Sun Dec 7 17:17:33 2025 +0530 fix: ensure unique TOC slugs for repeated headings(Examples) (asyncapi#4593) Co-authored-by: Sourya07 <singhsourya137@gmail.com> Co-authored-by: Sambhav Gupta <81870866+sambhavgupta0705@users.noreply.github.com> commit a056c20 Author: Varshitha Besthavemula <152318309+batchu5@users.noreply.github.com> Date: Sun Dec 7 13:47:47 2025 +0530 chore: add php, laravel and symphony in tage-color.ts (asyncapi#4667) Co-authored-by: Varshitha Besthavemula <varshithabesthavemula@gmail.com> commit a677dc6 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 17:52:47 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4665) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 4d06094 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 17:38:09 2025 +0100 docs(generator): update latest generator documentation (asyncapi#4623) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 127ac98 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 17:23:49 2025 +0100 ci: update of files from global .github repo (asyncapi#4612) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 56d5d41 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 17:15:48 2025 +0100 docs(community): update latest maintainers list (asyncapi#4666) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 3647eaa Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 17:05:44 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4679) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 962820d Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 16:58:33 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4633) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 7ad740c Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 16:20:16 2025 +0100 docs(community): update latest maintainers list (asyncapi#4678) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 222a622 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 16:06:31 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4660) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit fea45f1 Author: Prince Rajpoot <prince.rajpoot.20@gmail.com> Date: Fri Dec 5 19:55:54 2025 +0530 chore: add Prince Rajpoot as codeowner (asyncapi#4628) commit 3fc64a4 Author: Chan <bot+chan@asyncapi.io> Date: Mon Dec 1 01:52:20 2025 +0100 chore: update tools.json (asyncapi#4654) commit 5f83885 Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 30 11:11:37 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4651) commit fea633b Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 30 11:11:35 2025 +0100 docs(community): update latest maintainers list (asyncapi#4650) commit 4094d22 Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 26 11:24:47 2025 +0100 docs(generator): update latest generator documentation (asyncapi#4622) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit ad3d012 Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 26 11:00:29 2025 +0100 docs(community): update latest maintainers list (asyncapi#4626) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 40b340f Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 26 09:58:18 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4637) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 0291d0b Author: Ashish Padhy <ashishpadhy1729@gmail.com> Date: Wed Nov 26 14:18:37 2025 +0530 chore(blog): publish postmortem on recent security breach (asyncapi#4640) Co-authored-by: Shurtu-gal <ashishpadhy1729@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> commit ddc2d87 Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 25 01:41:32 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4641) commit 7accc24 Author: Chan <bot+chan@asyncapi.io> Date: Mon Nov 24 01:46:56 2025 +0100 chore: update tools.json (asyncapi#4639) commit 33db13d Author: Chan <bot+chan@asyncapi.io> Date: Sat Nov 22 01:41:38 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4635) commit d39efdf Author: Chan <bot+chan@asyncapi.io> Date: Fri Nov 21 13:56:32 2025 +0100 docs(community): update latest maintainers list (asyncapi#4620) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 85ce754 Author: Chan <bot+chan@asyncapi.io> Date: Thu Nov 20 01:42:28 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4630) commit d9e34fc Author: Prince Rajpoot <prince.rajpoot.20@gmail.com> Date: Wed Nov 19 21:24:10 2025 +0530 migrate macOS version to macos-latest (asyncapi#4625) commit e63c6c3 Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 18 08:19:29 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4610) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit d861164 Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 18 07:42:50 2025 +0100 docs(generator): update latest generator documentation (asyncapi#4611) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 47a9d92 Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 18 01:42:54 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4618) commit 7d42caf Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon Nov 17 18:00:11 2025 +0100 chore(deps-dev): bump js-yaml from 3.14.1 to 3.14.2 (asyncapi#4616) commit f0127ac Author: Chan <bot+chan@asyncapi.io> Date: Mon Nov 17 09:19:31 2025 +0100 docs(community): update latest maintainers list (asyncapi#4606) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit dbad9ab Author: Pottabathini Vivekananda <145771776+nandu-99@users.noreply.github.com> Date: Mon Nov 17 13:22:45 2025 +0530 chore: update Slack invite link (asyncapi#4597) Co-authored-by: Pottabathini Vivekananda <vivekananda.99666@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> commit 14f2093 Author: Chan <bot+chan@asyncapi.io> Date: Mon Nov 17 01:44:37 2025 +0100 chore: update tools.json (asyncapi#4609) commit 0e9faba Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 17:19:09 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4607) commit bd8cd1d Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 17:06:18 2025 +0100 docs(community): update latest maintainers list (asyncapi#4605) commit ace905f Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 16:55:27 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4604) commit 964b958 Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 16:55:23 2025 +0100 docs(community): update latest maintainers list (asyncapi#4603) commit 085e697 Author: Anushka Sharan <111284729+anushkaaaaaaaa@users.noreply.github.com> Date: Sun Nov 16 12:52:19 2025 +0530 test: add e2e tests for docs and tools pages (asyncapi#4210) * test: add e2e tests for docs and tools pages * fix: minor fixes * test: update e2e test files * test: small changes * fix: small changes * minor change * minor chabge * feat: implement base classes in e2e tests * fix: enhance link verification methods * fix: update tools data import path in E2E tests * feat: add comprehensive tools data to toolsData.json * chore: format JSON structure in docsSections.json for consistency * chore: remove Glee section from docsSections.json * chore: update tools and docs navigation methods in HomePage class * refactor: replace verifyConceptSection with goToConceptsSection for consistency * refactor: enhance page verification methods in ToolsPage * refactor: update documentation links and headings in docsSections.json * refactor: improve link verification logic in ToolsPage * Add newline at end of meetings.json Fix missing newline at end of meetings.json file. * Fix JSON formatting in newsroom_videos.json * chore: add newline at the end of BasePageTools.js * docs: add Community Travel Funding guidelines * docs: update links to AsyncAPI tool documentation * docs: add manual tools building functionality and related tests * remve line * add line * smhtg --------- Co-authored-by: Sambhav Gupta <81870866+sambhavgupta0705@users.noreply.github.com> Co-authored-by: Rohit <108233235+TRohit20@users.noreply.github.com> commit b9c3673 Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 07:06:09 2025 +0100 chore: update tools.json (asyncapi#4562) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit fe60602 Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 01:45:57 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4596) commit 9a53cfa Author: DuskWarden <pawar96sameer@gmail.com> Date: Sat Nov 15 19:58:09 2025 +0530 docs: fix broken git-workflow.md links across repository (asyncapi#4585) * docs: fix broken git-workflow.md links Updated links to point to new location after community repo restructuring * revert: remove workflow file change as it is centrally managed --------- Co-authored-by: Chan <bot+chan@asyncapi.io> commit 5bfca09 Author: Chan <bot+chan@asyncapi.io> Date: Sat Nov 15 01:43:23 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4590) commit b87dd1b Author: Chan <bot+chan@asyncapi.io> Date: Fri Nov 14 01:45:37 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4584) commit 8cba652 Author: Chan <bot+chan@asyncapi.io> Date: Thu Nov 13 01:44:26 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4581) commit 722963b Author: Souryavardhan singh <144201791+Sourya07@users.noreply.github.com> Date: Wed Nov 12 21:09:00 2025 +0530 docs: broken link to new-tool-documentation.md in Tools documentation (asyncapi#4542) Co-authored-by: Sourya07 <singhsourya137@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> commit 4d0d969 Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 12 07:32:39 2025 +0100 docs(community): update latest community documentation (asyncapi#4574) commit 6aaecb1 Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 12 01:43:52 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4573) commit 406151e Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 11 01:44:03 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4568) commit be72df8 Author: Chan <bot+chan@asyncapi.io> Date: Mon Nov 10 01:47:43 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4563) commit cecd342 Author: Prince Rajpoot <prince.rajpoot.20@gmail.com> Date: Sun Nov 9 13:14:15 2025 +0530 feat: enable tools view regeneration at build time (asyncapi#4511) * Add support for tools view regeneration at PR level for manual tools * minor formatting change * minor improvement * minor change * Added test cases * minor improvement * added more assertions commit 445e7c1 Author: Anushka Sharan <111284729+anushkaaaaaaaa@users.noreply.github.com> Date: Fri Nov 7 21:58:31 2025 +0530 test: add E2E tests for home page, header and footer components (asyncapi#4194) * feat: add cypress for e2e testing * feat: add cypress for e2e testing * feat: demo cypress test * feat: header e2e tests * feat: footer e2e tests * feat: add e2e tests for homepage (and other regarding pages) * test: add test for docs button * fix: minor e2e tests fixes * ci: add e2e tests workflow * fix: e2e tests fix * fix: minor fixes * ci: minor fix * fix: minor fix * fix: another fix * ci: another minor fix * fix: final fix * fix: failing test fix * test: update tests to get rid of hardcoded links * fix: replace direct Cypress commands with homePage methods * ci: minor fix * fix: minor fix * ci: minor fix * ci: update dependencies * fix: small change * test: remove files from tsconfig * feat: implement base classes for each test file * fix: small change * fix: small change * fix: changes * feat: add centralized footer data and update footer validation tests * small change in footer.cy.js * refactor: simplify visit method in BasePage class * fix: correct import path for footer data in footer tests * refactor: fix lint issues in ToolsCard and ToolsDashboard components * refactor: revert changes in ToolsCard and ToolsDashboard components * small change * small change * fix(footer): update email contact in news links --------- Co-authored-by: Sambhav Gupta <81870866+sambhavgupta0705@users.noreply.github.com> Co-authored-by: Rohit <108233235+TRohit20@users.noreply.github.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> commit 167fbb9 Author: Chan <bot+chan@asyncapi.io> Date: Fri Nov 7 01:45:16 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4554) commit b5a86b7 Author: Chan <bot+chan@asyncapi.io> Date: Thu Nov 6 01:42:44 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4541) commit 4c5ecac Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 5 11:41:23 2025 +0100 docs(community): update latest community documentation (asyncapi#4539) commit 8688dc0 Author: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Date: Wed Nov 5 11:22:05 2025 +0200 chore(blog): add October community summary (asyncapi#4512) Co-authored-by: thulieblack <sibanda.thulie@gmail.com> commit b4bdd8b Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 4 11:38:41 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4532) commit 11414cc Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 4 11:38:37 2025 +0100 docs(community): update latest maintainers list (asyncapi#4531) commit 005177e Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 4 01:42:03 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4528) commit 9611f42 Author: Chan <bot+chan@asyncapi.io> Date: Mon Nov 3 01:46:28 2025 +0100 chore: update tools.json (asyncapi#4525) commit 053e5a6 Author: Chan <bot+chan@asyncapi.io> Date: Thu Oct 30 01:43:09 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4516) commit 04921b1 Author: Lukasz Gornicki <lpgornicki@gmail.com> Date: Tue Oct 28 15:36:16 2025 +0100 chore: add content with case studies (asyncapi#4486) Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> commit 6287929 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 27 10:52:50 2025 +0100 docs(cli): update latest cli documentation (asyncapi#4510) commit e398ae7 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 27 09:39:38 2025 +0100 ci: update LICENSE and NOTICE files from global .github repo (asyncapi#4509) commit 4788d4b Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 27 01:45:31 2025 +0100 chore: update tools.json (asyncapi#4508) commit d3c31cc Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 24 13:07:33 2025 +0200 docs(cli): update latest cli documentation (asyncapi#4504) commit a57da1f Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 24 02:40:29 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4502) commit 304d2ae Author: Chan <bot+chan@asyncapi.io> Date: Wed Oct 22 02:42:59 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4497) commit 6c974fc Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 21 13:26:10 2025 +0200 docs(community): update latest community documentation (asyncapi#4493) Co-authored-by: asyncapi-bot <info@asyncapi.io> commit b1787a0 Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 21 02:41:49 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4492) commit 5733a74 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 20 02:45:33 2025 +0200 chore: update tools.json (asyncapi#4490) commit 841a1d3 Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 17 06:12:55 2025 +0200 ci: update of files from global .github repo (asyncapi#4475) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit db754f6 Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 17 02:41:45 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4487) commit 9de49c1 Author: Chan <bot+chan@asyncapi.io> Date: Thu Oct 16 02:41:23 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4483) commit 6757477 Author: Chan <bot+chan@asyncapi.io> Date: Wed Oct 15 10:07:12 2025 +0200 docs(community): update latest tsc members list (asyncapi#4479) commit 568740e Author: Chan <bot+chan@asyncapi.io> Date: Wed Oct 15 02:42:05 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4477) commit f33b0de Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 14 16:34:12 2025 +0200 docs(community): update latest Board and TSC members list (asyncapi#4472) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 6a18edf Author: Sarthak Karode <sarthakkarodework@gmail.com> Date: Tue Oct 14 19:57:20 2025 +0530 docs: remove glee folder and update introduction-to-glee-a-spec-first-framework.md (asyncapi#4358) Co-authored-by: sarthakKarode <sarthakkarode@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> commit b215375 Author: Zbigniew Malcherczyk <zmalcherczyk@gmail.com> Date: Tue Oct 14 14:29:44 2025 +0200 chore(blog): add TransferGo <> AsyncAPI Blog Post (asyncapi#4434) Co-authored-by: Ferror <zmalcherczyk@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com> commit 7480244 Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 14 14:18:15 2025 +0200 docs(community): update latest community documentation (asyncapi#4474) commit 7058fd5 Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 14 09:40:10 2025 +0200 docs(community): update latest maintainers list (asyncapi#4471) commit e18da3b Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 14 08:42:29 2025 +0200 docs(community): update latest maintainers list (asyncapi#4470) commit ac7e38b Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 13 18:04:36 2025 +0200 docs(community): update latest Board members list (asyncapi#4469) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 1e3e8e8 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 13 14:51:16 2025 +0200 docs(community): update latest tsc members list (asyncapi#4468) commit 8560539 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 13 02:43:38 2025 +0200 chore: update tools.json (asyncapi#4467) commit 4fd7abd Author: Chan <bot+chan@asyncapi.io> Date: Sun Oct 12 02:42:39 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4465) commit 19e3c34 Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 10 18:11:58 2025 +0200 docs(community): update latest community documentation (asyncapi#4462) commit 4b2284c Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 10 02:42:27 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4461) commit 7affdb1 Author: Pastukhov Nikita <diementros@yandex.ru> Date: Fri Oct 10 02:45:03 2025 +0300 docs: fix FastStream tools dead links (asyncapi#4458) * docs: update FastStream tools link * docs: update FastStream tools links * chore: remove empty line * Update tools.json * Update tools-manual.json --------- Co-authored-by: Sambhav Gupta <81870866+sambhavgupta0705@users.noreply.github.com> commit 55d08d5 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 6 02:41:28 2025 +0200 chore: update tools.json (asyncapi#4459) commit 3b4454f Author: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Date: Fri Oct 3 11:45:21 2025 +0200 chore(blog): add the september summary (asyncapi#4438) Co-authored-by: thulieblack <sibanda.thulie@gmail.com> commit 2e4022c Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 3 02:39:43 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4449) commit bfda003 Author: Chan <bot+chan@asyncapi.io> Date: Thu Oct 2 17:10:30 2025 +0200 docs(community): update latest community documentation (asyncapi#4444) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit dc85424 Author: Fran Méndez <fmvilas@gmail.com> Date: Thu Oct 2 16:43:56 2025 +0200 chore: replace press email with info email address (asyncapi#4443) Co-authored-by: Fran Méndez <fmvilas@gmail.com> Co-authored-by: Sambhav Gupta <81870866+sambhavgupta0705@users.noreply.github.com> commit 75cd925 Author: Chan <bot+chan@asyncapi.io> Date: Thu Oct 2 02:42:15 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4442) commit 960a6b5 Author: Chan <bot+chan@asyncapi.io> Date: Wed Oct 1 21:38:20 2025 +0200 chore: update meetings.json, newsrooom_videos.json and dashboard.json (asyncapi#4426) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 4234dda Author: Chan <bot+chan@asyncapi.io> Date: Wed Oct 1 02:46:05 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4441) commit d4a1175 Author: Chan <bot+chan@asyncapi.io> Date: Tue Sep 30 02:43:19 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4440) commit 231498d Author: Chan <bot+chan@asyncapi.io> Date: Mon Sep 29 02:42:47 2025 +0200 chore: update tools.json (asyncapi#4439) commit 42eac67 Author: Chan <bot+chan@asyncapi.io> Date: Sun Sep 28 02:43:54 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4437) commit 0be788f Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Date: Fri Sep 26 21:58:26 2025 +0200 chore(deps): bump tar-fs (asyncapi#4436) commit c19543b Author: Chan <bot+chan@asyncapi.io> Date: Fri Sep 26 02:39:08 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4435) commit 9a8c037 Author: Chan <bot+chan@asyncapi.io> Date: Thu Sep 25 12:54:38 2025 +0200 docs(community): update latest community documentation (asyncapi#4432) commit 54b7241 Author: Zbigniew Malcherczyk <zmalcherczyk@gmail.com> Date: Thu Sep 25 09:55:27 2025 +0200 chore: initial TransferGo CaseStudy (asyncapi#4409) Co-authored-by: Ferror <zmalcherczyk@gmail.com> Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com> commit 78769a8 Author: Chan <bot+chan@asyncapi.io> Date: Wed Sep 24 02:40:34 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4431) commit 1ac8db4 Author: Chan <bot+chan@asyncapi.io> Date: Tue Sep 23 02:40:29 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4430) commit 9791f0d Author: Chan <bot+chan@asyncapi.io> Date: Mon Sep 22 02:43:56 2025 +0200 chore: update tools.json (asyncapi#4429)
7 participants
Community summary for the month of October
Summary by CodeRabbit
New Features
Bug Fixes / Content
Chores