-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added new task to verify if package was published correctly to npm. #965
Conversation
packages/ckeditor5-dev-release-tools/lib/utils/publishpackageonnpmcallback.js
Outdated
Show resolved
Hide resolved
packages/ckeditor5-dev-release-tools/lib/tasks/verifypackagespublishedcorrectly.js
Outdated
Show resolved
Hide resolved
packages/ckeditor5-dev-release-tools/lib/tasks/verifypackagespublishedcorrectly.js
Outdated
Show resolved
Hide resolved
packages/ckeditor5-dev-release-tools/lib/tasks/verifypackagespublishedcorrectly.js
Outdated
Show resolved
Hide resolved
packages/ckeditor5-dev-release-tools/lib/tasks/verifypackagespublishedcorrectly.js
Outdated
Show resolved
Hide resolved
packages/ckeditor5-dev-release-tools/tests/utils/publishpackageonnpmcallback.js
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
const packageJson = await fs.readJson( upath.join( packageToVerify, 'package.json' ) ); | ||
|
||
try { | ||
await checkVersionAvailability( version, packageJson.name ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
checkVersionAvailability()
returns a promise that resolves to true
if the provided version does not exist or resolves the promise to false
otherwise.
We should check the returned value here.
Suggested merge commit message (convention)
Feature (release-tools): Added a new task to verify if packages were published correctly to npm. See ckeditor/ckeditor5#16625.
Additional information
For example – encountered issues, assumptions you had to make, other affected tickets, etc.