chore: update pricing data #362
Open
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
requested review from
LiuJi-Jim and
d-bytebase
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
force-pushed
the
update-pricing-data
branch
from
0efe26b to
3ff2c54
Compare
github-actions
bot
force-pushed
the
update-pricing-data
branch
from
3ff2c54 to
ae0efec
Compare
github-actions
bot
force-pushed
the
update-pricing-data
branch
from
ae0efec to
79e2ca0
Compare
github-actions
bot
force-pushed
the
update-pricing-data
branch
from
79e2ca0 to
4ad8974
Compare
github-actions
bot
force-pushed
the
update-pricing-data
branch
from
4ad8974 to
64ea69d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR means that our GitHub Action CronJob has detected an update to the pricing data.
This is a fairly rare event, so if anyone sees this PR, please check the results of the actions run first.
Before merging this PR, make sure the actions logs are as expected.