Release v0.4.0

[afrittoli]

• Make sure all issues are resolved: https://github.com/cdevents/spec/milestone/4
• Switch all versions from 0.4.0-draft to 0.4.0 Prepare all resources for release v0.4 spec#199
• Switch all event versions from version-draft to version Prepare all resources for release v0.4 spec#199
• Remove mentions of draft / work-in-progress content Prepare all resources for release v0.4 spec#199
• Update the README to mention 0.4.0 as latest release Update the README to v0.4 release spec#201
• Tag spec and create branch for patch releases https://github.com/cdevents/spec/releases/tag/v0.4.0
• Produce release notes through GitHub https://github.com/cdevents/spec/releases/tag/v0.4.0
• Update cdevents.dev as needed Update the website for v0.4 cdevents.dev#42
• Prepare a release announcement for v0.4 (see RFC: Github-CDEvents Integration #47 for reference) - draft
• Announce release on slack and mailing list
• Move main in the spec repo to the new -draft release Open main for v0.5.0 release contributions spec#203
• Updates the SDKs
  • Golang
  • Java
  • Rust
  • Python

[e-backmark-ericsson]

Should we also create issues as part of this issue, for each tool that implements CDEvents support, to upgrade to this new version? Those issues should then be added to our CDEvents in tools project

[afrittoli]

The Python SDK is currently un-maintained. Closing this issue.

[afrittoli]

Should we also create issues as part of this issue, for each tool that implements CDEvents support, to upgrade to this new version? Those issues should then be added to our CDEvents in tools project

We can track that, but I wouldn't block this issue on that.