Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Apr 29, 2022

This PR contains the following updates:

Package Change Age Confidence
nltk (source) == 3.6.2 -> ==3.9.1 age confidence

Release Notes

nltk/nltk (nltk)

v3.9.1

Compare Source

v3.9

Compare Source

v3.8.1

Compare Source

v3.8

Compare Source

v3.7

Compare Source

v3.6.7

Compare Source

v3.6.6

Compare Source

v3.6.5

Compare Source

v3.6.4

Compare Source

v3.6.3

Compare Source


Configuration

📅 Schedule: 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/nltk-3.x branch from b19b4f4 to 8a4c7cd Compare September 25, 2022 15:15
@renovate renovate bot changed the title Update dependency nltk to v3.7 chore(deps): update dependency nltk to v3.7 Sep 25, 2022
@renovate renovate bot force-pushed the renovate/nltk-3.x branch from 8a4c7cd to ae1e8dd Compare November 20, 2022 15:02
@renovate renovate bot force-pushed the renovate/nltk-3.x branch from ae1e8dd to 6e8dba8 Compare March 11, 2023 21:37
@renovate renovate bot changed the title chore(deps): update dependency nltk to v3.7 chore(deps): update dependency nltk to v3.8.1 Mar 11, 2023
@fairdataihub-bot
Copy link

Thanks for making updates to your pull request. Our team will take a look and provide feedback as soon as possible. Please wait for any GitHub Actions to complete before editing your pull request. If you have any additional questions or concerns, feel free to let us know. Thank you for your contributions!

3 similar comments
@fairdataihub-bot
Copy link

Thanks for making updates to your pull request. Our team will take a look and provide feedback as soon as possible. Please wait for any GitHub Actions to complete before editing your pull request. If you have any additional questions or concerns, feel free to let us know. Thank you for your contributions!

@fairdataihub-bot
Copy link

Thanks for making updates to your pull request. Our team will take a look and provide feedback as soon as possible. Please wait for any GitHub Actions to complete before editing your pull request. If you have any additional questions or concerns, feel free to let us know. Thank you for your contributions!

@fairdataihub-bot
Copy link

Thanks for making updates to your pull request. Our team will take a look and provide feedback as soon as possible. Please wait for any GitHub Actions to complete before editing your pull request. If you have any additional questions or concerns, feel free to let us know. Thank you for your contributions!

@renovate renovate bot changed the title chore(deps): update dependency nltk to v3.8.1 chore(deps): update dependency nltk to v3.8.2 Aug 10, 2024
@renovate renovate bot force-pushed the renovate/nltk-3.x branch 2 times, most recently from d04ee65 to 0e0e1b4 Compare August 15, 2024 09:20
@renovate renovate bot changed the title chore(deps): update dependency nltk to v3.8.2 chore(deps): update dependency nltk to v3.8.1 Aug 15, 2024
@renovate renovate bot force-pushed the renovate/nltk-3.x branch from 0e0e1b4 to 43ebf12 Compare August 18, 2024 07:36
@renovate renovate bot changed the title chore(deps): update dependency nltk to v3.8.1 chore(deps): update dependency nltk to v3.9 Aug 18, 2024
@renovate renovate bot force-pushed the renovate/nltk-3.x branch from 43ebf12 to 855fa04 Compare August 18, 2024 20:29
@renovate renovate bot changed the title chore(deps): update dependency nltk to v3.9 chore(deps): update dependency nltk to v3.9.1 Aug 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant