You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey!
I'm trying to use this action to publish an extension that is a part of a monorepo that consists of npm packages and the extension.
The automated publishing action goes over all the packages and tries to publish them. If the npm package version hasn't been updated—the package get's skipped. But when the extension's version stays the same, this action tries to publish it anyway—which is fine—but then the script throws which also cancels the whole action.
{
kind: 'chromewebstore#item',
id: 'my-ext-id',
uploadState: 'FAILURE',
itemError: [
{
error_code: 'ITEM_NOT_UPDATABLE',
error_detail: 'The item cannot be updated now because it is in pending review, ready to publish, or deleted status.'
}
]
}
Would it be possible to have an option for silent errors or something that would prevent throwing?
It could also be helpful in repos with only the extension, where the action is just running automatically on push every time—regardless of if the extension was updated or not.
The text was updated successfully, but these errors were encountered:
Hey!
I'm trying to use this action to publish an extension that is a part of a monorepo that consists of npm packages and the extension.
The automated publishing action goes over all the packages and tries to publish them. If the npm package version hasn't been updated—the package get's skipped. But when the extension's version stays the same, this action tries to publish it anyway—which is fine—but then the script throws which also cancels the whole action.
Would it be possible to have an option for silent errors or something that would prevent throwing?
It could also be helpful in repos with only the extension, where the action is just running automatically on push every time—regardless of if the extension was updated or not.
The text was updated successfully, but these errors were encountered: