-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Release new react-json-tree? #490
Comments
Can we please do this? We've had to clone the repo because you can't run babel 7 with this project because it specifies babel 6 as a dependency. We just need somebody to publish the code thats in the repo |
@timdorr What is the plan for publishing? It seems like we should publish:
|
No specific plan. I haven't yet looked through the state of the code right now to know if they should be published and at what version (patch vs minor vs major). Maybe we can do a quick RC release so they don't show up on the |
Makes sense. I've compiled an exhaustive changelog and made sure to find any changes since the last published version of the package (even packages that were last published from their original repo). Hopefully that will help with the publish. I've included a short summary under each change where appropriate. Overall, it looks like almost all of the changes were internal changes (#449 looks like mostly linting and converting tests to Jest). Before the PRs you merged, I don't think there had been any unpublished bug fixes or feature changes. Changelogreact-json-tree
redux-devtools-instrument
redux-devtools
redux-devtools-log-monitor
redux-devtools-core
redux-slider-monitor
redux-devtools-inspector
devui
redux-devtools-cli
d3tooltip
map2tree
redux-devtools-test-generator
redux-devtools-trace-monitor
|
@timdorr After thinking about it a little more, I think it would make sense to just publish
Based on #454 (comment), I don't think The rest of the packages don't have any non-internal changes. |
I don't know if it's helpful or not but here's a graph of the different repos getting merged together and the commit history since then: https://methuselah96.github.io/redux-devtools-app-testing/ (ignore the commit hashes and author). The last published version of each package is tagged. |
Any updates here? I'd love an update - we're getting warnings in our test runs about deprecated React methods. |
No updates from me. @timdorr Is there anything I can do to help publish? I have a bit of free time on my hands and if I knew that fixes/changes will get published at some point it would help motivate me to work on this project more. |
Hey @zalmoxisus or @alexkuz, can either of you grant me contributor access on npm? I'd like to help @Methuselah96 to get these updates published. |
@zalmoxisus @alexkuz @gaearon @jhen0409 @romseguy More specifically, the packages it would be great to have npm access to are: Already in this monorepo/organization:
Hope to move to this monorepo:
We already have npm access to (no action required):
You can give access to timdorr and/or methuselah96 on npm. |
Hey guys! Thanks for all the effort here!
Also for Let me know if I missed some that I have access. |
@zalmoxisus Thanks for your help, that looks great! @alexkuz The only one left that it would be nice to have access to from you is |
@timdorr @Methuselah96 here you are :) Thank you! |
Hey there!
There are downstream projects (the one I have my eye on is
@nteract/outputs
that could use a version ofreact-json-tree
that doesn't have a dependency onbabel-runtime
.Would it be possible to release a new version of
react-json-tree
?EDIT 20200721: updated nteract/outputs link
The text was updated successfully, but these errors were encountered: