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.0 LTSSupported (current)November 2028
.NET 9.0Dropped (April 2026)—
.NET 8.0 LTSDropped (April 2026)—
.NET 7.0EOLNot supported
.NET 6.0EOLNot supported

All packages target .NET 10.0 exclusively as of the .NET 10 release (April 2026). .NET 8.0 and .NET 9.0 are no longer supported targets. See the .NET 10 migration guide for consumer project update steps.

The Excalibur package line inherits these dates. Because the package major matches the .NET major, the 10.x line is supported for as long as .NET 10 is -- the row above is the date, and there is no second calendar. How long a line lasts, what gets backported to an older one, and when releases are cut are all stated in Support Lifecycle.

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:

TimelineAction
6 months before EOLAnnounce deprecation
3 months before EOLAdd [Obsolete] warnings
EOL dateRemove from CI matrix
Next major releaseRemove support completely

Breaking Changes​

The package major version matches the targeted .NET major (net10.0 → 10.x); minor and patch releases follow Semantic Versioning within that major line:

VersionBreaking Changes?Examples
Patch (10.0.Z)NoBug fixes
Minor (10.Y.0)NoNew features, deprecations
Major (10.x → 11.x)YesAPI changes, removals — coincides with a new .NET major line

Deprecation Process​

  1. Mark deprecated with [Obsolete] in a minor release
  2. Document migration in What's New
  3. It keeps working for the remainder of that major line -- minor and patch releases are backward compatible, so a deprecated API does not stop working before the next major
  4. Remove in the next major line, with a migration guide

During pre-release there is no deprecation window: an API may be removed in any subsequent build. The full policy, including how long each line is supported and what is backported to an older one, is Versioning and release stages.

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 10.0)
  • 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​