mirror of https://github.com/thegeeklab/docker-tidy.git synced 2026-09-10 09:02:44 +00:00

T

renovate[bot] de9bfd53a9 build(deps): update dependency dateparser to v1.4.3 (#1130 )

This PR contains the following updates:

| Package | Change |
[Age](https://docs.renovatebot.com/merge-confidence/) |
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [dateparser](https://redirect.github.com/scrapinghub/dateparser)
([changelog](https://dateparser.readthedocs.io/en/latest/history.html))
| `1.4.2` → `1.4.3` |
![age](https://developer.mend.io/api/mc/badges/age/pypi/dateparser/1.4.3?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/dateparser/1.4.2/1.4.3?slim=true)
|

---

### Release Notes

<details>
<summary>scrapinghub/dateparser (dateparser)</summary>

###
[`v1.4.3`](https://redirect.github.com/scrapinghub/dateparser/blob/HEAD/HISTORY.rst#143-2026-09-03)

[Compare
Source](https://redirect.github.com/scrapinghub/dateparser/compare/v1.4.2...v1.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
([#&#8203;1346](https://redirect.github.com/scrapinghub/dateparser/issues/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
([#&#8203;1371](https://redirect.github.com/scrapinghub/dateparser/issues/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
([#&#8203;1366](https://redirect.github.com/scrapinghub/dateparser/issues/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
([#&#8203;1370](https://redirect.github.com/scrapinghub/dateparser/issues/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
([#&#8203;1365](https://redirect.github.com/scrapinghub/dateparser/issues/1365))

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - At any time (no schedule defined)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/thegeeklab/docker-tidy).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC42MS4xIiwidXBkYXRlZEluVmVyIjoiNDQuNjEuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>