Bump dateparser from 1.4.1 to 1.4.3

[dependabot]

Bumps dateparser from 1.4.1 to 1.4.3.

Release notes

Sourced from dateparser's releases.

1.4.3

Fixes:

• Make parsing thread-safe: parsing from several threads no longer raises an intermittent KeyError from the shared language caches, and a DATE_ORDER or RELATIVE_BASE value meant for one parse no longer leaks into the settings that other parses read, where it could make them return a wrong date (#1346)
• Do not share the language detector and the detected locale between search_dates() calls, so concurrent searches over text in different languages no longer return None or a date read in the wrong locale (#1371)
• Resolve the BST and HDT timezone abbreviations to the offsets the tz database gives them, UTC+1 (British Summer Time) and UTC-9 (Hawaii-Aleutian Daylight Time), instead of +11 and -9:30, which no zone goes by those names today; abbreviations that the tz database maps to more than one offset, such as CST and IST, keep their current offset. Text carrying these abbreviations keeps its wall clock but moves by 10 hours for BST and 30 minutes for HDT, which can put the parsed instant on a different day (#1366)
• Reject a %j (day of year) value that the parsed year does not have, instead of rolling it over into the next year, so "1999366" with date_formats=["%Y%j"] returns None rather than 2000-01-01. A format with no year directive is checked against the year strptime defaults to, 1900, which is not a leap year, so "366" with date_formats=["%j"] now returns None where it used to return January 1 (#1370)

Cleanups and internal improvements:

• Add CodSpeed benchmarks and a workflow that runs them, so a performance regression such as the quadratic backtracking fixed in 1.4.1 is reported on the pull request that introduces it (#1365)

1.4.2

New features

• Add an IGNORE_SURROUNDING_TEXT setting that, when enabled, retries parsing after ignoring leading and trailing words the language does not recognize, so a date wrapped in extra text such as "Published on 16/04/2019" is parsed (#1356)
• Add a strategy argument to search_dates() to choose the search strategy: the default "split" keeps the current behavior, while the new "ngram" strategy parses the longest sequences of tokens as dates for more predictable results on noisy text (#1351)

Fixes

• Do not read a two-digit number as a year once a later component has been found in year-first date orders, so the day in Japanese dates such as "4月20日" is no longer consumed as the year (#1358)
• Parse ISO 8601 dates (those starting with a four-digit year) in month-day order even when an explicit day-first language such as it or fr is given, without needing to set PREFER_LOCALE_DATE_ORDER to False (#1352)
• Honor PREFER_DATES_FROM and RELATIVE_BASE when parsing with custom date_formats that use a two-digit year (%y) (#1342)
• Honor the %j (day of year) directive in date_formats instead of overwriting the parsed month and day with the current date (#1345)

... (truncated)

Changelog

Sourced from dateparser's changelog.

1.4.3 (2026-09-03)

Fixes:

• Make parsing thread-safe: parsing from several threads no longer raises an intermittent KeyError from the shared language caches, and a DATE_ORDER or RELATIVE_BASE value meant for one parse no longer leaks into the settings that other parses read, where it could make them return a wrong date (#1346)
• Do not share the language detector and the detected locale between search_dates() calls, so concurrent searches over text in different languages no longer return None or a date read in the wrong locale (#1371)
• Resolve the BST and HDT timezone abbreviations to the offsets the tz database gives them, UTC+1 (British Summer Time) and UTC-9 (Hawaii-Aleutian Daylight Time), instead of +11 and -9:30, which no zone goes by those names today; abbreviations that the tz database maps to more than one offset, such as CST and IST, keep their current offset. Text carrying these abbreviations keeps its wall clock but moves by 10 hours for BST and 30 minutes for HDT, which can put the parsed instant on a different day (#1366)
• Reject a %j (day of year) value that the parsed year does not have, instead of rolling it over into the next year, so "1999366" with date_formats=["%Y%j"] returns None rather than 2000-01-01. A format with no year directive is checked against the year strptime defaults to, 1900, which is not a leap year, so "366" with date_formats=["%j"] now returns None where it used to return January 1 (#1370)

Cleanups and internal improvements:

• Add CodSpeed benchmarks and a workflow that runs them, so a performance regression such as the quadratic backtracking fixed in 1.4.1 is reported on the pull request that introduces it (#1365)

1.4.2 (2026-08-04)

New features:

• Add an IGNORE_SURROUNDING_TEXT setting that, when enabled, retries parsing after ignoring the leading and trailing words the language does not recognize, so a date wrapped in extra text such as "Published on 16/04/2019" is parsed (#1356)
• Add a strategy argument to search_dates() to choose the search strategy: the default "split" keeps the current behavior, while the new "ngram" strategy parses the longest sequences of tokens as dates for more predictable results on noisy text (#1351)

... (truncated)

Commits

• 9ce60b1 1.4.3 release (#1376)
• 27182cd Avoid shared language_detector and locale cache in search_dates (#1371)
• 6b5f17d Reject a %j day of year that the parsed year does not have (#271) (#1370)
• cd9bb13 Make thread-safe (#1346)
• de7b986 tests: add CodSpeed benchmarks (#1365)
• 764091d Fix timezone ambiguity using tz database (#1322) (#1366)
• b1f603e 1.4.2 release (#1361)
• ff3dcb9 Specify README header content as RST (#1360)
• d886e23 Parse dates wrapped in harmless extra text (Close #518) (#1356)
• 06ca032 Do not read the day as a two-digit year after the year position (#1358)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)