-
Notifications
You must be signed in to change notification settings - Fork 41
Update Top HTML/CSS Interoperability pain points for 2025 #2161
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
Conversation
|
Any ideas why the build is failing? Do I need permissions on this repo? |
My trivial PR is also having errors. I'm not seeing the cause yet, but I'll try to look into it today. |
|
The go linter we use released an update The devcontainer config does not pin the version for the linter, only the go version: webstatus.dev/.devcontainer/devcontainer.json Lines 20 to 22 in 8ee1375
As a result, when the CI ran, it would install the latest version which Typically, we have been okay with the I will put a fix up shortly to pin to the previous version. Then when I update the go version in the future, I will also bump the linter to the latest version and fix those errors. |
Thanks @jcscottiii . I added the same fix as #2172 to this PR so we could get CI to run, but let's merge your PR first for git history and then this one. |
|
Thank you |
|
"Berry"? I know that's how the American's pronounce it but definitely not how it's spelt! :-) |
Based on these links:
HTML
CSS