Space: bump build stamp to v6.1-flywheel#23
Open
trinitron88 wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
The Space UI still showed
v5.2.0-enasrbecause the build stamp is (intentionally) defined in source and we never bumped it while shipping V6. Now readsv6.1-flywheel, matching the deployed model.After merging, redeploy the app to pick it up: re-run the notebook's publish cell (it'll skip nothing this time — code change means the Space rebuilds), or just
%run hf_space/deploy_colab.pyfrom a Colab with the write token set.🤖 Generated with Claude Code