Does Kaggle provide automatic safety checks for rolling back dataset versions after schema changes?
When a dataset owner modifies a schema and creates a new version, Kaggle lets them later set an earlier version as the active one for new notebooks. Existing notebooks continue to reference the version they were originally tied to, but any notebook that relies on the active version may suddenly encounter missing columns or altered types after a rollback. Bec
kaggle