Update ppm to commit 3542dee00f4622f7458f2f65f05e5 #1014
Merged
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.
Includes ppm Pull Requests:
Notes about notable changes:
PR 132 over at the ppm repo in particular is notable, as it fixes an issue with publishing a brand new package with the
ppm publish patch
command or similar. Other sub-commands ofpublish
to get a brand new package pushed to the Pulsar Package Registry are somewhat more cumbersome or advanced, so this gets the main popular way of publishing a new package "back online," so to speak.This seems to have also fixed
ppm publish --rename
, which may have been broken for some time inppm
'smaster
branch? As per my most-recent testing. Seems odd if I didn't recall this being reported before, but that was my impression from researching and testing this fix.Thanks for @confused-Techie for working through that fix, this has been a while in the making due to being a somewhat puzzling set of issues to debug and troubleshoot under the hood of ppm, also benefiting from knowledge of how the backend itself works.
(Giving myself some credit: I helped test the fixes extensively and gave feedback to develop the approach taken for the fix.)
Thank you also to multiple people for reporting this issue and bringing it to our attention. And, of course, apologies for the disruption to publishing your packages! The fix is here now.
(PR 127 is less notable for end-users, as
express
is a devDependency only, and would not be expected to be called in "production" or anywhere outside of runningppm
's own tests.)