Delete existing release before creating a new one when tag is updated.
This prevents "Release has no Tag" error when recreating tags.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Simplified workflow based on wp-fedistream and wc-tier-and-package-prices
which have working CI/CD pipelines with same project structure.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Copy workspace to temp directory with proper subdirectory name
before creating zip to ensure correct WordPress plugin structure.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Explicitly check vendor after composer install and replace
symlink with actual files if needed for proper packaging.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
--no-check-lock: Skip lock file validation (regenerated during install)
--no-check-all: Only validate schema, not warnings
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Change version constraint from @dev to * for path repository
- Remove --strict from composer validate (path repos can't have proper versions)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Replace non-existent actions/gitea-release-action with direct
Gitea API calls using curl for release creation and asset upload.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Convert wc-licensed-product-client from Composer VCS to git submodule
- Add Gitea Actions workflow for automated releases on version tags
- Update composer.json to use path repository for submodule
- Workflow includes: submodule checkout, PHP setup, translation compilation,
version verification, package creation, checksum generation, release upload
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
