Skip to content

chore(blog): board nomination for 2026#5239

Open
thulieblack wants to merge 10 commits intoasyncapi:masterfrom
thulieblack:gb-nom
Open

chore(blog): board nomination for 2026#5239
thulieblack wants to merge 10 commits intoasyncapi:masterfrom
thulieblack:gb-nom

Conversation

@thulieblack
Copy link
Copy Markdown
Member

@thulieblack thulieblack commented Mar 11, 2026

Board Nominations for 2026

Summary by CodeRabbit

  • Documentation
    • Added a new blog post announcing AsyncAPI Governance Board Nominations 2026 with eligibility, nominee requirements, submission guidelines, timeline, and key dates.
    • Updated blog metadata: removed the "featured" designation from the February 2026 summary and the AsyncAPI 3.1.0 release notes.

@netlify
Copy link
Copy Markdown

netlify bot commented Mar 11, 2026

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 96d4b27
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/69c833f96869260008fb2c1f
😎 Deploy Preview https://deploy-preview-5239--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 11, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 304a86b8-9a83-4b76-8318-9ac376d3afbb

📥 Commits

Reviewing files that changed from the base of the PR and between 3e1411e and 63c3f64.

📒 Files selected for processing (1)
  • markdown/blog/board-nomination.md
✅ Files skipped from review due to trivial changes (1)
  • markdown/blog/board-nomination.md

📝 Walkthrough

Walkthrough

Removed the featured: true frontmatter from two existing blog posts and added a new blog post announcing AsyncAPI Governance Board Nominations 2026 with eligibility, submission guidelines, and timeline.

Changes

Cohort / File(s) Summary
Featured Flag Removal
markdown/blog/2026-february-summary.md, markdown/blog/release-notes-3.1.0.md
Removed the featured: true frontmatter field from two existing blog posts.
New Blog Post
markdown/blog/board-nomination.md
Added a new blog post announcing AsyncAPI Governance Board Nominations 2026, including nomination timeline, eligibility (TSC membership required; no past misconduct/pending CoC issues), submission guidelines with required nominee details and word-count limits, and voting/announcement dates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰✨ I hopped through drafts with nimble feet,
New nominations placed so neat,
Featured flags tucked out of view,
A governance call for me and you,
Hop—submit your name, the board awaits!

🚥 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): board nomination for 2026' accurately describes the main change: adding a new blog post announcing AsyncAPI Governance Board Nominations for 2026.
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.

@thulieblack thulieblack changed the title initial-draft chore(blog): board nomination for 2026 Mar 11, 2026
@fmvilas
Copy link
Copy Markdown
Member

fmvilas commented Mar 16, 2026

@thulieblack you may want to mention that we're electing 3 members this year instead of the planned 2 because I'm stepping down.

@asyncapi-bot
Copy link
Copy Markdown
Contributor

asyncapi-bot commented Mar 24, 2026

⚡️ 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-5239--asyncapi-website.netlify.app/

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 24, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (f041491) to head (96d4b27).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #5239   +/-   ##
=========================================
  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.

fmvilas
fmvilas previously approved these changes Mar 24, 2026
Copy link
Copy Markdown
Member

@fmvilas fmvilas 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
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/board-nomination.md`:
- Around line 53-63: Standardize the timeline wording and timestamps: update the
sentence "Nominations are open from the **1st to the 26th of April at 12.00 PM
UTC**" to a consistent format with explicit year and time zone (e.g.,
"Nominations are open from 1 April 2026 until 26 April 2026 at 12:00 PM UTC"),
ensure the summary list entries match that same style (use "1 April 2026" not "1
of April 2026", and "26 April 2026" with the same time format where applicable),
and add the missing year to the standalone sentence "Candidates will be
announced on 30 April." so all dates consistently include the year and use the
same time format (e.g., "12:00 PM UTC").
🪄 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: 1ce19a74-664a-4ece-aa26-db154a0802ca

📥 Commits

Reviewing files that changed from the base of the PR and between e106ba7 and 3e1411e.

📒 Files selected for processing (4)
  • markdown/blog/2026-february-summary.md
  • markdown/blog/board-nomination.md
  • markdown/blog/release-notes-3.1.0.md
  • public/img/posts/2026-blog-banner/nominations.webp
💤 Files with no reviewable changes (2)
  • markdown/blog/release-notes-3.1.0.md
  • markdown/blog/2026-february-summary.md

bandantonio
bandantonio previously approved these changes Mar 26, 2026
@thulieblack
Copy link
Copy Markdown
Member Author

@TRohit20 please your approval

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

@sonarqubecloud
Copy link
Copy Markdown

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

Labels

None yet

Projects

Status: In Progress
Status: To Be Triaged

Development

Successfully merging this pull request may close these issues.

6 participants