This repository has been archived by the owner on Sep 1, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 358
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: