Include ".active" navbar breaking change in v5 migration docs

[jhthompson]

Prerequisites

• I have searched for duplicate or closed feature requests
• I have read the contributing guidelines

Proposal

• Add description of a navbar breaking change to the v5.0 migration documentation navbar section
  • Change: Move "active" class from .nav-item to .nav-link #32730
  • I am willing to open a PR to fix, but could not find source file to edit (is there a v5.0 branch to make the PR against?)

Motivation and context

Navbar breaking change¹ was not listed in the v5 migration docs under the navbar section. It would nice to have it listed for easier migration as I almost missed this breaking change. Other related doc fixes²³

Footnotes

1. https://github.com/twbs/bootstrap/pull/32730 ↩

2. https://github.com/twbs/bootstrap/pull/32589 ↩

3. https://github.com/twbs/bootstrap/issues/32583 ↩

[jhthompson]

(oops, accidentally added with feature label, should be docs instead)

[julien-deramond]

Thanks for opening an issue @jhthompson :)

I am willing to open a PR to fix, but could not find source file to edit (is there a v5.0 branch to make the PR against?)

You can create a branch against our main branch and modify migration.md.
If the modification is approved/merged, the latest version of the 5.x documentation will contain your modification in "Migrating to v5".
However I'm not sure if we will be able to modify as well the already shipped migration guide for 5.1 and 5.0.

[jhthompson]

Thanks for opening an issue @jhthompson :)

I am willing to open a PR to fix, but could not find source file to edit (is there a v5.0 branch to make the PR against?)

You can create a branch against our main branch and modify migration.md. If the modification is approved/merged, the latest version of the 5.x documentation will contain your modification in "Migrating to v5". However I'm not sure if we will be able to modify as well the already shipped migration guide for 5.1 and 5.0.

Sounds good! IMO it really should be applied to the 5.0 migration guide as it is broken at that version, but if there's no way to update the already shipped migration guide then adding it to the latest 5.x documentation is the next best thing.

[jhthompson]

Ahh I see that the new migrations docs are for all of 5.x, not just >5.0. I think this is the appropriate place to add this then.