chore(blog): add last summary

[thulieblack]

Add the last summary for 2025

Summary by CodeRabbit

• Documentation
  • Added a new community update blog post covering Nov–Dec 2025: conference recaps (including ambassador panel), Developer Week 2026 planning, 2026 venue discussions, NPM security incident and response, Spec × Tooling updates (official MIME types, triage/public spec meetings), contributor profiles, embedded media, and closing holiday remarks.
  • Updated October 2025 blog post metadata to remove the featured flag.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Adds a new December 2025 community-update blog post with front matter and long-form content; removes the featured: true front-matter field from the October 2025 summary post.

Changes

Cohort / File(s)	Change Summary
New blog post markdown/blog/2025-december-summary.md	Adds a December 2025 community update post including front matter (title, date, type, tags, cover, authors, excerpt, featured), long-form updates on conferences, event planning, an NPM security incident and response, spec/tooling updates, embedded media (figure), and a profiles roster.
Blog metadata update markdown/blog/2025-october-summary.md	Removes the featured: true front-matter field; post content otherwise unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Check front-matter fields for validity (date format, tags, authors, featured flag).
• Verify internal links and embedded media paths referenced in markdown/blog/2025-december-summary.md.
• Confirm the security incident links (postmortem) and any external URLs are correct and use HTTPS.

Poem

🐇 I thumped a note for winter bright,
Pages wrapped in holiday light.
October's badge set gently free,
December's update blooms with glee. 🎉

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'chore(blog): add last summary' is vague and generic. While it mentions adding a summary to the blog, it doesn't specify that this is the December 2025 summary or provide any meaningful detail about what makes this summary significant.	Consider using a more descriptive title like 'chore(blog): add December 2025 summary' or 'chore(blog): add community update for November & December 2025' to clarify what summary is being added.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	f92a512
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/69492d74f340090008829135
😎 Deploy Preview	https://deploy-preview-4699--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 project configuration.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	38
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

Lighthouse ran on https://deploy-preview-4699--asyncapi-website.netlify.app/

[thulieblack]

@derberg anything missing?

@bandantonio first round of review please

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (65c10bb) to head (f92a512).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4699   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          798       798           
  Branches       146       146           
=========================================
  Hits           798       798           

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

markdown/blog/2025-december-summary.md (1)

28-28: Optional: Refine word choice for clarity and formality.

Static analysis flags two style opportunities:

• Line 28: "which included a variety of talks" could be more concise. Consider: "which featured multiple talks" or simply "which included several talks"
• Line 117: "It has been amazing to contribute" uses informal language. Consider: "It has been rewarding to contribute" or "It has been an honor to contribute"

These changes are optional and depend on your preferred tone. The current phrasing is acceptable for a community-written update, but slight refinements could enhance clarity and formality.

Also applies to: 117-117

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 83e282a and 8a6150d.

📒 Files selected for processing (2)

• markdown/blog/2025-december-summary.md (1 hunks)
• markdown/blog/2025-october-summary.md (0 hunks)

💤 Files with no reviewable changes (1)

• markdown/blog/2025-october-summary.md

🧰 Additional context used

🧠 Learnings (3)

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

Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.714Z
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.

📚 Learning: 2025-11-03T08:14:22.714Z

Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.714Z
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-december-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-december-summary.md

🪛 LanguageTool

markdown/blog/2025-december-summary.md

[style] ~28-~28: Consider using a more concise synonym.
Context: ... had the AsyncAPI track, which included a variety of talks, with the ambassador panel as the...

(A_VARIETY_OF)

---

[style] ~117-~117: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...for the consistent support. It has been amazing to contribute to our shared efforts thr...

(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). (1)

• GitHub Check: cypress-run

🔇 Additional comments (2)

markdown/blog/2025-december-summary.md (2)

98-98: Review link accessibility to ensure references are correct.

The blog post references several external links. Verification confirms the security postmortem blog is accessible at the referenced URL and GitHub issue #936 exists as described. However, the GitHub discussion on conference venues (#2133) and spec issue #1131 could not be verified through available resources—confirm these links are active before publication.

---

38-90: All ambassador profiles have been verified and are accurate. All 10 listed GitHub usernames are correct with accessible profiles, avatar URLs resolve to valid images, and user IDs match between avatar URLs and GitHub API data. No data integrity issues found.

[TRohit20]

Except for the minor suggestion, looks good to me!

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

markdown/blog/2025-december-summary.md (1)

28-28: Minor style refinements for publication polish.

The content is substantive and well-structured, but a few expressions could be more formal and concise:

• Line 28: "a variety of talks" → consider "diverse talks" or "multiple talks"
• Line 124: "At the moment" → replace with "Currently" or simply remove for conciseness
• Line 126: "for sure" → replace with "certainly" or "definitely"
• Line 140: "amazing" → consider "rewarding," "meaningful," or "valuable"

These tweaks will elevate the tone for a publication-quality blog post.

Also applies to: 124-124, 126-126, 140-140

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8a6150d and dcc7299.

📒 Files selected for processing (1)

• markdown/blog/2025-december-summary.md (1 hunks)

🧰 Additional context used

🧠 Learnings (3)

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

Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.714Z
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.

📚 Learning: 2025-11-03T08:14:22.714Z

Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.714Z
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-december-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-december-summary.md

🪛 LanguageTool

markdown/blog/2025-december-summary.md

[style] ~28-~28: Consider using a more concise synonym.
Context: ... had the AsyncAPI track, which included a variety of talks, with the ambassador panel as the...

(A_VARIETY_OF)

---

[style] ~124-~124: For conciseness, consider replacing this expression with an adverb.
Context: ...AsyncAPI v3.1 release for January 2026. At the moment, we know that [ROS 2](https://github.co...

(AT_THE_MOMENT)

---

[style] ~126-~126: The expression “for sure” is rather colloquial. To elevate your writing, consider replacing it with an adverb.
Context: ... for this release. Stay tuned. We will for sure organize the third meeting in January. ...

(FOR_SURE2)

---

[style] ~140-~140: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...for the consistent support. It has been amazing to contribute to our shared efforts thr...

(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-december-summary.md (4)

1-15: Frontmatter and metadata look good.

The date (2025-12-17) appropriately reflects the actual publication date, the tags and cover image are consistent with prior community summaries, and the author details are complete. The featured: true flag makes sense for this concluding year-end summary.

---

110-137: Spec x Tooling section incorporates community feedback well.

The section clearly explains official MIME type registration, ongoing spec triage meetings, and the security proposal with appropriate links and context. The structure and content align with community discussion threads and provide actionable next steps for readers interested in contributing.

---

100-108: NPM security incident section appropriately credits contributors and links to postmortem.

The narrative clearly acknowledges the key individuals who responded to the incident (Charlie Eriksen, Łukasz Górnicki, Ashish Padhy, and Fran Méndez) and directs readers to the detailed postmortem. This transparency and attribution are important for community trust.

---

38-90: Profiles component is well-structured with correct ambassador roster and avatar URLs.

All 10 ambassadors are listed with GitHub avatar URLs and proper links. The component renders correctly in the blog post context.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (4)

markdown/blog/2025-december-summary.md (4)

28-28: Reduce redundancy: simplify "a variety of talks".

Per static analysis, consider using a more concise synonym (e.g., "diverse talks" or "several talks") to tighten the prose.

🔎 Proposed refinement

-On the third day, we had the AsyncAPI track, which included a variety of talks, with the ambassador panel as the highlight of the event.
+On the third day, we had the AsyncAPI track, which included diverse talks, with the ambassador panel as the highlight of the event.

---

124-124: Tighten language: replace "At the moment" with an adverb.

For a more professional and concise style, consider replacing this phrase with an adverb such as "Currently" or "Presently".

🔎 Proposed refinement

-As [a result of the last meeting](https://github.com/asyncapi/community/issues/2187#issuecomment-3671287512), we scheduled the next AsyncAPI v3.1 release for January 2026. At the moment, we know that [ROS 2](https://github.com/asyncapi/spec/pull/1109) binding is scheduled for this release.
+As [a result of the last meeting](https://github.com/asyncapi/community/issues/2187#issuecomment-3671287512), we scheduled the next AsyncAPI v3.1 release for January 2026. Currently, we know that [ROS 2](https://github.com/asyncapi/spec/pull/1109) binding is scheduled for this release.

---

126-126: Elevate tone: replace colloquial "for sure" with a more formal adverb.

To maintain professional writing standards, consider replacing this phrase with "certainly," "assuredly," or "definitely."

🔎 Proposed refinement

-Stay tuned. We will for sure organize the third meeting in January. Three meetings in three months means we are getting regular and might transform into an official working group.
+Stay tuned. We will certainly organize the third meeting in January. Three meetings in three months means we are getting regular and might transform into an official working group.

---

140-140: Use a more formal alternative to "amazing".

For a professional blog post, consider replacing this colloquialism with a more expressive term such as "remarkable," "gratifying," or "rewarding."

🔎 Proposed refinement

-I want to thank the community for taking the time to read the AsyncAPI monthly summary and for the consistent support. It has been amazing to contribute to our shared efforts throughout the year.
+I want to thank the community for taking the time to read the AsyncAPI monthly summary and for the consistent support. It has been rewarding to contribute to our shared efforts throughout the year.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dcc7299 and d37fbb9.

📒 Files selected for processing (1)

• markdown/blog/2025-december-summary.md (1 hunks)

🧰 Additional context used

🧠 Learnings (3)

📓 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-11-03T08:14:22.714Z

Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.714Z
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-december-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-december-summary.md

🪛 LanguageTool

markdown/blog/2025-december-summary.md

[style] ~28-~28: Consider using a more concise synonym.
Context: ... had the AsyncAPI track, which included a variety of talks, with the ambassador panel as the...

(A_VARIETY_OF)

---

[style] ~124-~124: For conciseness, consider replacing this expression with an adverb.
Context: ...AsyncAPI v3.1 release for January 2026. At the moment, we know that [ROS 2](https://github.co...

(AT_THE_MOMENT)

---

[style] ~126-~126: The expression “for sure” is rather colloquial. To elevate your writing, consider replacing it with an adverb.
Context: ... for this release. Stay tuned. We will for sure organize the third meeting in January. ...

(FOR_SURE2)

---

[style] ~140-~140: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...for the consistent support. It has been amazing to contribute to our shared efforts thr...

(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). (1)

• GitHub Check: cypress-run

🔇 Additional comments (2)

markdown/blog/2025-december-summary.md (2)

14-14: Verify featured field consistency with other blog posts.

The October 2025 summary post had featured: true removed, but this December post includes it. Confirm whether this is intentional standardization or if it should be removed here as well for consistency.

---

1-146: Verify JSX Profiles component syntax for compatibility.

The <Profiles> component at lines 38–90 uses JSX syntax with object arrays. Ensure this syntax is correctly supported in your blog framework's markdown/MDX processing pipeline, especially if the framework has specific component registration or import requirements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (4)

markdown/blog/2025-december-summary.md (4)

28-28: Consider tightening the phrasing for clarity.

The phrase "a variety of talks" could be more concise. Consider alternatives like "diverse talks" or "multiple talks" to improve readability.

🔎 Proposed options

-On the third day, we had the AsyncAPI track, which included a variety of talks, with the ambassador panel as the highlight of the event.
+On the third day, we had the AsyncAPI track, which featured diverse talks and an ambassador panel as the highlight.

Or:

-On the third day, we had the AsyncAPI track, which included a variety of talks, with the ambassador panel as the highlight of the event.
+On the third day, we had the AsyncAPI track with multiple talks, featuring the ambassador panel as the highlight.

---

124-124: Minor style improvement: replace "At the moment" with a more concise adverb.

The phrase "At the moment" is somewhat verbose. Consider using "Currently" or "Now" for brevity.

🔎 Proposed fix

-As [a result of the last meeting](https://github.com/asyncapi/community/issues/2187#issuecomment-3671287512), we scheduled the next AsyncAPI v3.1 release for January 2026. At the moment, we know that [ROS 2](https://github.com/asyncapi/spec/pull/1109) binding is scheduled for this release.
+As [a result of the last meeting](https://github.com/asyncapi/community/issues/2187#issuecomment-3671287512), we scheduled the next AsyncAPI v3.1 release for January 2026. Currently, we know that [ROS 2](https://github.com/asyncapi/spec/pull/1109) binding is scheduled for this release.

---

126-126: Elevate informal phrasing to match the formal tone of the post.

The colloquial expression "for sure" stands out in formal technical writing. Consider replacing with "certainly" or "definitely."

🔎 Proposed fix

-Stay tuned. We will for sure organize the third meeting in January. Three meetings in three months means we are getting regular and might transform into an official working group.
+Stay tuned. We will certainly organize the third meeting in January. Three meetings in three months means we are getting regular and might transform into an official working group.

---

138-145: Use more formal language in the closing remarks.

The word "amazing" on line 140 is too colloquial for a professional community update. Consider using "rewarding," "fulfilling," or "valuable" instead.

🔎 Proposed fix

-I want to thank the community for taking the time to read the AsyncAPI monthly summary and for the consistent support. It has been amazing to contribute to our shared efforts throughout the year.
+I want to thank the community for taking the time to read the AsyncAPI monthly summary and for the consistent support. It has been rewarding to contribute to our shared efforts throughout the year.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d37fbb9 and f92a512.

📒 Files selected for processing (1)

• markdown/blog/2025-december-summary.md

🧰 Additional context used

🧠 Learnings (3)

📓 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-11-03T08:14:22.714Z

Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.714Z
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-december-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-december-summary.md

🪛 LanguageTool

markdown/blog/2025-december-summary.md

[style] ~28-~28: Consider using a more concise synonym.
Context: ... had the AsyncAPI track, which included a variety of talks, with the ambassador panel as the...

(A_VARIETY_OF)

---

[style] ~124-~124: For conciseness, consider replacing this expression with an adverb.
Context: ...AsyncAPI v3.1 release for January 2026. At the moment, we know that [ROS 2](https://github.co...

(AT_THE_MOMENT)

---

[style] ~126-~126: The expression “for sure” is rather colloquial. To elevate your writing, consider replacing it with an adverb.
Context: ... for this release. Stay tuned. We will for sure organize the third meeting in January. ...

(FOR_SURE2)

---

[style] ~140-~140: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...for the consistent support. It has been amazing to contribute to our shared efforts thr...

(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 (2)

markdown/blog/2025-december-summary.md (2)

1-15: Frontmatter is well-structured and consistent.

The date correctly reflects the publication date as per AsyncAPI conventions, and all required metadata fields are present.

---

100-107: NPM security incident section is well-documented.

Clear attribution, comprehensive details, and helpful links to further reading. Good balance between transparency and acknowledgment of team efforts.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Fix grammatical error in the Paris section.

Line 26 contains a grammatical error: "many ever surprised" should be "many were surprised."

🔎 Proposed fix

-Paris hosted the last conference of the year, which spanned three busy days. The biggest highlight of the conference was the API Standards booth, which we shared with friends from GraphQL, JSON Schema, and OpenAPI. It was a busy moment with attendees interested in our work, and many ever surprised by our focus on promoting Open Source.
+Paris hosted the last conference of the year, which spanned three busy days. The biggest highlight of the conference was the API Standards booth, which we shared with friends from GraphQL, JSON Schema, and OpenAPI. It was a busy moment with attendees interested in our work, and many were surprised by our focus on promoting Open Source.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	### Paris
	Paris hosted the last conference of the year, which spanned three busy days. The biggest highlight of the conference was the API Standards booth, which we shared with friends from GraphQL, JSON Schema, and OpenAPI. It was a busy moment with attendees interested in our work, and many ever surprised by our focus on promoting Open Source.
	On the third day, we had the AsyncAPI track, which included a variety of talks, with the ambassador panel as the highlight of the event.
	<Figure
	src="/img/posts/2025-blog-banner/ambassadors.webp"
	caption="AsyncAPI Ambassadors Panel"
	className="text-center"
	/>
	A huge thank you to our speakers, TSC members, and Ambassadors for volunteering at the booth, delivering presentations, and sharing their valuable insights.
	### Paris
	Paris hosted the last conference of the year, which spanned three busy days. The biggest highlight of the conference was the API Standards booth, which we shared with friends from GraphQL, JSON Schema, and OpenAPI. It was a busy moment with attendees interested in our work, and many were surprised by our focus on promoting Open Source.
	On the third day, we had the AsyncAPI track, which included a variety of talks, with the ambassador panel as the highlight of the event.
	<Figure
	src="/img/posts/2025-blog-banner/ambassadors.webp"
	caption="AsyncAPI Ambassadors Panel"
	className="text-center"
	/>
	A huge thank you to our speakers, TSC members, and Ambassadors for volunteering at the booth, delivering presentations, and sharing their valuable insights.

🧰 Tools

🪛 LanguageTool

[style] ~28-~28: Consider using a more concise synonym.
Context: ... had the AsyncAPI track, which included a variety of talks, with the ambassador panel as the...

(A_VARIETY_OF)

🤖 Prompt for AI Agents

In markdown/blog/2025-december-summary.md around lines 24 to 36, replace the
incorrect phrase "many ever surprised" with "many were surprised" in the Paris
section to fix the grammatical error; ensure the sentence reads smoothly and
retains original punctuation and meaning after the replacement.

[TRohit20]

LGTM! Thanks and Happy new year ! @thulieblack

[thulieblack]

/rtm