Repository navigation
fix: add the repository field to core and parsefiles - #103
Merged
Merged
Conversation
Closed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The v1.1.0 publish (run 39515271770, attempt 2) staged
@nodevu/aliasesand then failed on@nodevu/core:coreandparsefileswere the only published packages without arepositoryfield.Added:
repository(git+https://github.com/cutenode/nodevu.git, the same value the other six use) tocore/package.jsonandparsefiles/package.json, set withnpm pkg set.Added: a step in
lint.yml("Linter: all") that fails when any packagerelease.ymlpublishes is missing thatrepository.url, and*/package.jsonin its path filters so it runs when a workspace manifest changes. Run locally, it passes on this branch and fails on main naming@nodevu/core.