feat(target): Add target local

[pohy]

Pull Request

Description

This PR adds another flag to the target option. Namely, target: 'local'.
When set, checking for environment variables is skipped in the verifyConditions step. As well as uploading the bundle to the Chrome store, during the publish step.

Why

It is sometimes desirable to skip publishing to Chrome store, but still update the version in manifest.json and obtain the zipped bundle. I.e. for publishing on the GitLab/Github releases page only.

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Release for testing

https://www.npmjs.com/package/@pohy/semantic-release-chrome

Checklist

• [x] Documentation
• [x] Ready to be merged
• [x] My code follows the code style of this project (run npm run ci to be sure).

[HenryC-3]

This is great, please merge it @GabrielDuarteM

[GabeDuarteM]

Hey @pohy 👋

Thank you for the PR!

I think this behaviour used to be possible before when you declared the plugin list. They used to allow you to opt-in/out of specific steps when declaring the plugin list (example here), but I can't find that anymore on the docs, so I guess at some point it was removed.

In any case, the code looks good to me. Not sure why the build pipeline is not being reported here, but I ran them locally and they passed, so I'll just merge it 👍

[github-actions[bot]]

:tada: This PR is included in version 3.2.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

[pohy]

Thanks for merging! 🙏