ai-platform-release

Guides the release and publish workflow for the ai_platform REDAXO addon to redaxo.org.

4|Updated May 27, 2026
One-click install
npx skills add https://github.com/FriendsOfREDAXO/ai_platform --skill ai-platform-release-friendsofredaxo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-platform-release
Source: https://github.com/FriendsOfREDAXO/ai_platform/tree/main/.claude/skills/ai-platform-release
Command: npx skills add https://github.com/FriendsOfREDAXO/ai_platform --skill ai-platform-release-friendsofredaxo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing the ai_platform REDAXO addon involves a fragile chain of steps: version alignment between package.yml and git tags, PHP 8.2 platform pinning for Composer, checked-in vendor directories, and a GitHub Actions workflow that publishes to myredaxo.com. This Skill captures the exact checklist, commands, and known failure modes so releases do not break CI or the publish step. ## Core Features & Use Cases - Pre-Release Checklist: Verifies package.yml version format, committed vendor/ and composer.lock, the composer.json platform.php 8.2.0 pin, and that all symfony/* packages stay on the 7.4 line. - Release Cutting: Provides the exact gh release create command with prerelease flagging conventions for beta/rc/alpha tags. - Workflow Debugging: Documents fixes for common failures such as incompatible composer.lock packages on PHP 8.2 CI and myredaxo.com addon fetch errors, including how to rerun workflows without recreating releases. - Use Case: You want to tag 1.0.0-beta1 of the addon. The Skill walks you through the checklist, creates the GitHub release targeting main, monitors the publish-to-redaxo workflow, and tells you to use gh run rerun if the MyRedaxo credentials step fails. ## Quick Start Ask the assistant to cut a new beta release of the ai_platform addon and monitor the publish workflow until it succeeds.

Frequently Asked Questions about ai-platform-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new release for a REDAXO addon on GitHub?

Use gh release create with the version tag matching package.yml, targeting the main branch, and add the --prerelease flag for beta, rc, or alpha versions. The release: published event automatically triggers the publish-to-redaxo workflow.

Why does composer install fail in CI with PHP 8.2 after a local update?

The lock file contains Symfony 8.x packages requiring PHP 8.4 or higher. Set config.platform.php to 8.2.0 in composer.json, then run rm -rf vendor composer.lock followed by composer install --no-dev, and commit both files.

How do I fix the 'Could not fetch addon ai_platform' publish error?

The addon must exist and be active on myredaxo.com, and the org bot account behind MYREDAXO_USERNAME and MYREDAXO_API_KEY must be a maintainer. After fixing that, rerun the failed workflow with gh run rerun instead of recreating the release.

Should vendor and composer.lock be committed for a REDAXO addon release?

Yes, FriendsOfREDAXO convention requires vendor/ and composer.lock to be checked in, so vendor must not appear in .gitignore. The installer action expects the packaged dependencies to be present in the release.

What happens if commits land on main after creating a release tag?

The tag stays anchored to the old commit. Delete the release with gh release delete using --cleanup-tag, then recreate it with gh release create targeting main so the tag points at the latest commit.