Skip to content

chore(blog): add March summary#5282

Open
thulieblack wants to merge 3 commits intoasyncapi:masterfrom
thulieblack:mar-26
Open

chore(blog): add March summary#5282
thulieblack wants to merge 3 commits intoasyncapi:masterfrom
thulieblack:mar-26

Conversation

@thulieblack
Copy link
Copy Markdown
Member

@thulieblack thulieblack commented Mar 26, 2026

add the March blog summary

Summary by CodeRabbit

  • Documentation
    • Published March 2026 community update blog post featuring governance board nominations, AsyncAPI Conference 2026 schedule details and speaker call, new community meetup launches with leadership and sponsorship requests, social media announcements with featured community members, and upcoming April deadline notices for community initiatives.

@netlify
Copy link
Copy Markdown

netlify bot commented Mar 26, 2026

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 5f92eea
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/69c569301a65b3000873802c
😎 Deploy Preview https://deploy-preview-5282--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
Copy Markdown
Contributor

coderabbitai bot commented Mar 26, 2026

📝 Walkthrough

Walkthrough

A new blog post file documenting the March 2026 community update, including governance board announcements, conference details, meetup introductions, team member welcomes, and upcoming April deadlines.

Changes

Cohort / File(s) Summary
Blog Post Addition
markdown/blog/2026-march-summary.md
New monthly community update post with front-matter metadata, governance and conference announcements, AsyncAPI Meetup introductions, team member profiles, and April event deadlines.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A springtime post hops into view,
March updates, fresh and bright and new!
Conferences call, and meetups bloom,
Community gathers—let's fill the room! 🌱✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore(blog): add March summary' clearly and concisely identifies the main change: adding a March blog summary post.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

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

@sonarqubecloud
Copy link
Copy Markdown

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 26, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (c29c62b) to head (5f92eea).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #5282   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          830       830           
  Branches       159       159           
=========================================
  Hits           830       830           

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

@asyncapi-bot
Copy link
Copy Markdown
Contributor

⚡️ Lighthouse report for the changes in this PR:

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

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

@asyncapi-bot
Copy link
Copy Markdown
Contributor

⚡️ Lighthouse report for the changes in this PR:

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

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

Copy link
Copy Markdown
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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@markdown/blog/2026-march-summary.md`:
- Line 66: The file is missing a POSIX trailing newline at EOF; open the file
and add a single newline character after the final line (the line containing "-
[The Call for Proposals for the Amsterdam Edition] ... will close on the **12th
of April**."), save the file so the repository records the change, and verify
the file now ends with a newline to produce a clean git diff.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0fda1c54-f6fa-41f8-9ace-f4a4a23e9ace

📥 Commits

Reviewing files that changed from the base of the PR and between c29c62b and 5f92eea.

📒 Files selected for processing (2)
  • markdown/blog/2026-march-summary.md
  • public/img/posts/2026-blog-banner/march-banner.webp

## Coming in April
- Governance Board Nominations for 2026 are now open. For more details, [please read the blog on requirements](https://www.asyncapi.com/blog/board-nomination).
- AsyncAPI Community Updates Newsletter - The April Edition will arrive in your inbox on the 8th. [Please subscribe to the AsyncAPI Newsletter to stay up-to-date with the latest updates](https://www.asyncapi.com/newsletter).
- [The Call for Proposals for the Amsterdam Edition](https://conference.asyncapi.com/venue/Amsterdam) will close on the **12th of April**. No newline at end of file
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add a trailing newline at the end of the file.

The file is missing a trailing newline. Adding one ensures POSIX compliance and produces cleaner git diffs.

📝 Proposed fix
 - [The Call for Proposals for the Amsterdam Edition](https://conference.asyncapi.com/venue/Amsterdam) will close on the **12th of April**.
+
📝 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
- [The Call for Proposals for the Amsterdam Edition](https://conference.asyncapi.com/venue/Amsterdam) will close on the **12th of April**.
- [The Call for Proposals for the Amsterdam Edition](https://conference.asyncapi.com/venue/Amsterdam) will close on the **12th of April**.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@markdown/blog/2026-march-summary.md` at line 66, The file is missing a POSIX
trailing newline at EOF; open the file and add a single newline character after
the final line (the line containing "- [The Call for Proposals for the Amsterdam
Edition] ... will close on the **12th of April**."), save the file so the
repository records the change, and verify the file now ends with a newline to
produce a clean git diff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: To Be Triaged

Development

Successfully merging this pull request may close these issues.

2 participants