DHBW/TelegramAktienBot
1
0
Fork 0
Code Issues 6 Pull Requests 26 Actions Packages Projects Releases Wiki Activity

Bump tzlocal from 2.1 to 4.2 in /telegram_bot #95

Closed
dependabot[bot] wants to merge 1 commits from dependabot/pip/telegram_bot/tzlocal-4.2 into main
pull from: dependabot/pip/telegram_bot/tzlocal-4.2
merge into: DHBW:main
Conversation 1 Commits 1 Files Changed 1 +1 -1
dependabot[bot] commented 2022-04-26 09:34:27 +00:00 (Migrated from github.com)
Copy Link

Bumps tzlocal from 2.1 to 4.2.

Changelog

Sourced from tzlocal's changelog.

4.2 (2022-04-02)

  • If TZ environment variable is set to /etc/localhost, and that's a link to a zoneinfo file, then tzlocal will now find the timezone name, and not just return a localtime TZ object.

4.1 (2021-10-29)

  • No changes from 4.1b1.

4.1b1 (2021-10-28)

  • It turns out a lot of Linux distributions make the links between zoneinfo aliases backwards, so instead of linking GB to Europe/London it actually links the other way. When /etc/localtime then links to Europe/London, and you also have a config file saying Europe/London, the code that checks if /etc/localtime is a symlink ends up at GB instead of Europe/London and we get an error, as it thinks GB and Europe/London are different zones.

    So now we check the symlink of all timezones in the uniqueness test. We still return the name in the config file, though, so you would only get GB or Zulu returned as the time zone instead of Europe/London or UTC if your only configuration is the /etc/localtime symlink, as that's checked last, and tzlocal will return the first configuration found.

  • The above change also means that GMT and UTC are no longer seen as synonyms, as zoneinfo does not see them as synonyms. This might be controversial, but you just have to live with it. Pick one and stay with it. ;-)

4.0.2 (2021-10-26)

  • Improved the error message when you had a conflict including a /etc/localtime symlink.

4.0.1 (2021-10-19)

  • A long time bug in Ubuntu docker images seem to not get fixed, so I added a workaround.

4.0.1b1 (2021-10-18)

... (truncated)

Commits
  • b2c0f73 Preparing release 4.2
  • 5cc5d42 Preparing for release
  • 7e12636 Support TZ pointing to a link
  • d5fb741 Back to development: 4.2
  • ca5eb5e Preparing release 4.1
  • 0ea226b Back to development: 4.1b2
  • 572d7ad Preparing release 4.1b1
  • 4d25c45 Redo the synonym handling completely, and now only use zoneinfo symlinks
  • f1049d2 Back to development: 4.0.3
  • 29ea845 Preparing release 4.0.2
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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)
Bumps [tzlocal](https://github.com/regebro/tzlocal) from 2.1 to 4.2. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/regebro/tzlocal/blob/master/CHANGES.txt">tzlocal's changelog</a>.</em></p> <blockquote> <h2>4.2 (2022-04-02)</h2> <ul> <li>If TZ environment variable is set to /etc/localhost, and that's a link to a zoneinfo file, then tzlocal will now find the timezone name, and not just return a localtime TZ object.</li> </ul> <h2>4.1 (2021-10-29)</h2> <ul> <li>No changes from 4.1b1.</li> </ul> <h2>4.1b1 (2021-10-28)</h2> <ul> <li> <p>It turns out a lot of Linux distributions make the links between zoneinfo aliases backwards, so instead of linking GB to Europe/London it actually links the other way. When /etc/localtime then links to Europe/London, and you also have a config file saying Europe/London, the code that checks if /etc/localtime is a symlink ends up at GB instead of Europe/London and we get an error, as it thinks GB and Europe/London are different zones.</p> <p>So now we check the symlink of all timezones in the uniqueness test. We still return the name in the config file, though, so you would only get GB or Zulu returned as the time zone instead of Europe/London or UTC if your only configuration is the /etc/localtime symlink, as that's checked last, and tzlocal will return the first configuration found.</p> </li> <li> <p>The above change also means that GMT and UTC are no longer seen as synonyms, as zoneinfo does not see them as synonyms. This might be controversial, but you just have to live with it. Pick one and stay with it. ;-)</p> </li> </ul> <h2>4.0.2 (2021-10-26)</h2> <ul> <li>Improved the error message when you had a conflict including a /etc/localtime symlink.</li> </ul> <h2>4.0.1 (2021-10-19)</h2> <ul> <li>A long time bug in Ubuntu docker images seem to not get fixed, so I added a workaround.</li> </ul> <p>4.0.1b1 (2021-10-18)</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/regebro/tzlocal/commit/b2c0f73d9d4decbf2e96dde334577fd133770791"><code>b2c0f73</code></a> Preparing release 4.2</li> <li><a href="https://github.com/regebro/tzlocal/commit/5cc5d4226f768b03d9314bd6a1841937d96fbffe"><code>5cc5d42</code></a> Preparing for release</li> <li><a href="https://github.com/regebro/tzlocal/commit/7e1263699fa33fd0ce7b381b2d6869b1016ec591"><code>7e12636</code></a> Support TZ pointing to a link</li> <li><a href="https://github.com/regebro/tzlocal/commit/d5fb741969269c1cc0f4c1a87a66c10426863761"><code>d5fb741</code></a> Back to development: 4.2</li> <li><a href="https://github.com/regebro/tzlocal/commit/ca5eb5ebe244fa5a8c673a6d74100b5a60037a91"><code>ca5eb5e</code></a> Preparing release 4.1</li> <li><a href="https://github.com/regebro/tzlocal/commit/0ea226bbe097f15c2549bb33fcb27e344fb219b3"><code>0ea226b</code></a> Back to development: 4.1b2</li> <li><a href="https://github.com/regebro/tzlocal/commit/572d7ad452531a6c6befb50027359420aa704e47"><code>572d7ad</code></a> Preparing release 4.1b1</li> <li><a href="https://github.com/regebro/tzlocal/commit/4d25c45a9d2e53efc8af56b7b77c32028658016e"><code>4d25c45</code></a> Redo the synonym handling completely, and now only use zoneinfo symlinks</li> <li><a href="https://github.com/regebro/tzlocal/commit/f1049d2a0db957c5e10f94e62a7ebda3b2aee29f"><code>f1049d2</code></a> Back to development: 4.0.3</li> <li><a href="https://github.com/regebro/tzlocal/commit/29ea845a281dc7d1c2e73123f9798ba2960d90bd"><code>29ea845</code></a> Preparing release 4.0.2</li> <li>Additional commits viewable in <a href="https://github.com/regebro/tzlocal/compare/2.1...4.2">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tzlocal&package-manager=pip&previous-version=2.1&new-version=4.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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) </details>
dependabot[bot] commented 2022-05-12 17:17:46 +00:00 (Migrated from github.com)
Copy Link

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
dependencies
Pull requests that update a dependency file
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
invalid
This doesn't seem right
javascript
Pull requests that update Javascript code
python
Pull requests that update Python code
question
Further information is requested
wontfix
This will not be worked on
No Label
dependencies
python
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
H4CK3R-01 renovate
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DHBW/TelegramAktienBot#95
No description provided.
Delete Branch "dependabot/pip/telegram_bot/tzlocal-4.2"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?