release:publish should not print an error if a package does not exist on npm and it will not be published #10639
Labels
package:dev
squad:platform
Issue to be handled by the Platform team.
type:bug
This issue reports a buggy (incorrect) behavior.
type:task
This issue reports a chore (non-production change) and other types of "todos".
Milestone
📝 Provide detailed reproduction steps (if any)
It's hard to reproduce because you need to find a package that will not be published on npm but it's tracked in the repository.
It happened when I was releasing changes from https://github.com/ckeditor/ckeditor5-package-generator.
✔️ Expected result
❌ Actual result
❓ Possible solution
The text was updated successfully, but these errors were encountered: