Skip to content

Conversation

@agriyakhetarpal
Copy link
Member

@agriyakhetarpal agriyakhetarpal commented Dec 5, 2025

This PR tries to recreate #294 but with jlpm handling things instead of yarn or otherwise. The pre-commit failure will be handled by #296.

@agriyakhetarpal agriyakhetarpal added maintenance This PR performs maintenance for the repository dependencies Pull requests that update a dependency file labels Dec 5, 2025
agriyakhetarpal and others added 3 commits December 10, 2025 14:42
Co-authored-by: Michał Krassowski <5832902+krassowski@users.noreply.github.com>
@github-actions
Copy link
Contributor

🚀 PR Environment Deployment Started

Infrastructure deployment has been triggered after all checks passed.

Backend Version: latest

Frontend Ref: 60cb2f76b3360ab738b9f2978a3f962c674e227f

You can monitor the deployment progress in the infrastructure repository.

📜 Previous Deployments
Timestamp Backend Frontend
2025-12-05T05:35:16.113Z latest 9d19d87

Deployment initiated at 2025-12-10T09:37:47.623Z

@agriyakhetarpal agriyakhetarpal enabled auto-merge (squash) December 10, 2025 10:14
Copy link
Collaborator

@krassowski krassowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking a bit more into this:

  • I think it should be possible to avoid the resolution pin - there are patched versions on both 4.x and 3.x branches of js-yaml
  • why do we need the 3.x one and why did it not break? I think because it is only used by a babel plugin used for unit tests and we don't really have unit tests

describe('jupytereverywhere', () => {

My suggestion would be to drop the resolution pin AND:

  • just use jlpm upgrade-interactive to bump the versions granularly OR
  • drop the unit tests machinery altogether since we are testing everything via playwright (which makes sense for this project)

Anyways, since the resolution pin as is has no bearing on the runtime I am approving this - the follow up work can be done in a separate PR.

@agriyakhetarpal agriyakhetarpal merged commit 1407891 into JupyterEverywhere:main Dec 10, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file maintenance This PR performs maintenance for the repository

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants