chore(npm): changes scope to @hyperledger-labs/ #38
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
Fixes hyperledger-cacti#28 We'll be allowed to use the @hyperledger scope once the project graduates from the labs. At that point we can publish the same package contents under multiple package scopes for each new release to spare early adopters the migration effort. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
requested review from
tkuhrt,
hugo-borne,
jonathan-m-hamilton and
denis-yu-glotov
|
Ignoring build failures for RCA on #36 |
blefevre
pushed a commit
to blefevre/blockchain-integration-framework
that referenced
this pull request
Feb 4, 2020
…mogyvari/npm-package-scope-labs chore(npm): changes scope to @hyperledger-labs/
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.
Fixes #28
We'll be allowed to use the @hyperledger scope once the project
graduates from the labs.
At that point we can publish the same package contents under multiple package
scopes for each new release to spare early adopters the migration
effort.
Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com