Skip to content
This repository has been archived by the owner on Mar 6, 2022. It is now read-only.

Feature: deploy NPM package to multiple registries #22

Closed
1 task done
0-vortex opened this issue Nov 23, 2021 · 1 comment
Closed
1 task done

Feature: deploy NPM package to multiple registries #22

0-vortex opened this issue Nov 23, 2021 · 1 comment
Labels
accepting prs Please work on this dependencies Pull requests that update a dependency file 🍕 enhancement 💡 feature A label to note if work is a feature

Comments

@0-vortex
Copy link
Contributor

Type of feature

Feature

Current behavior

Currently deploying NPM packages based on the publishConfig to https://www.npmjs.com

Desired solution

Expand to include and default to ghcr.io, while enabling npmjs.com releases only if corresponding environment variables are present

Additional context

explore https://github.com/amanda-mitchell/semantic-release-npm-multiple

Code of Conduct

  • I agree to follow this project's Code of Conduct
@0-vortex 0-vortex added 💡 feature A label to note if work is a feature 👀 needs triage accepting prs Please work on this dependencies Pull requests that update a dependency file 🍕 enhancement and removed 👀 needs triage labels Nov 23, 2021
@0-vortex
Copy link
Contributor Author

0-vortex commented Mar 4, 2022

closing in favor of open-sauced/release#2

@0-vortex 0-vortex closed this as completed Mar 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
accepting prs Please work on this dependencies Pull requests that update a dependency file 🍕 enhancement 💡 feature A label to note if work is a feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@0-vortex