Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About update interval for Runtime compatibility website #123

Open
nabetti1720 opened this issue May 13, 2024 · 3 comments
Open

About update interval for Runtime compatibility website #123

nabetti1720 opened this issue May 13, 2024 · 3 comments

Comments

@nabetti1720
Copy link

Hello to all contributors.

First of all, thank you for publishing this Runtime compatibility website where we can get great insight.

I am currently working with the LLRT project in a small way as a contributor.
LLRT just released v0.1.13-beta last week.

There have been some improvements in terms of WinterCG compliance, and we thought we could measure the degree of improvement on this website, but it appears that information on the new version has not yet been updated.

What is the update interval for this website?

I apologize if you are experiencing problems with the update procedure and have already identified this as an issue.

@nabetti1720 nabetti1720 changed the title About update interval for this website About update interval for Runtime compatibility website May 13, 2024
@ascorbic
Copy link
Collaborator

It's updated whenever we merge one of the update PRs 😁
I just did that, which updates LLRT to 0.1.13-beta. In general, if you look at the latest "update runtime compat data" PR you should see the latest version

@nabetti1720
Copy link
Author

Hi @ascorbic . Thank you very much for your quick response!
We have seen that the website has been updated here as well.

PRs are generated automatically, but human judgment comes into play as to whether to merge them or not?

Additionally, how do I request to have the latest data merged in the future?
Should I make a mentions in the comments section of the PR that is automatically generated?

@ascorbic
Copy link
Collaborator

Honestly we should probably just auto-merge them. But yes, if there's been an update then check the PR, see if it shows up in the deploy preview, and if it is then just add a comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants