When I remove the “unused imports” (not without fears, because these “features” are known to break projects), the subsequent publishing attempts make the same alert to show up.
Note that I’m in a “Community Edition” license type (I explained this before), so maybe it has something to do.
Then when it’s my mate who tries to do it, with the proper license (even if it’s expired, we see a “grace period” message until tomorrow), she gets this problem:
The program runs in her local machine, there’s already a version number in the text input when trying to publish the package, and the package dependencies in her machine are up to date.
First, close the project and make sure there are no extra files which increase the package size unnecessary. Rename the project name in project.json. Reopen the project and try again.
Renaming project.json can cause problems because there is important info stored in that file. At least, you’ll have to reinstall the correct dependencies.
