build-models: bump pget pin from v0.8.2 to v0.11.1#9
Open
lucataco wants to merge 1 commit into
Open
Conversation
The build-models skill pins pget to v0.8.2, but the latest pget release is v0.11.1 (https://github.com/replicate/pget/releases). New cog models following this skill should pull the current release, not a 3+ year old one. Note the asset filename also changed case in newer releases: v0.8.2: pget_linux_x86_64 (lowercase) v0.11.1: pget_Linux_x86_64 (capital L) so the URL update is not a pure version bump.
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
build-modelsskill currently pins pget to v0.8.2, but the latest pget release is v0.11.1. New cog models following the skill should pull the current release.Diff
Heads up: asset filename case changed between releases
The release asset naming changed:
pget_linux_x86_64(lowercasel)pget_Linux_x86_64(capitalL)So this is not a pure version bump — both the version segment and the filename casing need to change or curl will 404. Verified the v0.11.1 URL returns HTTP 302 (redirect to the release asset).
The text-guidance bullet under Guidelines is also updated to reference v0.11.1.