Avoid to create a release of the action for every release of phparkitect #13
+82
−108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change decouples the GitHub Action release cycle from PHPArkitect releases. Changes: - Added 'phparkitect-version' input parameter to action.yml - Changed from pre-built Docker image to local Dockerfile build - Modified entrypoint.sh to handle custom version installation - Updated Dockerfile to use '*' (latest) as default version - Enhanced README with configuration examples and release strategy Benefits: - Users can specify any PHPArkitect version without waiting for a new action release - Supports version constraints (e.g., '^0.7', '0.7.0', '*') - Reduces maintenance burden - no need to release for every PHPArkitect update - Action releases only needed for actual action changes Breaking Changes: - Users referencing docker://phparkitect/arkitect-github-actions:X.X.X should update to phparkitect/arkitect-github-actions@main
The update_version.yml workflow is no longer needed because: - PHPArkitect version is now configurable via action input - Dockerfile uses '*' (latest) by default - No releases needed for PHPArkitect version bumps - Docker image is built locally on each workflow run This eliminates the automated cycle of checking for new PHPArkitect versions, committing, tagging, and publishing Docker images.
Added a clear migration section to help users transition from the deprecated docker://phparkitect/arkitect-github-actions:X.X.X format to the new phparkitect/arkitect-github-actions@main format. This helps users understand: - What needs to change in their workflows - Benefits of the new approach - How to specify versions if needed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.