Managing Existing Releases

Managing Existing Releases

Developers can update release metadata after creation.

Supported actions include:

• Change version
• Change changelog
• Change release status
• Update critical/config/database flags
• Update compatibility notes
• Replace the release file
• Delete releases when allowed

Replacing a release file updates the existing release instead of creating a fake version.

The customer library continues to resolve the latest published release with a valid file.