We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
By adding automated releases to each plugin, and causing the bower.json to be a copy of the package.json and in including "private": true in the package.json to prevent the automation scripts publishing on npm, the bower library will now not register the plugins, due to these lines in the bower library https://github.com/bower/bower/blob/a0d44443245cbe52f3f0bd90c3f41274bc040c7a/lib/commands/register.js#L44-L49
"private": true
As we register plugins by hand, it should be possible to register plugins in our bower repos even if they are marked as private.
"private": true, "scripts": { "postversion": "cp package.json bower.json" },
The text was updated successfully, but these errors were encountered:
Fix: Allow register of private repos (fixes #200)
c87882e
Fix: Allow register of private repos (fixes #200) (#201)
11723bd
* Fix: Allow register of private repos (fixes #200) * Update register.js
Chore(release): 3.1.4 [skip ci]
f2bc507
## [3.1.4](v3.1.3...v3.1.4) (2023-10-17) ### Fix * Allow register of private repos (fixes #200) (#201) ([11723bd](11723bd)), closes [#200](#200) [#201](#201) [#200](#200)
🎉 This issue has been resolved in version 3.1.4 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
oliverfoster
Successfully merging a pull request may close this issue.
Subject of the issue
By adding automated releases to each plugin, and causing the bower.json to be a copy of the package.json and in including
"private": true
in the package.json to prevent the automation scripts publishing on npm, the bower library will now not register the plugins, due to these lines in the bower library https://github.com/bower/bower/blob/a0d44443245cbe52f3f0bd90c3f41274bc040c7a/lib/commands/register.js#L44-L49As we register plugins by hand, it should be possible to register plugins in our bower repos even if they are marked as private.
Example package.json:
The text was updated successfully, but these errors were encountered: