Apache Pulsar 4.1 end of life (EOL) date and support status
End of life End of life since 2026-03-08 (214 days ago)
Upgrade: Apache Pulsar 4.1 no longer receives fixes. Supported cycles: 5.0, 4.0.
| Product | Apache Pulsar |
|---|---|
| Version cycle | 4.1 |
| Status | End of life |
| Released | 2025-09-08 |
| Active support until | — |
| End of life | 2026-03-08 |
| Latest version | 4.1.3 (2026-02-19) |
| Last verified | 2026-10-08 |
All Apache Pulsar versions → · Source: endoflife.date
Frequently asked questions
Is Apache Pulsar 4.1 end of life?
Yes. End of life since 2026-03-08 (214 days ago). It no longer receives security or bug fixes.
When does Apache Pulsar 4.1 reach end of life?
Apache Pulsar 4.1 reached end of life on 2026-03-08.
When was Apache Pulsar 4.1 released?
Apache Pulsar 4.1 was first released on 2025-09-08.
What is the latest Apache Pulsar 4.1 version?
The latest 4.1 release is 4.1.3, published on 2026-02-19.
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
For agents
GET https://vigia.coredls.cloud/v1/eol/apache-pulsar/4.1