Releases

Release Management

• Releases may align with Spring AI OSS releases, commercial product releases, or operate on an independent schedule.
• The Spring AI Team can assist with:
  • Bootstrapping initial repositories
  • Providing a standardized project template
  • Setting up CI/CD workflows using GitHub Actions
• All projects must follow a clear Semantic Versioning (semver) scheme.
• The preferred release path is via GitHub Actions in the community repository, using Maven Central publication.
• Artifacts should use the groupId io.github.springaicommunity, consistent with GitHub-based Maven Central publishing conventions.
• Artifact IDs (e.g., spring-ai-rag-helper) may include dashes and should follow standard naming patterns. Note that this naming suggestion is specific to the GitHub-based Maven Central process; project owners can use their own bespoke process and their own artifact IDs to publish to a public Maven repository.
• Root Java package names are flexible and up to the contributor, though they should follow common Spring conventions.
• Note: The release templates for community-hosted repositories cannot use Spring's internal Maven Central credentials — credential sharing is not permitted.

Release Requirements

• Passing CI/CD pipeline
• Documentation updates reflecting any new features, changes, or deprecations
• A clear, well-structured changelog describing what has changed
• Version number must follow semantic versioning