fix(i18n): regression bug: i18n/<path> should always use locale key/id, not htmlLang#11979
Merged
Merged
Conversation
…tifier for path, never htmlLang #11952
slorber
added
pr: bug fix
✅ [V2]
To edit notification comments on pull requests, go to your Netlify project configuration. |
7 tasks
|
Size Change: 0 B Total Size: 12 MB ℹ️ View Unchanged
|
⚡️ Lighthouse report for the deploy preview of this PR
|
|
Size Change: 0 B Total Size: 12.5 MB ℹ️ View Unchanged
|
slorber
added a commit
that referenced
this pull request
Apr 30, 2026
fix(i18n): regression bug: `i18n/<path>` should always use locale key/id, not `htmlLang` (#11979)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Fix #11952
For sites using
localeConfigs['fr'].htmlLang = 'fr-FR, upgrading from v3.9 to v3.10 would change the i18n path fromi18n/frtoi18n/fr-FRThis was an unexpected breaking change coming from #11550
This reverts to the former behavior. Will be backported to v3.10.1 asap.
Test Plan
Unit tests