chore: update links to correct URLs in package.json #2068
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
…istribution (dashpay#2032) Co-authored-by: Ivan Shumkov <[email protected]>
) Co-authored-by: Quantum Explorer <[email protected]>
Co-authored-by: owl352 <[email protected]>
Co-authored-by: Odysseas Gabrielides <[email protected]>
…ository.url", and "bugs.url"
|
Are the homepages supposed to point to the |
Maybe HEAD, for example https://github.com/dashpay/platform/tree/HEAD/packages/dashpay-contract#readme ? |
shumkov
requested changes
Aug 24, 2024
| }, | ||
| "homepage": "https://github.com/dashevo/dapi-grpc#readme", | ||
| "homepage": "https://github.com/dashpay/platform/tree/v1.1-dev/packages/dapi-grpc#readme", |
There was a problem hiding this comment.
It's better to use master. v1.1-dev will be deleted at some point.
shumkov
changed the title
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.
Updated the package.json files to reflect the move to the monorepo.
Note: I did not update the versions of the package.json files. I presume that would happen immediately before pushing to npm?
Issue being fixed or feature implemented
Helps npm point to the right location
What was done?
Updated links in the package.json files. In each package.json file:
How Has This Been Tested?
n/a
Breaking Changes
none
Checklist:
For repository code-owners and collaborators only