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
Licensing issues #162
Comments
@char0n thanks for the heads up, I verified that building from master does not include the outdated BSD header. cc @sophiebits |
@aweary is it possible to publish a new release with the fixed bundle ? We just cannot use prop-types until it contains the BSD + Patent references. |
@char0n I think we could push a patch release. I'll ping the right people to look into this today, sorry about the delay. |
@char0n You can always build it locally if you want. |
@char0n I've published 15.6.1 and verified that |
Yeah I double checked. Thank for for swift response and release. |
The latest version of prop-types 15.6.0 on npm contains files
prop-types.js
andprop-types.min.js
. These files represents UMD builds. Unfortunatelyprop-types.js
file contains segments still licensed under BSD + Patents. It can be seen for example here:I think this happened accidentally by creating the UMD build before changing the license headers in the required files. There are totally 3 references to the BSD + Patents and it can be seen here. This may have some legal implications for people using it.
Is it possible to release a patch release fixing this UMD build files ?
Thank you very much
The text was updated successfully, but these errors were encountered: