Fix version number in composer.lock and remove development dependencies #50
Conversation
This file contains 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
|
Merging thanks. |
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.
Pull Request for joomla#35073 .
Summary of Changes
With this commit we had added
"non-feature-branches": ["staging"],to the composer.json file in order to get the right pseudo-version number generated by composer in the autoloader files: joomla@87ed567 .This can be reverted since all our current branches which are not feature branches have a version in it so composer uses them.
Because the autoloader files are those from the staging branch as it seems, this PR here also updates them after a run of "composer install --no-dev". This also removes testing resources from the autoloader files.
Testing Instructions
Code review.