Montée de version de execa de v1 à v4 #38
Merged
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
octo-topi
added
cross-team
CHANNGELOG: sindresorhus/execa#253
octo-topi
force-pushed
the
bump-execa-1-to-4
branch
from
fd571c1 to
5c2bf30
Compare
octo-topi
added
💬 Tech Review Needed
and removed
cross-team
octo-topi
removed
💬 Tech Review Needed
work-in-progess
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.
🦄 Problème
execaest en version 1 (2016) et la dernière version est la version 4🤖 Solution
Application des changements préconisés dans les CHANGELOG:
💯 Pour tester
Exécuter en RA car les impacts concernent les opérations spécifiques Scalingo