[TASK] Modernize publish workflow #435
Merged
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
With this change the GitHub action based publishin is enabled again after modernizing it. * Copy tailor package exclude configuration to the project to adjust which should be excluded and what not. This is required to tell tailor **NOT** to exclude the `vendor` folder used to ship hard required dependency for classic mode installations. * Add additional step to the publish workflow using composer to create a installation for the selected direct dependencies required in classic mode setups and not shipped by TYPO3 itself, removing unneeded stuff and autoload from the vendor folder. Further, PSR-4 autoload namespaces are added to the extension composer.json to tell TYPO3 to autoload additional packages. * Use tailor to create upload artifact first for given version tag. * Create GitHub release for version if not existing. * Attach tailor upload artifact to GitHub release, either created or pre-created. * Try upload created upload artifact with tailor to the `TYPO3 Extension Repository`, allow failing gracefully for now, because tailor based upload is broken but T3O/TER Team is working on it. * Document release workflow as maintainer only section in the `README.md` file. Nothing to hide, and maybe the whole process can server as example.
calien666
approved these changes
Feb 27, 2025
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.
With this change the GitHub action based publishin
is enabled again after modernizing it.
project to adjust which should be excluded and
what not. This is required to tell tailor NOT
to exclude the
vendorfolder used to ship hardrequired dependency for classic mode installations.
composer to create a installation for the selected
direct dependencies required in classic mode setups
and not shipped by TYPO3 itself, removing unneeded
stuff and autoload from the vendor folder. Further,
PSR-4 autoload namespaces are added to the extension
composer.json to tell TYPO3 to autoload additional
packages.
version tag.
either created or pre-created.
the
TYPO3 Extension Repository, allow failinggracefully for now, because tailor based upload is
broken but T3O/TER Team is working on it.
in the
README.mdfile. Nothing to hide, and maybethe whole process can server as example.