chore(release): record the 0.39.44 seed-snapshot timestamp - #127
Merged
Conversation
prepublishOnly regenerates the vendored LiteLLM seed on every publish, so the PR head and the published tarball diverge by one field unless it is committed. Inspected structurally before committing, as the release workflow requires: 2522 models before and after, zero added, zero removed, zero with changed rates. The only difference is _meta.generated_at. Anything else would have meant stopping to review rather than committing.
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.
Post-publish follow-up for #125.
prepublishOnlyregenerates the vendored LiteLLM seed on every publish, so the PR head and the published tarball diverge by one field unless it is committed.Inspected structurally before committing, as the release workflow requires rather than assuming:
_meta.generated_atTimestamp-only, which is the expected case. Anything touching model counts or rates would have meant stopping to review instead.
Also worth recording: the direct push to
mainwas rejected by branch protection, which is theenforce_adminsrule working as intended — so this trivial one-field change goes through a PR like everything else.