Skip to content

Conversation

@asterisk-release-automation
Copy link

Asterisk Releases Update

πŸ“¦ New Versions Detected

Stable Releases:

  • 20.17.0 (Stable Release)
  • 21.12.0 (Stable Release)
  • 22.7.0 (Stable Release)
  • 23.1.0 (Stable Release)

βœ… Changes Made

  • ✨ Updated supported-asterisk-builds.yml with new versions
  • πŸ“¦ Refreshed release lists (TXT and YAML formats)
  • πŸ”§ Generated YAML config files for new versions
  • 🐳 Generated Dockerfiles and build scripts (build.sh, healthcheck.sh)
  • 🎯 Ready for Docker builds - can trigger build-images workflow

🎨 Review Checklist

  • Verify all versions are legitimate Asterisk releases
  • Check versions follow semantic versioning
  • Confirm release types are appropriate for building
  • Review if special build configurations needed

πŸš€ Next Steps

After merging this PR:

  • Build system will support new versions
  • Can trigger builds via build-images workflow
  • Versions will be available in build matrix

πŸ€– Automation Details

  • Branch: asterisk-new-releases
  • Workflow: Discover New Asterisk Releases
  • Run ID: 19582129622
  • Generated: 2025-11-21 20:06:11 UTC

….0 23.1.0 - Auto-generated by: Discover New Asterisk Releases (19582129622)
@github-actions
Copy link
Contributor

πŸŽ† New Asterisk Releases Detected

This PR adds the following new versions:

  • 20.17.0
  • 21.12.0
  • 22.7.0
  • 23.1.0

πŸ”¨ Building and pushing Docker images with `-dev` suffix for validation...

Note: Images are pushed to GitHub Container Registry only (`ghcr.io`) with `-dev` tags (e.g., `latest-dev`, `stable-dev`) to avoid consuming Docker Hub quota. Production tags will be created on both registries after merging to main.

@github-actions
Copy link
Contributor

❌ Build Results for New Releases

Status: Some builds failed
Versions: 20.17.0, 21.12.0, 22.7.0, 23.1.0
Total configurations: 4

❌ Build failures detected. Please review the workflow logs before merging.

Note: Images are pushed to GitHub Container Registry only (`ghcr.io`) with `-dev` tags for validation to avoid consuming Docker Hub quota. Production tags will be created on both registries after merging to main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant