[AAE-11496] Publish npm package using https #2930
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
BSekula
force-pushed
the
dev-bsekula-AAE-11496-publish-to-npm-via-https
branch
from
5dcd529
to
57a8a3a
Compare
BSekula
force-pushed
the
dev-bsekula-AAE-11496-publish-to-npm-via-https
branch
from
57a8a3a
to
598fded
Compare
BSekula
commented
Jan 26, 2023
| @@ -70,11 +70,11 @@ do | |||
|
|
|||
| echo "npm deprecate @alfresco/$PROJECT@$PREVIOUS_LIBRARY_VERSION 'Upgrade to @latest or $NEW_LIBRARY_VERSION'" | |||
| else | |||
| echo -e "Publish $PROJECT\n" | |||
| echo -e "======== Publishing project: $PROJECT ========\n" | |||
There was a problem hiding this comment.
To be aligned with adf messages :)
mauriziovitale
approved these changes
Jan 26, 2023
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behaviour? (You can also link to an open issue here)
What is the new behaviour?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: