Skip to main content

Getting Support

This guide explains how to get help with Excalibur, our support policy, and what to expect.

ResourceDescription
GitHub DiscussionsAsk questions, share ideas
GitHub IssuesReport bugs, request features
Security AdvisoriesReport vulnerabilities (private)
Community Project

This is an open-source project maintained by volunteers. Response times are best-effort and not guaranteed.

Supported Versions​

FrameworkStatusSupport Ends
.NET 10.0Current.NET 11 + 6 months
.NET 9.0SupportedMay 2026
.NET 8.0 LTSSupportedNovember 2026
.NET 7.0EOLNot supported
.NET 6.0EOLNot supported

All packages multi-target .NET 8.0, .NET 9.0, and .NET 10.0.

Provider Testing Coverage​

Providers vary in how thoroughly they are tested and documented.

Primary Providers​

Fully tested in CI, documented, and actively maintained.

ProviderPackages
SQL ServerEventSourcing, Data, LeaderElection, Saga
PostgresEventSourcing, Data
RabbitMQTransport
Azure Service BusTransport
Azure Cosmos DBEventSourcing, Data

Additional Providers​

Functional with tests, but may lag behind primary providers in documentation or edge-case coverage.

ProviderPackages
KafkaTransport
AWS SQSTransport
Google Pub/SubTransport
MongoDBData
RedisData, LeaderElection
DynamoDBEventSourcing, Data
FirestoreEventSourcing, Data

In-Memory Providers​

For testing only. Not recommended for production use.

End-of-Life Policy​

When a framework version reaches EOL:

timeline
    title EOL Process
    6 months before : Announce deprecation
    3 months before : Add [Obsolete] warnings
    EOL date : Remove from CI matrix
    Next major release : Remove support
TimelineAction
6 months before EOLAnnounce deprecation
3 months before EOLAdd [Obsolete] warnings
EOL dateRemove from CI matrix
Next major releaseRemove support completely

Breaking Changes​

We follow Semantic Versioning:

VersionBreaking Changes?Examples
Patch (x.y.Z)NoBug fixes
Minor (x.Y.0)NoNew features, deprecations
Major (X.0.0)YesAPI changes, removals

Deprecation Process​

  1. Mark deprecated with [Obsolete] in a minor release
  2. Document migration in CHANGELOG.md
  3. Wait minimum 6 months before removal
  4. Remove in next major release

Security Vulnerabilities​

Reporting​

Private Disclosure Required

DO NOT create public issues for security vulnerabilities.

Use GitHub Security Advisories for private disclosure.

Include in your report:

  • Affected versions
  • Severity assessment
  • Steps to reproduce
  • Potential impact

Response​

Security reports are treated with high priority. Expect acknowledgment and triage as soon as practical.

Compatibility Matrix​

For detailed compatibility information, see the Compatibility Matrix:

  • .NET version support and EOL dates
  • Provider package compatibility
  • Cloud platform support (Azure, AWS, GCP)
  • Native AOT and trimming status
  • Provider SDK versions

FAQ​

Which providers are production-ready?​

Primary providers (SQL Server, Postgres, RabbitMQ, Azure Service Bus, Cosmos DB) are fully tested and recommended for production.

Additional providers are functional but may have less documentation or edge-case coverage.

How do I report a bug?​

Create a GitHub Issue with:

  • Framework version (.NET 8, 9, or 10)
  • Provider (SQL Server, Kafka, etc.)
  • Error message and stack trace
  • Minimal reproduction steps

When will feature X be added?​

Check GitHub Discussions for roadmap items. Feature requests are prioritized by community interest.

How do I request a release?​

See RELEASE.md for details on requesting releases.

Is commercial support available?​

No. This is a community-maintained open-source project with no commercial support tier.

For enterprise needs:

  • Contribute fixes and features
  • Sponsor development
  • Build internal expertise

See Also​