AJDA-2169 - Switch autosave to data-loader internal endpoint #32
Merged
Conversation
07c9f83 to
2286e66
Compare
d352e4c to
e427138
Compare
… use /internal/save endpoint
e427138 to
2c9a449
Compare
ErikZigo
commented
Feb 15, 2026
ErikZigo
commented
Feb 15, 2026
odinuv
approved these changes
Feb 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release Notes
Change Type
Minor
Impact Analysis
Customer Communication Plans
No external communication needed. The user experience is identical — notebooks continue to autosave transparently.
Justification
Jupyter sandbox containers currently require a Storage API token for notebook autosave, which is a security concern. This change is step 2 of a multi-phase effort to remove storage tokens from sandbox containers entirely, as part of the Sandbox API deprecation initiative.
Deployment Plan
Rollback Plan
Since this release has no effect on its own, no rollback is needed at this stage. If issues arise after step 3 (new JupyterLab images), rebuild the images with the previous notebook-utils version 2.2.0 to restore the original token-based autosave path. No data loss or service disruption expected.
Post-Release Support Plan