Skip to content
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

feat(target): Add target local #106

Merged
merged 1 commit into from
Mar 23, 2023

Conversation

pohy
Copy link
Contributor

@pohy pohy commented Feb 17, 2023

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)
  • 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

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

Sometimes, it is not necessary to publish to the Chrome store. But you want the zipped extension.
@HenryC-3
Copy link

This is great, please merge it @GabrielDuarteM

@GabeDuarteM
Copy link
Owner

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 👍

@GabeDuarteM GabeDuarteM merged commit 45b4c15 into GabeDuarteM:master Mar 23, 2023
@github-actions
Copy link

🎉 This PR is included in version 3.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@pohy
Copy link
Contributor Author

pohy commented Apr 1, 2023

Thanks for merging! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants