-
Notifications
You must be signed in to change notification settings - Fork 119
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
Mark that we're intentionally on CT v1. #712
Conversation
Can we have a reviewer for this? If this is a minor update for SXG and don't need any intense review, I am happy to do a rubber-stamp. |
This is primarily to fix the build, but it's not the obvious fix after one RFC obsoletes another. I checked with Chrome Security, and it sounds like we don't have a plan to move to v2, so signed exchanges shouldn't either. |
Ah, I got the context. It seems this is a fix for #704 (or any other build error maybe). It sounds the situation is complex than I expected. Anyway, thanks for working on this! Much appreciated. |
It's part of #704: I think the bikeshed bit of the action that's failing there is unnecessary, but I can't be sure while this action is failing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Let me merge this. |
SHA: b109d94 Reason: push, by @hayatoito Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: b109d94 Reason: push, by @hayatoito Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: b109d94 Reason: push, by @hayatoito Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: b109d94 Reason: push, by @hayatoito Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: b109d94 Reason: push, by @hayatoito Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Preview | Diff