Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump jupyter-core from 4.10.0 to 4.11.2 #613

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Bump jupyter-core from 4.10.0 to 4.11.2 #613

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 30, 2022

Bumps jupyter-core from 4.10.0 to 4.11.2.

Release notes

Sourced from jupyter-core's releases.

4.11.1

What's Changed

Full Changelog: jupyter/jupyter_core@4.11.0...4.11.1

4.11.0

What's Changed

New Contributors

Full Changelog: jupyter/jupyter_core@4.10.0...4.11.0

Changelog

Sourced from jupyter-core's changelog.

Changes in jupyter-core

5.1.0

(Full Changelog)

Enhancements made

Maintenance and upkeep improvements

Documentation improvements

Contributors to this release

(GitHub contributors page for this release)

@​blink1073 | @​davidbrochart | @​pre-commit-ci

5.0.0

(Full Changelog)

Major Changes

Prefer Environment Level Configuration

We now make the assumption that if we are running in a virtual environment, we should prioritize the environment-level sys.prefix over the user-level paths. Users can opt out of this behavior by setting JUPYTER_PREFER_ENV_PATH, which takes precedence over our autodetection.

Migrate to Standard Platform Directories

In version 5, we introduce a JUPYTER_PLATFORM_DIRS environment variable to opt in to using more appropriate platform-specific directories. We raise a deprecation warning if the variable is not set. In version 6, JUPYTER_PLATFORM_DIRS will be opt-out. In version 7, we will remove the environment variable checks and old directory logic.

Drop Support for Python 3.7

We are dropping support for Python 3.7 ahead of its official end of life, to reduce maintenance burden as we add support for Python 3.11.

Enhancements made

... (truncated)

Commits

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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
Bump jupyter-core from 4.10.0 to 4.11.2
bb29cc6 
Bumps [jupyter-core](https://github.com/jupyter/jupyter_core) from 4.10.0 to 4.11.2.
- [Release notes](https://github.com/jupyter/jupyter_core/releases)
- [Changelog](https://github.com/jupyter/jupyter_core/blob/main/CHANGELOG.md)
- [Commits](jupyter/jupyter_core@4.10.0...4.11.2)

---
updated-dependencies:
- dependency-name: jupyter-core
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Nov 30, 2022
@sesheta
Copy link
Contributor

sesheta commented Nov 30, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chauhankaranraj for approval by writing /assign @chauhankaranraj in a comment. For more information see:The Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sesheta sesheta added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 30, 2022
@sesheta
Copy link
Contributor

sesheta commented Nov 30, 2022

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a aicoe-aiops member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@MichaelClifford
Copy link
Member

Our Model Predicts this PR to be in category [8]

2 similar comments
@MichaelClifford
Copy link
Member

Our Model Predicts this PR to be in category [8]

@github-actions
Copy link

github-actions bot commented Dec 7, 2022

Our Model Predicts this PR to be in category [8]

@MichaelClifford
Copy link
Member

This PR is predicted to merge in the time frame '2 days, 23:40:00 - 5 days, 19:16:00' by our model.

2 similar comments
@github-actions
Copy link

github-actions bot commented Dec 7, 2022

This PR is predicted to merge in the time frame '2 days, 23:40:00 - 5 days, 19:16:00' by our model.

@github-actions
Copy link

github-actions bot commented Dec 8, 2022

This PR is predicted to merge in the time frame '2 days, 23:40:00 - 5 days, 19:16:00' by our model.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@MichaelClifford MichaelClifford Awaiting requested review from MichaelClifford MichaelClifford is a code owner

@durandom durandom Awaiting requested review from durandom durandom is a code owner

@tumido tumido Awaiting requested review from tumido tumido is a code owner

@Shreyanand Shreyanand Awaiting requested review from Shreyanand

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@sesheta @MichaelClifford