Skip to content

fix(deps): update module golang.org/x/net to v0.50.0 (main)#14414

Open
renovate-sh-app[bot] wants to merge 1 commit intomainfrom
deps-update/main-golang.org-x-net-0.x
Open

fix(deps): update module golang.org/x/net to v0.50.0 (main)#14414
renovate-sh-app[bot] wants to merge 1 commit intomainfrom
deps-update/main-golang.org-x-net-0.x

Conversation

@renovate-sh-app
Copy link
Contributor

@renovate-sh-app renovate-sh-app bot commented Feb 19, 2026

This PR contains the following updates:

Package Change Age Confidence
golang.org/x/net v0.49.0v0.50.0 age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.

| datasource | package          | from    | to      |
| ---------- | ---------------- | ------- | ------- |
| go         | golang.org/x/net | v0.49.0 | v0.50.0 |


Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
@renovate-sh-app renovate-sh-app bot requested a review from stevesg as a code owner February 19, 2026 02:08
@renovate-sh-app renovate-sh-app bot requested a review from a team as a code owner February 19, 2026 02:08
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is ON. A Cloud Agent has been kicked off to fix the reported issue.

FrameGoAway: parseGoAwayFrame,
FrameWindowUpdate: parseWindowUpdateFrame,
FrameContinuation: parseContinuationFrame,
FramePriorityUpdate: parsePriorityUpdateFrame,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nil parser panic for HTTP/2 frame types 0xa-0xf

High Severity

Adding FramePriorityUpdate at 0x10 (decimal 16) expands the frameParsers array to 17 elements, leaving indices 10–15 as nil. The typeFrameParser function returns frameParsers[t] for any t < len(frameParsers), so frame types 0x0a0x0f now return nil instead of parseUnknownFrame. This nil parser is immediately invoked at the call site in ReadFrameForHeader, causing a panic. Frame types 0x0a (ALTSVC) and 0x0c (ORIGIN) are legitimate registered HTTP/2 frame types that real peers may send. This is a known upstream regression (Go issue #77652).

Additional Locations (1)

Fix in Cursor Fix in Web

@cursor
Copy link

cursor bot commented Feb 19, 2026

Bugbot Autofix prepared fixes for 1 of the 1 bugs found in the latest run.

  • ✅ Fixed: Nil parser panic for HTTP/2 frame types 0xa-0xf
    • Added a nil check in typeFrameParser to return parseUnknownFrame instead of nil for uninitialized frame parser indices 10-15.

Create PR

Or push these changes by commenting:

@cursor push ae6bb77ee2
Preview (ae6bb77ee2)
diff --git a/vendor/golang.org/x/net/http2/frame.go b/vendor/golang.org/x/net/http2/frame.go
--- a/vendor/golang.org/x/net/http2/frame.go
+++ b/vendor/golang.org/x/net/http2/frame.go
@@ -145,7 +145,9 @@
 
 func typeFrameParser(t FrameType) frameParser {
 	if int(t) < len(frameParsers) {
-		return frameParsers[t]
+		if f := frameParsers[t]; f != nil {
+			return f
+		}
 	}
 	return parseUnknownFrame
 }

Copy link
Contributor

@aknuds1 aknuds1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This release has a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments