chore(pricing): vendor ai-price-index v2026.07.09-43f905c#39
Merged
Conversation
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.
Automated pin bump: re-vendors the ai-price-index dataset to
v2026.07.09-43f905c.What changed
internal/pricing/PINNED_TAG->v2026.07.09-43f905cinternal/pricing/index/**+PROVENANCE.jsonre-vendored from that tag (sha256 provenance refreshed)internal/pricing/table_gen.goregenerated from the new vendored dataWhy this is safe to auto-merge
The pricing was already human-verified upstream in the dataset repo, which is the source of truth and owns the daily pricing audit. This PR does not introduce a new rate by hand; it only re-vendors the already-verified data into the binary's embedded table.
CI proves the embedding is faithful before this can merge:
pricing-codegenregeneratestable_gen.gofrom the vendored artifacts (offline) and fails on any drift, so the embedded table provably matches the dataset.internal/pricingran green in this job and run again in CI.BudgetClaw stays zero-key, zero-latency, and fully offline: the price table is embedded at build time, there is no runtime network access.
No forced migration
Pricing is point-in-time. A new rate adds a new interval and does not change rows already priced at their then-effective rate, so this routine refresh does not require users to run
backfill --rebuild. Only a correction to a past rate would.Opened by
.github/workflows/pricing-bump.yml.