# SDKs Published articles for SDKs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Company's Building AI Agent Sandbox SDKs & APIs DevFeed: [Company's Building AI Agent Sandbox SDKs & APIs]() Original publisher: [Read original article]() Author: iHateReading Published: 2026-09-12T13:15:15Z Content type: opinion Language: en Sources: [iHateReading]() Topics: [AI Agent](), [SDKs](), [Artificial Intelligence](), [Development]() Tags: [ai](), [ai-agent](), [ai-sandboxes](), [ai-sandboxes-vercel-aws-google-daytona](), [apis](), [aws](), [backend](), [blockchain](), [coding](), [company-s-building-ai-agent-sandbox-sdks-apis](), [daytona](), [developer](), [development](), [frontend](), [google](), [ihatereading](), [javascript](), [node-js](), [product](), [programming](), [react](), [sdks](), [typescript](), [vercel](), [web-development]() ### AI overview An opinion article discusses companies building AI agent sandboxes, SDKs, and APIs, in the context of an ongoing competition around AI sandboxes. ### Source excerpt Company's Building AI Agent Sandbox SDKs & APIs I wrote about the fight for AI sandboxes back in March -- the short version was that every AI agent that wri... ## Scaling AI Agent Infrastructure with the MCP Stateless updates DevFeed: [Scaling AI Agent Infrastructure with the MCP Stateless updates]() Original publisher: [Read original article]() Author: Kurtis Van Gent; Alan Blount Published: 2026-09-12T11:04:33.891311Z Content type: release Language: en Sources: [Google Developers Blog]() Topics: [networking](), [SDKs]() Tags: [agentic](), [ai-agent](), [c-sharp](), [go](), [http](), [infrastructure](), [mcp](), [python](), [routing](), [sdks](), [serverless](), [typescript](), [updates]() ### AI overview The MCP release candidate replaces transport-level session management with a stateless core for HTTP load balancing, cloud-native scaling, and serverless deployments. It also introduces routing headers, caching controls, MRTR, and beta SDKs for Python, TypeScript, Go, and C#. ### Source excerpt The 2026-07-28 Model Context Protocol (MCP) specification replaces legacy stateful constraints with a fully stateless core, enabling cloud-native horizontal scaling, serverless deployments, and standard round-robin load balancing. This architectural shift introduces standardized HTTP headers for efficient routing without deep packet inspection, caching controls, and Multi Round-Trip Requests (MRTR) to handle interactive and long-running tasks without blocking connections. Developers can immediately begin migrating their agentic applications to this highly scalable infrastructure using the newly available beta SDKs for Python, TypeScript, Go, and C#. ## Designing Documentation for LLMs and Coding Agents DevFeed: [Designing Documentation for LLMs and Coding Agents]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-09-11T22:55:25Z Content type: opinion Language: en Sources: [The CommonsBlog]() Topics: [Documentation](), [Large Language Model](), [AI-assisted coding](), [SDKs]() Tags: [ai](), [blog](), [coding-agents](), [documentation](), [llms](), [markdown](), [sdk](), [sdks](), [software-development](), [vibe-coding]() ### AI overview This opinion article argues that SDK and library documentation should be designed for both human developers and AI systems. It recommends text-based formats such as Markdown, smaller topic-focused sections, and strong indexing to make documentation more efficient for LLMs and coding agents, while retaining formats such as PDFs and videos for human consumption. ### Source excerpt Let's continue to explore how we can succeed with libraries and SDKs at a time when coding agents will be consuming what we create, as will ordinary developers ## NVIDIA Brings Real-Time AI to Broadcast, Sports and Global Streaming at IBC DevFeed: [NVIDIA Brings Real-Time AI to Broadcast, Sports and Global Streaming at IBC]() Original publisher: [Read original article]() Author: NVIDIA Writers Published: 2026-09-09T16:00:42Z Content type: release Language: en Sources: [NVIDIA Blog]() Topics: [AI Development](), [GPU](), [SDKs](), [Microservice]() Tags: [ai](), [artificial-intelligence](), [compliance](), [events](), [gpu](), [holoscan-for-media](), [image-to-video](), [media](), [media-and-entertainment](), [microservices](), [news](), [nvidia](), [nvidia-nim](), [pro-graphics](), [real-time](), [sdks](), [streaming](), [synthetic](), [text-to-video](), [video]() ### AI overview NVIDIA announced an expansion of NVIDIA AI for Media at IBC 2026, including GPU-accelerated SDKs and NIM microservices for media workflows. The article highlights Synthetic Video Detector integrations for assessing whether video footage may be AI-generated and for compliance review. ### Source excerpt At the IBC conference, running Sept. 11-14 in Amsterdam, the creative, technology and business communities are coming together to turn ideas into action and discuss innovations across the media and entertainment industries. More than 44,000 attendees from 170+ countries are gathering to explore 1,300+ exhibitions in 14+ halls and outdoor spaces, with over 600 speakers [...] ## Grindr settles HIV status data-sharing lawsuit for $35 million DevFeed: [Grindr settles HIV status data-sharing lawsuit for $35 million]() Original publisher: [Read original article]() Author: Pieter Arntz Published: 2026-09-08T12:51:14Z Content type: news Language: en Sources: [Malwarebytes]() Topics: [online privacy](), [App](), [SDKs]() Tags: [advertising](), [grindr](), [lawsuit](), [news](), [norway](), [privacy](), [sdks](), [uk-lawsuit]() ### AI overview Grindr reportedly agreed to settle a UK lawsuit alleging that it shared sensitive user data, including HIV-status information, with advertisers. The article explains privacy risks from advertising identifiers, analytics, SDKs, and other third-party app integrations. ### Source excerpt Grindr has settled a UK lawsuit alleging that it shared sensitive user data, including HIV status, with advertising companies. ## Announcing the Appwrite OAuth2 server: Turn your project into an identity provider DevFeed: [Announcing the Appwrite OAuth2 server: Turn your project into an identity provider]() Original publisher: [Read original article]() Author: Matej Bačo Published: 2026-09-04T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [OAuth 2.0](), [OpenID connect (OIDC)](), [Authorization](), [API](), [internal developer portal]() Tags: [announcements](), [api](), [authorization](), [developer-portal](), [github](), [oauth](), [oauth2](), [oidc](), [openid-connect](), [product](), [sdks]() ### AI overview Appwrite announces an OAuth2 server that lets projects act as OAuth 2.1 and OpenID Connect providers. Other applications can register as clients, obtain user-approved scoped access to APIs, and use standard authorization and token flows. ### Source excerpt Your Appwrite project can now act as an OAuth 2.1 and OpenID Connect provider, so other apps can offer Sign in with your product and request scoped access to your APIs. ## Give your agent Neon tools DevFeed: [Give your agent Neon tools]() Original publisher: [Read original article]() Author: Andre Landgraf Published: 2026-09-03T12:00:00Z Content type: release Language: en Sources: [Blog -- Neon Docs]() Topics: [MSP MCP]() Tags: [agent](), [api](), [mcp](), [mcp-server](), [openapi](), [product](), [sdks](), [tools](), [workflows]() ### AI overview Neon announces @neon/tools, which adapts its SDK client into typed tools for agents and expands the hosted Neon MCP Server. The article explains progressive tool discovery and why agent-oriented tools should bundle workflows rather than mirror raw REST operations. ### Source excerpt Today we're launching @neon/tools, a package that turns the @neon/sdk ergonomic client into typed agent tools with adapters for MCP, Mastra, and Eve. We're also using it to expand the hosted Neon MCP Server. ## Announcing the S3 API: Use any S3 client with Appwrite Storage DevFeed: [Announcing the S3 API: Use any S3 client with Appwrite Storage]() Original publisher: [Read original article]() Author: Torsten Dittmann Published: 2026-09-03T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Amazon S3](), [API](), [Amazon Web Services](), [SDKs](), [Command-line interface](), [migration]() Tags: [announcements](), [api](), [aws](), [backup](), [cli](), [code](), [commands](), [data](), [files](), [migration](), [reuse](), [s3](), [sdk](), [sdks](), [server](), [storage](), [tools]() ### AI overview Appwrite Storage now exposes an S3-compatible API that supports AWS CLI, AWS SDKs, rclone, s3cmd, and other S3 clients. Existing buckets and files remain available through both the native Storage API and the S3 API, with support for standard operations, multipart uploads, and presigned URLs. ### Source excerpt Appwrite Storage now exposes an S3-compatible API. Point the AWS CLI, the AWS SDKs, and tools like rclone at your Appwrite buckets, with no migration required. ## WorkOS announces Agent Registration, Airlock, Relay, and native iOS and Android SDKs DevFeed: [WorkOS announces Agent Registration, Airlock, Relay, and native iOS and Android SDKs]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-02T00:00:00Z Content type: release Language: en Sources: [WorkOS Blog]() Topics: [SDKs](), [Android](), [iOS](), [Authorization](), [Mobile](), [Claude](), [Kotlin](), [Swift](), [MCP](), [Coroutines](), [Claude Code](), [codex]() Tags: [agent](), [android](), [api](), [authorization](), [await](), [claude](), [claude-code](), [coroutines](), [ios](), [kotlin](), [maven-central](), [mcp](), [sdks](), [swift](), [updates]() ### AI overview WorkOS announces August updates including Agent Registration for scoped, short-lived credentials, Airlock for authorizing AI-agent actions, Relay for proxying third-party application requests, and native Swift and Kotlin SDKs for iOS and Android. ### Source excerpt Agent Registration, Airlock, Relay, iOS & Android SDKs, & more ## Announcing Console IV: the website and Console as one app DevFeed: [Announcing Console IV: the website and Console as one app]() Original publisher: [Read original article]() Author: Aditya Oberai Published: 2026-08-31T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [Website](), [Command-line interface](), [Documentation](), [SDK](), [Svelte]() Tags: [app](), [cli](), [docs](), [products](), [projects](), [sdks](), [svelte]() ### AI overview Appwrite announces Console IV, a fourth-generation Console that brings documentation, the CLI, Explorer, Terminal, Command Center, and projects together in one application. The release is intended to reduce context switching while preserving existing projects, APIs, bookmarks, API keys, and SDK code. ### Source excerpt Console IV puts the docs, CLI, Explorer, and your projects in one app so you stop bouncing between the IDE, docs, SDKs, terminals, and the agent. ## Solana Changelog: August 27, 2026 DevFeed: [Solana Changelog: August 27, 2026]() Original publisher: [Read original article]() Author: Solana Foundation Published: 2026-08-28T16:00:00Z Content type: release Language: en Sources: [Solana News Feed]() Topics: [changelog](), [Solana](), [releases](), [Tooling](), [SDKs](), [Transactions](), [Network]() Tags: [2026](), [announcements](), [blockchain](), [blockchain-technology](), [changelog](), [crypto-news](), [cryptocurrency](), [defi](), [developers](), [javascript](), [network](), [newsletter](), [nfts](), [podcasts](), [release](), [releases](), [sdk](), [sdks](), [solana](), [solana-ecosystem](), [technology](), [tooling](), [transactions](), [v5](), [web3]() ### AI overview The August 27, 2026 Solana changelog covers approaching V1 Transactions, a Mainnet feature gate reducing slot time to 300ms, releases across Solana tooling and SDKs, and proposed protocol changes. ### Source excerpt V1 Transactions are approaching, while a 300ms slot-time feature gate reached Mainnet and new releases shipped across Solana tooling. ## From one switch to a control panel: meet \`dataCollection\` DevFeed: [From one switch to a control panel: meet \`dataCollection\`]() Original publisher: [Read original article]() Author: Sigrid Huemer Published: 2026-08-28T09:00:00Z Content type: release Language: en Sources: [Sentry Blog]() Topics: [SDKs](), [data](), [JavaScript](), [sensitive data](), [Release notes](), [passwords]() Tags: [api-keys](), [data](), [javascript](), [passwords](), [release-notes](), [sdks](), [sensitive-data]() ### AI overview Sentry is replacing the all-or-nothing `sendDefaultPii` setting with `dataCollection`, which provides granular control over automatically collected data such as user information, headers, request bodies, and GenAI data. The change is rolling out across Sentry SDKs, with JavaScript SDK v11 making it the default and collecting more data than v10 by default. ### Source excerpt Sentry SDKs replace the `sendDefaultPii` boolean with `dataCollection`, granular options for user data, headers, bodies, GenAI data, and more. ## Pulumi Kubernetes v4.34.0: CRDs as provider extensions DevFeed: [Pulumi Kubernetes v4.34.0: CRDs as provider extensions]() Original publisher: [Read original article]() Author: Guinevere Saenger Published: 2026-08-28T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Kubernetes](), [Extension](), [SDKs](), [YAML](), [ingress-nginx]() Tags: [extensions](), [install](), [kubernetes](), [migration](), [product](), [providers](), [release](), [releases](), [sdk](), [sdks](), [yaml]() ### AI overview Pulumi Kubernetes provider v4.34.0 adds support for extending the provider with Kubernetes Custom Resource Definitions through a manifest and the new --extension flag. The release generates SDKs, supports all supported Pulumi languages including YAML, uses a single provider instance, and provides a migration path from crd2pulumi. ### Source excerpt We're really excited to bring you v4.34.0, the newest version of the Pulumi Kubernetes provider, which includes improved support for Kubernetes Custom Resource Definitions (CRDs). As with any release, we've also shipped standard dependency updates and bug fixes. This provider release includes the newest resources for Kubernetes v1.37.0, which was recently cut. So that in itself is very exciting! But the feature we're proudest of is that you can now extend the Kubernetes provider with any Kubernetes Custom Resource Definition of your choice by passing its manifest file to Pulumi, using the new --extension flag. We believe first-class CRD support in Pulumi is becoming more important than ever. For example, since the retirement of the ingress-nginx controller earlier this year, the recommended path for cluster ingress is Gateway API, which is maintained and shipped as CRDs. Generating a Pulumi SDK for CRDs In your Pulumi project root, run: pulumi package add kubernetes --extension "name=gateway-networking crd-manifest=gateway-api-crds.yaml" You will see the custom SDK appear in a new sdks/ folder, as well as a new parameterization reference in Pulumi.yaml. Single provider instance Your new CRD schema exists as an extension to your existing provider and will be managed under the same provider instance, allowing you to use a single provider configuration and kubeconfig. SDKs as dependencies Additionally, your code no longer needs to ship SDK files as part of the project. The provider extension is referenced in your project file and its SDK, like all dependencies, can be regenerated via pulumi install. You can choose to version the extension SDK, or continue to check the files into version control if you so desire. Full language support, including for YAML Kubernetes CRDs can now be provisioned with Pulumi in all supported languages. Unified CLI experience pulumi package add --extension extends your CRD schema into the Pulumi Kubernetes provider, using the same CLI as any ## Designing Libraries and SDKs for Human Developers and Coding Agents DevFeed: [Designing Libraries and SDKs for Human Developers and Coding Agents]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-22T17:08:47Z Content type: opinion Language: en Sources: [The CommonsBlog]() Topics: [SDKs](), [AI-assisted coding](), [Agentic development](), [Documentation](), [test](), [Specifications]() Tags: [agentic](), [blog](), [coding-agents](), [documentation](), [open-source](), [sdk](), [sdks](), [specifications](), [tests]() ### AI overview This opinion article argues that library and SDK authors should support both human developers and coding agents. It recommends clear source-code comments, generated API documentation, robust and runnable test suites, coverage analysis, and language-neutral specifications with conformance tests to clarify intended behavior and support faithful ports. ### Source excerpt Let's explore how we can succeed with libraries and SDKs at a time when coding agents will be consuming what we create, as will ordinary developers ## v1 Transactions and the ALT Trade-off DevFeed: [v1 Transactions and the ALT Trade-off]() Original publisher: [Read original article]() Author: Umberto Natale Published: 2026-08-17T00:00:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Transactions](), [benchmarking](), [SDKs]() Tags: [blockchain](), [blockchain-technology](), [crypto-news](), [cryptocurrency](), [defi](), [nfts](), [podcasts](), [reference](), [reports](), [rpc](), [sdks](), [serialization](), [solana](), [solana-ecosystem](), [transactions](), [upgrades](), [web3]() ### AI overview Solana is introducing the v1 transaction format with a maximum serialized size of 4,096 bytes, replacing Account Lookup Table resolution with larger inline transaction capacity. The analysis finds that current workloads are broadly compatible with the new envelope, while the unchanged 64-account limit may remain a constraint for some applications. ### Source excerpt Solana is introducing a new transaction format (v1) alongside an increase of the maximum transaction size from 1232 bytes to 4096 bytes. The v1 format aims to unlock new possibilities on-chain. This is done trading-off Account Lookup Tables (ALT) usage. In this research we explore in details the current usage of ALTs, alongside implications of removing them. ## Choosing & integrating LLM APIs: a practical guide DevFeed: [Choosing & integrating LLM APIs: a practical guide]() Original publisher: [Read original article]() Author: Cedric Turner Published: 2026-08-17T00:00:00Z Content type: tutorial Language: en Sources: [Redis Blog]() Topics: [Large Language Model](), [API](), [SDKs](), [Latency](), [Caching](), [Inference](), [Streaming](), [Embeddings](), [multimodal]() Tags: [apis](), [caching](), [code](), [engineering](), [inference](), [latency](), [llm](), [multimodal](), [sdks](), [streaming](), [tech-de]() ### AI overview A practical guide to choosing and integrating LLM APIs, covering provider capabilities, pricing, latency, quality evaluation, and the caching, retry, and memory layers needed for reliable production applications. ### Source excerpt Making your first LLM API call is easy: with most provider SDKs, it's about five lines of code. Keeping that call fast, affordable, and reliable once real users show up is where the actual engineering happens: costs can compound as conversations grow,... ## NVIDIA JetPack 7.2.1 Adds Agentic Video Skills and T3000 Emulation DevFeed: [NVIDIA JetPack 7.2.1 Adds Agentic Video Skills and T3000 Emulation]() Original publisher: [Read original article]() Author: Elizabeth Goodman Published: 2026-08-11T19:00:00Z Content type: article Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [Jetson](), [SDKs](), [CUDA](), [GPU](), [AI Inference](), [Inference Performance](), [Latency](), [Low Latency](), [C++](), [Python](), [Artificial Intelligence](), [Automation]() Tags: [agentic-ai-generative-ai](), [ai-inference](), [automation](), [c-plus-plus](), [cuda](), [edge-computing](), [featured](), [gpu](), [inference](), [jetpack](), [jetson](), [latency](), [low-latency](), [nvidia](), [python](), [robotics](), [robotics-compute](), [sdks](), [video-analytics](), [video-codec-sdk]() ### AI overview NVIDIA JetPack 7.2.1 adds PyNvVideoCodec 2.2 support on Jetson Thor, enabling Python-based hardware video encoding and decoding with GPU-resident frames. It also introduces agentic video skills that turn developer goals into device inspection, configuration, execution, measurement, and evidence-driven codec workflows. ### Source excerpt Video is a core data path across NVIDIA Jetson applications, from robotics and intelligent video analytics to industrial automation, healthcare, media... ## MoneyGram Ramps launches on Solana DevFeed: [MoneyGram Ramps launches on Solana]() Original publisher: [Read original article]() Author: Solana Foundation Published: 2026-08-11T10:00:00Z Content type: release Language: en Sources: [Solana News Feed]() Topics: [Solana](), [API](), [Developer Platform](), [Global Payments]() Tags: [announcements](), [api](), [blockchain](), [blockchain-technology](), [cross-border](), [crypto-news](), [cryptocurrency](), [defi](), [developer-platform](), [developers](), [integration](), [nfts](), [partner](), [payments](), [podcasts](), [remittances](), [sdks](), [solana](), [solana-ecosystem](), [stablecoins](), [web3]() ### AI overview MoneyGram Ramps is now live on Solana, providing developers with a single API for integrating fiat cash deposits and withdrawals into Solana applications, wallets, and exchanges. The service includes sandbox access and SDK documentation, with coverage spanning more than 25 countries for deposits and more than 170 countries and territories for withdrawals. ### Source excerpt MoneyGram Ramps gives Solana builders one API for cash deposits in 25+ countries and withdrawals in 170+ countries and territories. ## Baseten on Hugging Face Inference Providers 🔥 DevFeed: [Baseten on Hugging Face Inference Providers 🔥]() Original publisher: [Read original article]() Author: Alex Ker; Roland Crosby; Sid Shanker; Johan; Célina Hanouti; Simon Brandeis; Lucain Pouget; merve Published: 2026-08-06T00:00:00Z Content type: news Language: en Sources: [Hugging Face - Blog]() Topics: [AI Chat](), [SDKs]() Tags: [baseten](), [deepseek](), [enterprise](), [hub](), [hugging-face](), [inference](), [inference-providers](), [llms](), [partnerships](), [sdks](), [text-generation]() ### AI overview Baseten is now an Inference Provider on the Hugging Face Hub, offering conversational and text-generation access to supported open-weight LLMs. The integration is available through Hugging Face Python and JavaScript SDKs, with custom-key and Hugging Face-routed request modes. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## Connecting OpenTelemetry Traces with Sentry Errors in One Trace Waterfall DevFeed: [Connecting OpenTelemetry Traces with Sentry Errors in One Trace Waterfall]() Original publisher: [Read original article]() Author: Johannes Daxböck; Neel Shah Published: 2026-08-05T09:00:00Z Content type: tutorial Language: en Sources: [Sentry Blog]() Topics: [OpenTelemetry](), [tracing](), [telemetry](), [SDKs]() Tags: [errors](), [instrumentation](), [logs](), [opentelemetry](), [sdk](), [sdks](), [sentry](), [tracing]() ### AI overview Sentry's OtlpIntegration connects OpenTelemetry traces with Sentry errors and other events, allowing them to appear together in a trace waterfall. It reads the active OTel trace context and associates it with Sentry events while configuring an OTLP exporter for Sentry. ### Source excerpt The OtlpIntegration bridges OTel traces and Sentry errors. Keep your OTel setup, add Sentry for errors, and see both in one trace waterfall. ## Bringing Google Maps to Friendly Meals with Firebase AI Logic DevFeed: [Bringing Google Maps to Friendly Meals with Firebase AI Logic]() Original publisher: [Read original article]() Author: Marina Coelho Published: 2026-07-28T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Artificial Intelligence](), [Google Maps](), [Android](), [Kotlin](), [Google](), [SDKs](), [Mobile](), [personalization](), [real-time](), [configuration]() Tags: [ai](), [ai-logic](), [android](), [build](), [configuration](), [features](), [firebase](), [firebase-ai-logic](), [gemini](), [google](), [google-maps](), [grounding](), [kotlin](), [mobile](), [personalization](), [prompt](), [real-time](), [sdks](), [time]() ### AI overview A Firebase team tutorial explains how to add a Store Finder feature to the Friendly Meals Android app using Grounding with Google Maps through Firebase AI Logic. The Kotlin implementation uses location-aware Gemini responses to provide nearby businesses, operational details, and geographic personalization. ### Source excerpt News, tutorials, and updates from the Firebase team. ## SecretSpec 0.17: scopes, secrets caching, SOPS, age, and systemd credentials DevFeed: [SecretSpec 0.17: scopes, secrets caching, SOPS, age, and systemd credentials]() Original publisher: [Read original article]() Author: domenkozar Published: 2026-07-27T04:36:14Z Content type: release Language: en Sources: [Announcements - NixOS Discourse]() Topics: [SDKs](), [Authentication](), [GitHub](), [forgejo](), [Caching](), [OpenID connect (OIDC)]() Tags: [announcements](), [authentication](), [caching](), [forgejo](), [github](), [jwt](), [oidc](), [scaleway](), [sdk](), [sdks](), [systemd](), [upgrade]() ### AI overview SecretSpec 0.17 adds scoped secret resolution, caching for slow remote providers, cross-secret validation, JWT/OIDC authentication for Vault and OpenBao, GitHub and Forgejo Actions support, and six new providers. Its SDKs also gain scope support, requiring applications to upgrade the SDK package and bundled native resolver together. ### Source excerpt Hi all, We've released SecretSpec 0.17 with: scopes: consumers can now resolve only the secrets it declares, instead of receiving an entire profile. Secrets caching for slow remote providers, with configurable freshness and explicit invalidation. Cross-secret validation, including "at least one" and "exactly one" credential groups. JWT/OIDC authentication for Vault and OpenBao. A new GitHub and Forgejo Action that resolves, masks, and exposes secrets to later workflow steps. Six new providers: SOPS, age, KeePass KDBX, OpenBao, Scaleway Secret Manager, and systemd credentials. All SecretSpec SDKs have been updated with scope support. This required an FFI change, so applications should upgrade the SDK package and bundled native resolver together. Read the release blog post post or see the GitHub release. Domen Disclaimer: LLMs have been used in all the work delivered 1 post - 1 participant Read full topic ## OpenTelemetry: The platform engineer's path to standardized observability DevFeed: [OpenTelemetry: The platform engineer's path to standardized observability]() Original publisher: [Read original article]() Author: Sam Barlien Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [OpenTelemetry](), [observability](), [telemetry](), [Instrumentation](), [Traces](), [Kubernetes]() Tags: [cncf](), [incident](), [instrumentation](), [kubernetes](), [logs](), [metrics](), [observability](), [opentelemetry](), [platform](), [sdks](), [telemetry](), [traces](), [vendor-lock-in]() ### AI overview This article explains how OpenTelemetry standardizes observability across platform services by providing vendor-neutral APIs, SDKs, semantic conventions, and a Collector for routing and processing telemetry. It connects logs, metrics, and traces while allowing teams to choose analysis backends later, reducing fragmentation and vendor lock-in. ### Source excerpt Standardize observability across your platform with OpenTelemetry. Eliminate fragmented telemetry, reduce incident resolution time, and avoid vendor lock-in. ## Migrate Datadog telemetry with the OpenTelemetry Collector DevFeed: [Migrate Datadog telemetry with the OpenTelemetry Collector]() Original publisher: [Read original article]() Author: Mike Shi Published: 2026-07-21T18:01:08Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [migration](), [SDKs]() Tags: [agents](), [clickhouse](), [cost](), [instrumentation](), [kubernetes](), [logs](), [metrics](), [migration](), [observability](), [opentelemetry](), [sdks](), [telemetry](), [traces]() ### AI overview The article describes using the OpenTelemetry Collector's Datadog receiver to route existing Datadog agent and SDK telemetry to other supported observability destinations, avoiding immediate reinstrumentation during migration. It presents ClickStack as an example and frames lower storage costs and fuller telemetry retention as motivations for moving from Datadog. ### Source excerpt Recent improvements to the OpenTelemetry Collector's Datadog receiver let teams reroute telemetry from their existing Datadog agents and SDKs to ClickStack. or any OTel destination making migrations and evaluations simpler than ever. [Next page]()