Skip to content

Feat/observability package GitHub#1835

Open
LeonardoVieira1630 wants to merge 6 commits intodevfrom
feat/observability_package_github
Open

Feat/observability package GitHub#1835
LeonardoVieira1630 wants to merge 6 commits intodevfrom
feat/observability_package_github

Conversation

@LeonardoVieira1630
Copy link
Copy Markdown
Member

@LeonardoVieira1630 LeonardoVieira1630 commented Apr 23, 2026

Summary

Prepares @anticapture/observability for publishing to npm and restructures its OpenTelemetry dependency so consumers share a single @opentelemetry/api instance. Bumps the package to 1.0.1 and wires each consuming app to depend on @opentelemetry/api directly to satisfy the new peer dependency.

Changes

  • packages/observability/package.json: bump version to 1.0.1; add files: ["dist"], publishConfig.access: public, and repository metadata for npm publishing.
  • packages/observability/package.json: move @opentelemetry/api from dependencies to devDependencies + peerDependencies to avoid duplicate tracer/meter instances in consumers.
  • apps/address-enrichment, apps/api-gateway, apps/gateful, apps/offchain-indexer: add @opentelemetry/api@^1.9.0 as a direct dependency to satisfy the new peer requirement.
  • pnpm-lock.yaml: regenerated to reflect the dependency reshuffling.

@railway-app
Copy link
Copy Markdown

railway-app Bot commented Apr 23, 2026

This PR was not deployed automatically as @LeonardoVieira1630 does not have access to the Railway project.

In order to get automatic PR deploys, please add @LeonardoVieira1630 to your workspace on Railway.

@LeonardoVieira1630 LeonardoVieira1630 self-assigned this Apr 23, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 23, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
anticapture Error Error Apr 24, 2026 8:59pm
anticapture-storybook Ready Ready Preview, Comment Apr 24, 2026 8:59pm

Request Review

@claude
Copy link
Copy Markdown

claude Bot commented Apr 23, 2026

Claude encountered an error —— View job


I'll analyze this and get back to you.

@LeonardoVieira1630 LeonardoVieira1630 marked this pull request as ready for review April 24, 2026 17:24
@claude
Copy link
Copy Markdown

claude Bot commented Apr 24, 2026

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 553bda1738

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread pnpm-lock.yaml
"@apollo/client":
specifier: ^3.13.8
version: 3.14.0(@types/react@19.2.8)(graphql-ws@6.0.7(crossws@0.3.5)(graphql@16.13.1)(ws@8.18.0(bufferutil@4.0.9)(utf-8-validate@5.0.10)))(graphql@16.13.1)(react-dom@19.2.3(react@19.2.3))(react@19.2.3)
version: 3.14.0(@types/react@19.2.8)(graphql-ws@6.0.7(crossws@0.3.5)(graphql@16.13.1)(ws@7.5.10(bufferutil@4.0.9)(utf-8-validate@5.0.10)))(graphql@16.13.1)(react-dom@19.2.3(react@19.2.3))(react@19.2.3)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep dashboard websocket peer on ws@^8

This lockfile change now resolves the dashboard’s Apollo/Wagmi websocket chain against ws@7.5.10, but graphql-ws@6.0.7 in the same lockfile declares a peer requirement of ws: ^8. Because this commit switched the resolved peer instance from ws@8.18.0 to v7, websocket-dependent paths (for example Node-side GraphQL subscriptions or wallet connector flows) can execute against an unsupported major and fail at runtime. Please preserve a ws@^8 resolution for this dependency graph.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator

@PedroBinotto PedroBinotto left a comment

Choose a reason for hiding this comment

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

lgtm

@claude
Copy link
Copy Markdown

claude Bot commented Apr 24, 2026

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 870565990e

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread pnpm-lock.yaml
"@solana/subscribable": 3.0.3(typescript@5.9.3)
typescript: 5.9.3
ws: 8.18.0(bufferutil@4.0.9)(utf-8-validate@5.0.10)
ws: 7.5.10(bufferutil@4.0.9)(utf-8-validate@5.0.10)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Restore ws@^8 for Solana subscription transport

This lockfile update downgrades the Solana websocket transport path to ws@7.5.10, but @solana/rpc-subscriptions-channel-websocket@3.0.3 declares a ws: ^8.18.0 peer in the same pnpm-lock.yaml. That creates an unsupported major-peer resolution for the Coinbase/Solana connector chain used via wagmi/rainbowkit, so websocket-based subscription flows can fail at runtime even though install succeeds; keep this dependency chain on a ws@^8 resolution.

Useful? React with 👍 / 👎.

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.

2 participants