fix: Use FromContext(any) for multi-context retrieval in paseto, newrelic, and sentry

[Copilot]

• Remove *AnyContext helpers — FromContext, GetHubFromContext, MustGetHubFromContext each accept any
• Update tests to call context helpers directly with c.Context()
• Update READMEs (paseto, sentry, newrelic) for new (ctx any) signatures
• Fix newrelic README to use *nr.Transaction consistently with the alias in the signature block
• Update jwt README with alias comment and return type description (consistent with newrelic/sentry pattern)
• Standardize FromContext description phrasing across all READMEs (paseto, newrelic, sentry, jwt)

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• collector.newrelic.com
  • Triggering command: /tmp/go-build2399329134/b275/newrelic.test /tmp/go-build2399329134/b275/newrelic.test -test.paniconexit0 -test.count=1 -test.timeout=1m0s go1.25.0 -c=4 -nolocalimports -importcfg /tmp/go-build2399329134/b285/importcfg -pack /home/REDACTED/go/pkg/mod/golang.org/x/net@v0.51.0/trace/events.go /home/REDACTED/go/pkg/mod/golang.org/x/net@v0.51.0/trace/histogram.go abis�� ity/connectivity-p rg/toolchain@v0.google.golang.org/grpc/peer ux-amd64/pkg/tool/linux_amd64/vet --depth 8 m ux-amd64/pkg/too-trimpath (dns block)
  • Triggering command: /tmp/go-build882747594/b275/newrelic.test /tmp/go-build882747594/b275/newrelic.test -test.paniconexit0 -test.timeout=10m0s -test.count=1 -test.v=true rg/toolchain@v0.-p m 0.1-go1.25.0.lin-lang=go1.25 (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[gaby]

@copilot we only want to support FromContext with any, you do not need to add another helper.

[Copilot]

@copilot we only want to support FromContext with any, you do not need to add another helper.

Done in commit 23c5b92. Removed all *AnyContext helpers — FromContext, GetHubFromContext, and MustGetHubFromContext now each accept any directly, supporting fiber.Ctx, fiber.CustomCtx, *fasthttp.RequestCtx, and context.Context. READMEs updated accordingly.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• collector.newrelic.com
  • Triggering command: /tmp/go-build3506980738/b275/newrelic.test /tmp/go-build3506980738/b275/newrelic.test -test.paniconexit0 -test.count=1 -test.timeout=1m0s go1.25.0 -c=4 -nolocalimports -importcfg /tmp/go-build3506980738/b319/importcfg -pack /home/REDACTED/go/pkg/mod/google.golang.org/grpc@v1.79.1/balancer/pickfirst/pickfirst.go ux-amd64/pkg/too-trimpath abis�� rg/toolchain@v0.-p credential.helpegoogle.golang.org/grpc/keepalive ux-amd64/pkg/tool/linux_amd64/vet (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

This PR updates context-retrieval helper APIs in the paseto, newrelic, and sentry middlewares to accept any, enabling value retrieval from multiple context types (e.g., fiber.Ctx vs c.Context() when PassLocalsToContext is enabled), and adjusts README/docs accordingly.

Changes:

• Document/clarify GetHubFromContext / MustGetHubFromContext behavior in sentry (panic semantics).
• Document newrelic.FromContext(ctx any) as supporting multiple context types.
• Disambiguate README “Signature” sections using package aliases to avoid confusion with upstream SDK packages.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
v3/sentry/sentry.go	Adds explicit doc note that MustGetHubFromContext panics when hub is missing.
v3/sentry/README.md	Updates signature docs to disambiguate middleware package vs Sentry SDK types.
v3/newrelic/fiber.go	Updates FromContext doc comment to note supported context types.
v3/newrelic/README.md	Updates signature docs/examples with aliases; clarifies PassLocalsToContext retrieval.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gaby]

@copilot double check all the docs again.

[Copilot]

@copilot double check all the docs again.

Done in commit 4d6722c. The only inconsistency across all three READMEs was *newrelic.Transaction vs *nr.Transaction in the newrelic README — that's now fixed. Everything else (paseto, sentry) looks correct.

[gaby]

@copilot make sure every model using FromContext had their docs updated

[Copilot]

@copilot make sure every model using FromContext had their docs updated

Done in commit 90953bf. The jwt package was the only one missing docs — its README now has the // jwt "github.com/golang-jwt/jwt/v5" alias comment in the signature block and a prose description of the return type, consistent with the newrelic and sentry READMEs. All four modules (paseto, newrelic, sentry, jwt) now have fully updated FromContext docs.

[gaby]

@copilot also check the docs for otel and jwt.

[Copilot]

@copilot also check the docs for otel and jwt.

Checked both:

• jwt: Already updated in commit 90953bf — the signature block has the // jwt "github.com/golang-jwt/jwt/v5" alias comment and the prose description mentions the return type.
• otel: Has no FromContext-style helper to document. It stores a tracer internally via a private key, and exposes spans to callers through the standard OTel API (oteltrace.SpanFromContext(c.Context())). The otel README's Signature section is correct as-is.

All modules that expose a FromContext-style helper (paseto, newrelic, sentry, jwt) now have updated docs.

[gaby]

@copilot in each readme, be consistent about this part:

`FromContext` accepts a `fiber.Ctx`, `fiber.CustomCtx`, `*fasthttp.RequestCtx`, or a standard `context.Context` (e.g. the value returned by `c.Context()` when `PassLocalsToContext` is enabled)

You have the same messages in different ways across README files; it should be the same as above instead.

[Copilot]

@copilot in each readme, be consistent about this part:

...

Fixed in commit f330648. The paseto README had a different phrasing at the FromContext usage section — it now uses the canonical sentence consistently across all READMEs (paseto, newrelic, sentry, jwt).

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.