chore(deps): bumps react-transition-group to 4.3.0 (#1738)

[thecodejack]

Fixes #1738

• Bug fix
• New feature
• Chore
• Breaking change
• There is an open issue which this change addresses
• I have read the CONTRIBUTING document.
• My commits follow the Git Commit Guidelines
• My code follows the code style of this project.
• My change requires a change to the documentation.
• • I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

Have also tested manually react-transition-group consumed components which are Carousel, Collapse, Fade

[TheSharpieOne]

The usage of react-transition-group within reactstrap require react and react-dom of ^16.6.0, but the peerDep within our package.json is still ^16.3.0. The reason it works for things like the netlify preview (and locally) is because the version it runs is 16.8.6.
Can you bump the peerDep (at least ^16.6.0 but maybe want to jump to ^16.8.0 min version so we can use hooks) and mark the commit as a breaking change?

[thecodejack]

sure. It makes sense to update the peer dependancies. I will do that.

But the part I don't understand is why should this be a breaking change? I mean any app using react <16.8.x and >16.3.0 should be able to upgrade without any changes.

[thecodejack]

Ok. I see it failing if deps are mentioned this way

"react": "16.3.0",
"reactstrap": "^8.2.0"

Is it worth making a major release for this?

[TheSharpieOne]

The next release is going to be a major after a fix accidentally introduced a breaking change. Change you update this PR to make the changes to the peerDeps?

[thecodejack]

@TheSharpieOne Have updated peer dependencies via e64b199

[thecodejack]

@TheSharpieOne Do I need to do anything for this PR or it's waiting for Major release?

[TheSharpieOne]

Waiting on a major. I really want to get forwardRef stuff in with this next breaking change. I haven't had time. Hoping to get it done sometime this month.

[GoPro16]

Waiting on a major. I really want to get forwardRef stuff in with this next breaking change. I haven't had time. Hoping to get it done sometime this month.

@TheSharpieOne I was going to plan on fixing #1356 in the next day if you can hold off before then. Then we can merge this in as well and kill 2 birds with one stone

[azizur]

Any update on this? There has been a new https://github.com/reactjs/react-transition-group/releases release 4.4.1 reactjs/react-transition-group#429 (comment)

[noacohen]

Do you know what is the expected date to release this update?

[andefred]

Any update on this? Is there anything I can do to help?

[phwebi]

Update: we have react-transition-group bumped to 4.4.2 on the bootstrap5 upgrade branch. The plan is to do a major release for the Bootstrap 5 updates after some further testing.