Skip to content

Comments

chore(blog): add may update#4132

Merged
asyncapi-bot merged 6 commits intoasyncapi:masterfrom
thulieblack:may-2025
May 29, 2025
Merged

chore(blog): add may update#4132
asyncapi-bot merged 6 commits intoasyncapi:masterfrom
thulieblack:may-2025

Conversation

@thulieblack
Copy link
Member

@thulieblack thulieblack commented May 27, 2025

Add the monthly summary for May 2025!

Summary by CodeRabbit

  • New Features

    • Added a new blog post: "Monthly Community Update: May 2025," featuring project news, community highlights, upcoming events, and new member introductions.
  • Chores

    • Removed the featured status from the April 2025 community update blog post metadata.

@netlify
Copy link

netlify bot commented May 27, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit d6757d7
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/68383b7abd07fc00089e34b4
😎 Deploy Preview https://deploy-preview-4132--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 27, 2025

Walkthrough

A new blog post for May 2025 has been added, featuring community updates, event announcements, and recognitions. Additionally, the featured: true metadata has been removed from the April 2025 blog post. No changes were made to code or public entities.

Changes

File(s) Change Summary
markdown/blog/2025-may-summary.md Added new blog post for May 2025 with community updates, event news, and recognitions.
markdown/blog/2025-april-summary.md Removed featured: true metadata from the April 2025 community update blog post.

Sequence Diagram(s)

sequenceDiagram
    participant Reader
    participant Website
    participant BlogPost

    Reader->>Website: Visit Blog
    Website->>BlogPost: Fetch May 2025 Update
    BlogPost-->>Website: Provide Content (news, events, recognitions)
    Website-->>Reader: Display May 2025 Community Update
Loading

Possibly related PRs

Suggested labels

ready-to-merge

Suggested reviewers

  • derberg
  • quetzalliwrites
  • anshgoyalevil
  • sambhavgupta0705
  • Mayaleeeee
  • asyncapi-bot-eve
  • devilkiller-ag
  • vishvamsinh28
  • Aahil13
  • VaishnaviNandakumar
  • akshatnema

Poem

May brings a blog post, fresh and new,
With updates and news for the AsyncAPI crew.
April’s spotlight dims, as metadata shifts,
Community stories and recognitions give us lifts.
Hopping along, we share and cheer—
Here’s to another vibrant, bustling year! 🐰✨


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@codecov
Copy link

codecov bot commented May 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (0709749) to head (d6757d7).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #4132   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          778       778           
  Branches       144       144           
=========================================
  Hits           778       778           

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (2)
markdown/blog/2025-may-summary.md (2)

17-17: Refine redundant wording

The phrase “upcoming winter season” is a bit wordy. Consider simplifying to “upcoming winter” for conciseness.

-As May ushers in the warmth of spring, while some of us in the southern hemisphere brace ourselves for the upcoming winter season, it's also a time to recognize...
+As May ushers in the warmth of spring, while some of us in the southern hemisphere brace ourselves for the upcoming winter, it's also a time to recognize...
🧰 Tools
🪛 LanguageTool

[style] ~17-~17: This phrase is redundant. Consider writing “winter”.
Context: ...sphere brace ourselves for the upcoming winter season, it's also a time to recognize and cele...

(SPRING_SEASON)


36-36: Improve sentence clarity

The call to action is slightly confusing. Consider splitting into two sentences:

-Please watch, share, and subscribe to our channel for more content like this will be published occasionally.
+Please watch, share, and subscribe to our channel. More content like this will be published occasionally.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c58c8a5 and a5a8cea.

📒 Files selected for processing (2)
  • markdown/blog/2025-april-summary.md (0 hunks)
  • markdown/blog/2025-may-summary.md (1 hunks)
💤 Files with no reviewable changes (1)
  • markdown/blog/2025-april-summary.md
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-may-summary.md

[style] ~17-~17: This phrase is redundant. Consider writing “winter”.
Context: ...sphere brace ourselves for the upcoming winter season, it's also a time to recognize and cele...

(SPRING_SEASON)


[duplication] ~46-~46: Possible typo: you repeated a word.
Context: ...st ambassadors to become TSC members. <Profiles profiles={[ { name: 'Daniel Kocot', av...

(ENGLISH_WORD_REPEAT_RULE)

⏰ Context from checks skipped due to timeout of 180000ms (1)
  • GitHub Check: Lighthouse CI
🔇 Additional comments (1)
markdown/blog/2025-may-summary.md (1)

14-14: Verify the featured flag usage

Please confirm whether featured: true is intentional for this monthly update—recently we removed featured from the April summary. If you don’t want this post to be promoted on the homepage carousel, consider removing it.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
markdown/blog/2025-may-summary.md (1)

44-44: Rephrase TSC ambassadors announcement for clarity
The sentence repeats names and could read more smoothly. This duplicates a previous review comment.

Proposed:

-We are excited to welcome [Naresh Jain](https://www.linkedin.com/in/nareshjain) as our new ambassador and [Daniel Kocot](https://www.linkedin.com/in/danielkocot) and Naresh as our first ambassadors to become TSC members.
+We are excited to welcome [Naresh Jain](https://www.linkedin.com/in/nareshjain) as our new ambassador, and congratulations to [Daniel Kocot](https://www.linkedin.com/in/danielkocot) and Naresh on becoming the first ambassadors to join the TSC.
🧹 Nitpick comments (2)
markdown/blog/2025-may-summary.md (2)

17-17: Remove redundant wording in introductory sentence
The phrase “upcoming winter season” is wordy; consider simplifying to “winter” for clarity and brevity.

Apply this diff:

-As May ushers in the warmth of spring, while some of us in the southern hemisphere brace ourselves for the upcoming winter season, it's also a time to recognize and celebrate the dedication of those who contribute to projects that drive innovation in the community. 
+As May ushers in the warmth of spring, while some of us in the southern hemisphere brace ourselves for winter, it's also a time to recognize and celebrate the dedication of those who contribute to projects that drive innovation in the community. 
🧰 Tools
🪛 LanguageTool

[style] ~17-~17: This phrase is redundant. Consider writing “winter”.
Context: ...sphere brace ourselves for the upcoming winter season, it's also a time to recognize and cele...

(SPRING_SEASON)


36-36: Fix grammatical error in subscription call-to-action
The sentence is currently ungrammatical. Revise to clarify that more content will be published occasionally.

Consider:

-Please watch, share, and subscribe to our channel for more content like this will be published occasionally.
+Please watch, share, and subscribe to our channel, where more content like this will be published occasionally.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a5a8cea and 3f4e995.

📒 Files selected for processing (1)
  • markdown/blog/2025-may-summary.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-may-summary.md

[style] ~17-~17: This phrase is redundant. Consider writing “winter”.
Context: ...sphere brace ourselves for the upcoming winter season, it's also a time to recognize and cele...

(SPRING_SEASON)


[duplication] ~46-~46: Possible typo: you repeated a word.
Context: ...st ambassadors to become TSC members. <Profiles profiles={[ { name: 'Daniel Kocot', av...

(ENGLISH_WORD_REPEAT_RULE)

@thulieblack
Copy link
Member Author

@derberg anything missing?

derberg
derberg previously approved these changes May 28, 2025
Copy link
Member

@derberg derberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

♻️ Duplicate comments (2)
markdown/blog/2025-may-summary.md (2)

59-59: Resolved: “Coming in June” corrected
The heading now accurately reads “Coming in June,” addressing the previous mismatch.


44-44: ⚠️ Potential issue

Fix duplication and improve flow
The sentence repeats “Naresh” and is a bit clunky. Example revision:

- We are excited to welcome [Naresh Jain](https://www.linkedin.com/in/nareshjain) as our new ambassador and [Daniel Kocot](https://www.linkedin.com/in/danielkocot) and Naresh as our first ambassadors to become TSC members.
+ We are excited to welcome [Naresh Jain](https://www.linkedin.com/in/nareshjain) and [Daniel Kocot](https://www.linkedin.com/in/danielkocot) as our first ambassadors to join the TSC.
🧹 Nitpick comments (5)
markdown/blog/2025-may-summary.md (5)

5-7: Consider enriching tags for better discoverability
Adding a tag like Community Updates or Newsletter alongside Project Status can help readers filter monthly summaries more easily.


17-17: Nitpick: simplify seasonal phrasing
The word “season” is redundant here. For clarity and conciseness, consider:

-As May ushers in the warmth of spring, while some of us in the southern hemisphere brace ourselves for the upcoming winter season, it's also a time…
+As May ushers in the warmth of spring, while some of us in the southern hemisphere brace ourselves for winter, it's also a time…
🧰 Tools
🪛 LanguageTool

[style] ~17-~17: This phrase is redundant. Consider writing “winter”.
Context: ...sphere brace ourselves for the upcoming winter season, it's also a time to recognize and cele...

(SPRING_SEASON)


23-23: Optional: rephrase nomination count
To make the sentence more succinct, you could say “We have three candidates already” instead of “We currently have three nominations submitted”.


30-30: Unify date formatting
The post uses “June 5th” above but “the 27th of June” here. For consistency, rewrite as:

- submit your proposals before **the 27th of June**.
+ submit your proposals before **June 27th**.

40-40: Typographical: add space before apostrophe
For GSoC ’25, include a space:

- ## Google Summer of Code'25
+ ## Google Summer of Code '25
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3f4e995 and 6c32456.

📒 Files selected for processing (1)
  • markdown/blog/2025-may-summary.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-may-summary.md

[style] ~17-~17: This phrase is redundant. Consider writing “winter”.
Context: ...sphere brace ourselves for the upcoming winter season, it's also a time to recognize and cele...

(SPRING_SEASON)


[duplication] ~46-~46: Possible typo: you repeated a word.
Context: ...st ambassadors to become TSC members. <Profiles profiles={[ { name: 'Daniel Kocot', av...

(ENGLISH_WORD_REPEAT_RULE)

🔇 Additional comments (1)
markdown/blog/2025-may-summary.md (1)

14-14: Confirm the use of the featured flag in front matter
Monthly recap posts are typically not marked as featured on the site. Please verify whether this should remain featured: true or be removed/changed to false to align with site conventions.

derberg
derberg previously approved these changes May 28, 2025
Copy link
Collaborator

@TRohit20 TRohit20 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you @thulieblack

@TRohit20 TRohit20 requested a review from derberg May 28, 2025 12:59
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
markdown/blog/2025-may-summary.md (1)

44-44: 🛠️ Refactor suggestion

Remove duplicate name and clarify ambassador announcement.

Line 44 repeats “Naresh” and reads awkwardly. Rephrase to introduce both ambassadors clearly:

- We are excited to welcome [Naresh Jain](https://www.linkedin.com/in/nareshjain) as our new ambassador and [Daniel Kocot](https://www.linkedin.com/in/danielkocot) and Naresh as our first ambassadors to become TSC members.
+ We are excited to welcome [Naresh Jain](https://www.linkedin.com/in/nareshjain) as our new ambassador, and congratulations to [Daniel Kocot](https://www.linkedin.com/in/danielkocot) and Naresh Jain on becoming the first ambassadors to join the TSC.
🧹 Nitpick comments (2)
markdown/blog/2025-may-summary.md (2)

36-37: Improve clarity in the onboarding video call-to-action.

The sentence is a bit long and the clause “for more content like this, which are planned to be published occasionally” can be tightened for readability. Consider splitting into two sentences and updating wording for consistency:

- Our second onboarding video, done by [Azeez Elegbede](https://www.linkedin.com/in/acebuild) on API architecture, is now available on YouTube. Please watch, share, and subscribe to our channel for more content like this, which are planned to be published occasionally.
+ Our second onboarding video, created by [Azeez Elegbede](https://www.linkedin.com/in/acebuild) on API architecture, is now available on YouTube. Please watch, share, and subscribe to our channel—more videos like this will be published periodically.

17-17: Consider simplifying descriptive phrasing.

The phrase “upcoming winter season” is slightly redundant (“season” can be omitted). You might rewrite for brevity:

- some of us in the southern hemisphere brace ourselves for the upcoming winter season
+ some of us in the southern hemisphere brace ourselves for the upcoming winter
🧰 Tools
🪛 LanguageTool

[style] ~17-~17: This phrase is redundant. Consider writing “winter”.
Context: ...sphere brace ourselves for the upcoming winter season, it's also a time to recognize and cele...

(SPRING_SEASON)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6c32456 and e0b238b.

📒 Files selected for processing (1)
  • markdown/blog/2025-may-summary.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-may-summary.md

[style] ~17-~17: This phrase is redundant. Consider writing “winter”.
Context: ...sphere brace ourselves for the upcoming winter season, it's also a time to recognize and cele...

(SPRING_SEASON)


[duplication] ~46-~46: Possible typo: you repeated a word.
Context: ...st ambassadors to become TSC members. <Profiles profiles={[ { name: 'Daniel Kocot', av...

(ENGLISH_WORD_REPEAT_RULE)

⏰ Context from checks skipped due to timeout of 180000ms (1)
  • GitHub Check: Test NodeJS PR - macos-13

@anshgoyalevil
Copy link
Member

/rtm

@asyncapi-bot asyncapi-bot merged commit f3ed568 into asyncapi:master May 29, 2025
18 of 19 checks passed
@thulieblack thulieblack deleted the may-2025 branch May 29, 2025 10:57
aminoxix pushed a commit to aminoxix/asyncapi-website that referenced this pull request Jun 4, 2025
Co-authored-by: thulieblack <sibanda.thulie@gmail.com>
Co-authored-by: Rohit <108233235+TRohit20@users.noreply.github.com>
Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants