# REST API Published articles for REST API. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## GitHub Actions: правила запуска стали общедоступными, для pull\_request\_target вводят ограничения DevFeed: [GitHub Actions: правила запуска стали общедоступными, для pull\_request\_target вводят ограничения]() Original publisher: [Read original article]() Author: MaxRokatansky (OTUS) Published: 2026-09-18T07:27:15Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [GitHub Actions](), [GitHub](), [API](), [ci]() Tags: [api](), [ci](), [cicd-2622a5c70597](), [github](), [github-actions](), [rest-api](), [tag-070ecaaf0eda](), [tag-431721c35e50](), [tag-7d2878fc3cc1](), [tag-9e079357c819](), [workflow]() ### AI overview GitHub has made workflow execution protections for GitHub Actions generally available. The rules control who can trigger workflows and under which events, support file-specific policies, provide evaluation results in Insights, and can be managed through the REST API. GitHub is also introducing default restrictions for pull_request_target in affected public repositories. ### Source excerpt GitHub вывел в общий доступ защиту запуска рабочих процессов Actions: правила позволяют контролировать, кто и при каких событиях может запускать пайплайны. Отдельное изменение касается pull_request_target, который в публичных репозиториях начнут блокировать по умолчанию. Разобраться в изменениях ## Turbo build machines can now be enabled per deployment DevFeed: [Turbo build machines can now be enabled per deployment]() Original publisher: [Read original article]() Author: Mehul Kar Published: 2026-09-17T20:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Deployment](), [Vercel](), [Command-line interface](), [REST API](), [GitHub](), [builds]() Tags: [build](), [cli](), [deploy](), [deployment](), [github](), [rest-api](), [vercel]() ### AI overview Vercel now allows Turbo build machines to be enabled for individual deployments. Developers can opt in through a Git commit message, Vercel CLI 59.20.0 or later, or the REST API without changing project settings. ### Source excerpt You can now opt into Turbo build machines on any individual deployment. This is useful when you need to increase resources temporarily without changing project settings. You can do this in three ways: Include #VERCEL_BUILD_MACHINE=TURBO in your Git commit message before pushing to GitHub Use vc deploy --turbo (Vercel CLI 59.20.0 or later) Set buildMachine to turbo when creating a deployment with the REST API Learn more in the managing builds documentation. Read more ## Microsoft прекратит поддержку модулей Graph для Windows PowerShell 5.x DevFeed: [Microsoft прекратит поддержку модулей Graph для Windows PowerShell 5.x]() Original publisher: [Read original article]() Author: maybe\_elf Published: 2026-09-17T07:07:54Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [PowerShell](), [Microsoft](), [API](), [REST API]() Tags: [api](), [graph](), [microsoft](), [microsoft-365](), [microsoft-graph](), [powershell](), [rest-api](), [tag-13acbb3718a7](), [tag-25f83bc28918](), [tag-82fb255df683](), [tag-c85b5c428c35](), [windows]() ### AI overview Microsoft is ending support for Microsoft Graph PowerShell modules on PowerShell 5.x through a planned 12-month transition. Version 2.x modules will continue to work during that period, but new features will target PowerShell 7.x and version 3.x modules will support only PowerShell 7.x. ### Source excerpt Microsoft объявила о прекращении поддержки модулей Graph для PowerShell 5.x и порекомендовала пользователям перейти на новую версию. В 2025 году компания сообщила о планах по выводу из эксплуатации некоторых компонентов Graph. Читать далее ## Native Marketplace integrations now support custom environments DevFeed: [Native Marketplace integrations now support custom environments]() Original publisher: [Read original article]() Author: Tony Pan Published: 2026-09-17T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Deployment](), [Environment Variables](), [Command-line interface](), [REST API]() Tags: [cli](), [deployment](), [environment-variables](), [environments](), [rest-api](), [vercel]() ### AI overview Vercel now lets users connect native Marketplace resources to custom environments through the dashboard, CLI, or REST API. The resulting environment variables can be scoped to the selected environments, while existing deployments remain unchanged. ### Source excerpt You can now connect native Marketplace resources to custom environments. Previously, resource connections could only target production, preview, and development environments. Choose custom environments when connecting a resource from the Vercel dashboard, Vercel CLI, or REST API. Vercel scopes the environment variables created by the connection to the selected environments. For example, from the CLI: Existing deployments do not change. Create a new deployment after connecting a resource or changing its environment scope. Custom environments are available on Pro and Enterprise plans. Read the docs for connecting from the dashboard, the CLI --environment flag, and the REST API envVarEnvironments field. Read more ## How to Connect Your Twilio Agent to External APIs DevFeed: [How to Connect Your Twilio Agent to External APIs]() Original publisher: [Read original article]() Author: Amanda Lange Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [AI Agent](), [API](), [C#](), [.NET 9](), [REST API](), [SDKs](), [OpenAI]() Tags: [agent](), [api](), [apis](), [c-sharp](), [developer-insights](), [environment-variables](), [how-to](), [net](), [net-9](), [ngrok](), [openai](), [rest-api](), [sdk]() ### AI overview This tutorial explains how to build a voice AI agent with C# and .NET 9 using Twilio Conversation Relay. It demonstrates LLM tool calling to fetch live data from an external REST API and covers project setup, required packages, environment variables, and API key storage. ### Source excerpt How to Connect Your Twilio Agent to External APIs ## How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation in Node.js Memory DevFeed: [How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation in Node.js Memory]() Original publisher: [Read original article]() Author: Amanda Lange, Dhruv Patel Published: 2026-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Node.js](), [Large Language Model](), [Express](), [OpenAI](), [API](), [WebSocket](), [Machine learning]() Tags: [api](), [axios](), [console](), [developer-insights](), [environment-variables](), [express](), [how-to](), [http](), [ide](), [install](), [js](), [json](), [llm](), [ngrok](), [node-js](), [npm](), [openai](), [rest-api](), [sdk](), [visual-studio-code](), [web]() ### AI overview This tutorial shows how to build a Node.js Express service that uses Twilio Conversation Memory, OpenAI, and voice streams to preserve caller context, preferences, and action history across separate inbound calls. It covers project setup, package installation, local webhook exposure with ngrok, and access to Twilio's Conversation Memory REST API. ### Source excerpt Learn how to orchestrate multi-call voice conversations using Node.js, OpenAI, and Twilio Conversation Memory to persist caller context across separate calls. ## How to Connect Your Twilio Agent to External APIs with PHP DevFeed: [How to Connect Your Twilio Agent to External APIs with PHP]() Original publisher: [Read original article]() Author: Amanda Lange, Matthew Setter Published: 2026-09-11T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [PHP](), [Tutorial](), [AI Agent](), [API](), [REST API](), [voice ai](), [.env](), [OpenAI](), [Composer](), [ide]() Tags: [agent](), [agents](), [apis](), [build](), [conversation-relay](), [developer-insights](), [external](), [how-to](), [openai](), [openswoole](), [php](), [rest-api](), [tutorial](), [voice]() ### AI overview This tutorial shows how to use PHP and OpenSwoole with Twilio Conversation Relay to build a voice agent that uses LLM tool calling to retrieve live data from an external REST API. It covers project setup, required packages, and storing an OpenAI API key in a .env file. ### Source excerpt In this tutorial, you will use PHP and OpenSwoole to build a voice agent using Twilio Conversation Relay. ## Document360 Releases Real-Time Collaborative Editing and API v3 DevFeed: [Document360 Releases Real-Time Collaborative Editing and API v3]() Original publisher: [Read original article]() Author: Darshan Sureshkumar Published: 2026-09-10T12:17:41Z Content type: release Language: en Sources: [Knowledge Management Tips, Best Practices and More]() Topics: [API](), [REST API](), [Authorization](), [Documentation](), [Automation]() Tags: [api](), [authorization](), [automation](), [product-update](), [release](), [rest-api]() ### AI overview Document360 announces real-time collaborative editing in its Advanced WYSIWYG editor and a ground-up rebuild of its public REST API as API v3. The release also includes permission-aware authorization, expanded automation coverage, publishing workflow changes, labels, reader-group controls for Eddy AI features, unified navigation, and improved offline exports. ### Source excerpt Documentation is a team effort, but most authoring tools still treat writing as ... The post No Locks, No Limits: Collaborative Editing and API v3 Are Here appeared first on Document360. ## Co-Create: Building GitLab with our users DevFeed: [Co-Create: Building GitLab with our users]() Original publisher: [Read original article]() Author: Isa Huerga Published: 2026-09-10T00:00:00Z Content type: article Language: en Sources: [GitLab]() Topics: [GitLab](), [CI/CD](), [Scala](), [Claude](), [Application Security](), [Cloud APIs]() Tags: [api](), [ci-cd](), [co-created](), [community](), [contributors](), [duo](), [engineering](), [open-source](), [rest-api](), [scala](), [security]() ### AI overview GitLab users collaborated through the Co-Create program on product improvements delivered in the first half of 2026, including API extensions, CI/CD capabilities, Scala support for AI-powered code understanding, security controls, and integration flexibility. ### Source excerpt GitLab users bring firsthand experience of the workflows they want to improve. Through our Co-Create program, they collaborate directly with us to design, build, and deliver product improvements that benefit more teams. In the first half of 2026, our users helped us extend APIs, add CI/CD capabilities, expand language support for AI-powered code understanding, strengthen security controls, increase the flexibility of integrations, and make GitLab easier to use and understand. Co-Create gives customers a direct path from a real-world challenge to a product improvement. Customers collaborate with us on the problem and solution, and help deliver the change. Unlike a feedback-only model, this puts real workflow context into the product development process. It creates a shorter path from need to value while helping us validate improvements in real conditions and extend their benefits to more GitLab users. "Over ten years ago, we set out to build code.siemens.com, our internal coding platform based on GitLab, which today serves close to 100,000 people. We've run and scaled the platform with a tiny team, guided by a 'for developers, from developers' philosophy. We co-created hundreds of features such as x509/gpg signed commits, protected container/packages, and project and social features such as follow users, allowing us to strengthen the security and collaboration culture at the scale of Siemens." -- Roger Meier, Distinguished Engineer, Siemens From a specific need to a shared improvement Some of the best product improvements start with a specific, real-world need. GitLab contributors helped us address the following needs: Making Scala codebases understandable to Orbit and GitLab Duo Giving security administrators a way to enforce Secret Push Protection across an entire instance Letting high-throughput teams configure merge train pipeline limits Showing the platforms supported by multi-architecture images Providing screen reader users with more context on documentation pa ## Customize Amazon API Gateway destinations for execution logs DevFeed: [Customize Amazon API Gateway destinations for execution logs]() Original publisher: [Read original article]() Author: Giedrius Praspaliauskas Published: 2026-09-09T22:35:42Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [Amazon API Gateway](), [Amazon CloudWatch Logs](), [log management](), [Amazon S3](), [SIEM, Security, Observability]() Tags: [amazon-api-gateway](), [amazon-cloudwatch-logs](), [amazon-s3](), [announcements](), [intermediate-200](), [logs](), [observability](), [rest-api]() ### AI overview This tutorial explains how to route Amazon API Gateway REST API execution logs to CloudWatch Logs, Amazon S3, or Amazon Data Firehose. It contrasts execution logs with access logs and describes their use for diagnosing authorization, validation, integration, mapping, and error-handling behavior. ### Source excerpt Amazon API Gateway execution logs help you trace request processing step by step through your REST API stages. They capture authorization results, integration latency, mapping template output, and error details that are otherwise invisible at the API surface. When a production request fails in a way the access log cannot explain, the execution log is [...] ## The thoroughness of Tom Johnson's free Documenting API's course on OpenAPI 3.0 and Swagger UI DevFeed: [The thoroughness of Tom Johnson's free Documenting API's course on OpenAPI 3.0 and Swagger UI]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-09-09T21:17:32Z Content type: article Language: en Sources: [T.J. Maher]() Topics: [OpenAPI Specification](), [Documentation](), [REST API](), [Swagger](), [Testing](), [Postman](), [JavaScript](), [JSON](), [Authentication](), [cURL](), [Chrome](), [Open Source]() Tags: [api](), [api-documentation](), [authentication](), [chrome](), [chrome-extension](), [curl](), [documentation](), [github](), [javascript](), [json](), [openapi](), [pdf](), [postman](), [rest-api](), [swagger](), [testing]() ### AI overview The article reviews Tom Johnson's free "Documenting APIs: A guide for technical writers and engineers" course. It describes the course's 17 chapters, practical API-learning exercises, coverage of REST APIs, OpenAPI, Swagger UI, testing and publishing API documentation, and a PDF edition exceeding 900 pages. ### Source excerpt While researching information for my job about the Swagger UI and how it can be used for testing, I came across this free course, called Documenting APIs: A guide for technical writers and engineers at https://idratherbewriting.com/learnapidoc/docapis_overview.html written by Tom Johnson, a technical writer based in Seattle who works for Google. The course looks intense, containing 17 chapters talking about Introduction to REST APIs, using APIs like a developer, Documenting API endpoints, the Open API spec, Testing API docs, Publishing API docs, and more. From the Course Introduction: "You'll first learn about API documentation by using a simple weather API to put a weather forecast on your site. [...] As you use the API, you'll learn about endpoints, parameters, data types, authentication, curl, JSON, the command line, Chrome's Developer Console, JavaScript, and more. The idea is that rather than learning about these concepts independent of any context, you learn them by immersing yourself in a real scenario while using an API. Immersion in real scenarios makes these tools and technologies more meaningful. "We'll then transition into standards, tools, and specifications for REST APIs. You'll learn about the required sections in API documentation, analyze examples of REST API documentation from various companies, learn how to join an open-source project to get experience, and more. "[...] We'll also dive into specifications such as the OpenAPI specification and Swagger UI (which provides tooling for the OpenAPI specification). Additionally, you'll learn how to document native library APIs and generate Javadoc". Tom Johnson offers a PDF version of this free course... over 900 pages, with more always being added. It also offers many workshop-like activities you could put in an actual itinerary. You would need for the course: Chrome, since it provides "a Javascript Console that works well for inspecting JSON", the JSON Formatter Chrome extension, Postman, a GitHub acco ## Bring your own client certificate for backend mTLS in Amazon API Gateway DevFeed: [Bring your own client certificate for backend mTLS in Amazon API Gateway]() Original publisher: [Read original article]() Author: Biswanath Mukherjee Published: 2026-09-08T21:46:39Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [Amazon API Gateway](), [AWS Certificate Manager](), [Amazon Elastic Container Service](), [nginx]() Tags: [amazon-api-gateway](), [amazon-elastic-container-service](), [announcements](), [architecture](), [authentication](), [aws-certificate-manager](), [aws-fargate](), [intermediate-200](), [rest-api](), [tls]() ### AI overview This tutorial shows how to configure Amazon API Gateway to present a third-party or AWS Private CA-issued client certificate for outbound mTLS to an Amazon ECS backend. ### Source excerpt Enterprises that use Amazon API Gateway often want to bring their own client certificate for backend mutual TLS (mTLS) authentication. With API Gateway, you can now use a third-party or AWS Private CA-issued client certificate for the outbound mTLS handshake. In this post, you build a REST API with an outbound mTLS connection to an Amazon ECS backend. ## Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs DevFeed: [Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs]() Original publisher: [Read original article]() Author: vmwareblogs Published: 2026-09-07T09:38:44Z Content type: tutorial Language: en Sources: [VMware Blogs]() Topics: [OpenAPI Specification](), [SDKs](), [.NET](), [C#](), [developer tooling](), [Java](), [Python](), [PowerShell]() Tags: [apis](), [cli](), [cloud](), [cloud-infrastructure](), [csharp](), [developer](), [developer-tooling](), [docker](), [home-page](), [java](), [net](), [openapi](), [powershell](), [programming](), [programming-language](), [python](), [rest](), [rest-api](), [sdk](), [specifications](), [vcf-9-0](), [vcf-9-1](), [vcf-sdk]() ### AI overview This guide explains how to generate a strongly typed .NET C# client SDK from VMware Cloud Foundation and vSphere OpenAPI specifications. It covers OpenAPI Generator, installation options, large specification handling, API-surface scoping, and the REST and JSON-RPC interfaces targeted by the example. ### Source excerpt Starting with VMware Cloud Foundation (VCF) 9.0, VMware officially publishes OpenAPI specifications for VCF APIs. This is a major milestone for developers, enabling you to consume VCF APIs using your programming language of choice. VMware provides first-class developer tooling such as VCF PowerCLI for PowerShell users and the VCF SDK offering Java and Python bindings. ... Continued The post Client-Side SDK Generation with VMware Cloud Foundation OpenAPI Specs appeared first on VMware Blogs. ## Build a real-time market data app with ClickHouse and Massive DevFeed: [Build a real-time market data app with ClickHouse and Massive]() Original publisher: [Read original article]() Author: Lionel Palacin Published: 2026-09-04T00:00:00Z Content type: tutorial Language: en Sources: [ClickHouse Blog]() Topics: [App](), [data](), [Node.js](), [Back end](), [API keys]() Tags: [analytics](), [api](), [app](), [backend](), [clickhouse](), [compression](), [data](), [demo](), [events](), [how-to](), [latency](), [low-latency](), [node](), [node-js](), [react](), [real-time](), [rest-api](), [storage](), [streams](), [visualization]() ### AI overview A tutorial for building a real-time market-data application that ingests, stores, and queries trade and quote ticks with Massive and ClickHouse, using Node.js for backend work and React for live visualization. ### Source excerpt Learn how to build a real-time financial analytics application with Massive and ClickHouse that scales to thousands of events per second. ## Introducing Appwrite Explorer DevFeed: [Introducing Appwrite Explorer]() Original publisher: [Read original article]() Author: Eldad Fux Published: 2026-08-31T00:00:00Z Content type: release Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [REST API](), [OpenAPI Specification](), [browser]() Tags: [api](), [documentation](), [openapi](), [product](), [products](), [release](), [rest-api]() ### AI overview Appwrite introduces Appwrite Explorer, a built-in API workspace in the Console. It lets developers browse REST endpoints, construct requests with guided forms, send live calls, and inspect responses without leaving the browser. Explorer uses OpenAPI definitions generated from Appwrite server source code and shared with the API reference and SDK generation pipeline. ### Source excerpt Appwrite Explorer brings the Appwrite REST API into the Console. Browse every endpoint, build requests with guided forms, send live calls against your project, and inspect responses without leaving the browser. ## Introducing Orbit: Turn Any Task Into the Right API Calls DevFeed: [Introducing Orbit: Turn Any Task Into the Right API Calls]() Original publisher: [Read original article]() Author: Abhinav Asthana Published: 2026-08-27T16:00:00Z Content type: article Language: en Sources: [Postman Blog]() Topics: [API](), [MCP Server](), [Artificial Intelligence](), [MCP](), [Postman](), [REST API](), [Claude Code]() Tags: [agents](), [ai](), [ai-agents](), [api-discovery](), [blog](), [free](), [general](), [mcp](), [mcp-server](), [model-context-protocol](), [orbit](), [post](), [rest-api]() ### AI overview Postman introduces Orbit, a free API discovery tool for AI agents. Agents can describe a task to find suitable public API endpoints, then select an endpoint and receive an integration brief covering authentication, URLs, request steps, parameters, response codes, dependencies, and common pitfalls. Orbit is available as an MCP server and a REST API, with no account, API key, or OAuth setup required. ### Source excerpt Orbit is a free API discovery tool for AI agents. Describe a task, get the endpoints that fit, then get a task brief to integrate them. No account, no auth. The post Introducing Orbit: Turn Any Task Into the Right API Calls appeared first on Postman Blog. ## Python projects now support routing rules DevFeed: [Python projects now support routing rules]() Original publisher: [Read original article]() Author: Ricardo Gonzalez Published: 2026-08-26T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Routing (disambiguation)](), [Python](), [FastAPI](), [Django](), [Flask](), [Command-line interface](), [SDKs](), [Deployment](), [CI/CD](), [REST API]() Tags: [api](), [automation](), [ci-cd](), [cli](), [deployment](), [python](), [rest-api](), [routing](), [sdk](), [vercel]() ### AI overview Vercel now supports routing rules for Python projects, allowing response headers and request rewrites to internal paths for FastAPI, Django, and Flask applications. Rules are evaluated by the Vercel CDN before requests reach the application and can take effect immediately without a new deployment. ### Source excerpt Python projects can now use routing rules to set response headers or rewrite requests to internal paths, including apps built with FastAPI, Django, and Flask. The Vercel CDN evaluates rules before requests reach your application, so changes apply without a new deployment. For example, this FastAPI app serves a /new route: To send requests for /old to that route, create a rewrite from the CDN tab in your project dashboard or with the Vercel CLI: Published rules take effect immediately across all regions, and you can roll back to a previous version from the History tab. You can also manage rules from Python with the vercel SDK, which wraps the Vercel REST API. add_route stages the rule, and update_route_version publishes it: Rewrites can also be defined in vercel.json: Project-level rules live outside your deployment and are evaluated before its routes, so a published rule takes precedence over a vercel.json rewrite for the same path. Each surface fits a different workflow: How you define it Takes effect Best for CDN tab in the dashboard On publish Editing and testing rules visually Vercel CLI On publish One-off changes from the terminal vercel Python SDK or REST API On publish Automation and CI/CD vercel.json On each deployment Rewrites that ship with the application code Update Vercel CLI to the latest version and read the routing documentation to get started. Read more ## Pulumi Context API: query your infrastructure as a graph DevFeed: [Pulumi Context API: query your infrastructure as a graph]() Original publisher: [Read original article]() Author: Levi Blackstone Published: 2026-08-26T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [API](), [Graphs](), [Cloud APIs](), [infrastructure as code (IAC)](), [Command-line interface](), [JSON](), [pulumi-neo]() Tags: [agent](), [ai-agents](), [api](), [cli](), [features](), [graph](), [iac](), [infrastructure-as-code-iac](), [json](), [product](), [pulumi](), [pulumi-cloud](), [pulumi-neo](), [rest-api]() ### AI overview Pulumi is launching the Context API, a read-only API that connects Pulumi-managed and discovered resources, stacks, and their relationships into a graph. Available in public preview for Enterprise and Business Critical organizations, it supports infrastructure-impact, coverage, and cleanup queries through the Pulumi CLI or REST API. Pulumi Neo uses it out of the box, and other authenticated agents can access its schema and query guidance. ### Source excerpt Every platform team fields the same questions: What is running? What breaks if we change this? What can we safely delete? The answers exist, but they're scattered across state files, cloud consoles, and the memories of whoever set things up. Today we're launching the Pulumi Context API, a read-only API that connects Pulumi-managed and discovered resources, stacks, and their relationships into a graph. It's designed agent-first: Pulumi Neo, our infrastructure agent, uses it out of the box, and other agents can fetch the current graph vocabulary and query guidance on demand. It's available in public preview for organizations on the Enterprise and Business Critical editions. Answers that follow infrastructure relationships Pulumi already records the resources your programs manage, their dependencies, how stacks consume each other's outputs, and the resources Pulumi Discovery finds outside infrastructure as code (IaC). The Context API connects this data so you can ask questions that depend on the relationships: Impact: Which stacks are affected if we upgrade this provider? If this stack changes, what consumes its outputs? Coverage: How much of our infrastructure lives outside IaC, and in which accounts? Cleanup: Which stacks have no dependents and are candidates for retirement? A query is a JSON document with a handful of clauses. anchor names the starting nodes, traverse follows relationships from there, and return chooses what comes back. You can run a query through the Pulumi CLI or REST API. Here's a selector that starts from AWS provider instances older than version 7.0.0 and follows incoming provided_by relationships back to the visible resources they manage: { "anchor": { "nodeType": "resource", "match": { "type": "pulumi:providers:aws", "fields": { "provider_version": { "op": "lt", "value": "7.0.0" } } } }, "traverse": [ { "edgeTypes": ["provided_by"], "direction": "in", "alias": "managed" } ], "return": { "select": ["anchor", "managed"] } } A response for one m ## Wire It, Run It, Deploy It: AI Workflows in Gradio DevFeed: [Wire It, Run It, Deploy It: AI Workflows in Gradio]() Original publisher: [Read original article]() Author: yuvraj sharma; Abubakar Abid Published: 2026-08-25T00:00:00Z Content type: tutorial Language: en Sources: [Hugging Face - Blog]() Topics: [AI, ML & Data Engineering](), [AI Chat](), [GPU]() Tags: [ai](), [gpu](), [gradio](), [hugging-face](), [inference-providers](), [llm](), [models](), [python](), [rest-api](), [spaces](), [tutorial](), [workflows]() ### AI overview A tutorial on building and deploying Gradio AI workflows as typed-node graphs, with runnable examples for image editing, generation, text-to-speech, dataset analysis, REST endpoints, and GPU-backed Python nodes. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## WordPress PHP-Only Block Registration DevFeed: [WordPress PHP-Only Block Registration]() Original publisher: [Read original article]() Author: Fränk Klein Published: 2026-08-24T13:54:02Z Content type: tutorial Language: en Sources: [CSS-Tricks]() Topics: [Web Development]() Tags: [articles](), [javascript](), [php](), [rest-api](), [wordpress](), [wordpress-blocks]() ### AI overview WordPress 7.0 adds PHP-only block registration, generating the JavaScript registration, editor preview, and sidebar controls from PHP definitions. The article explains the approach and its limits, including reduced interaction within the block preview. ### Source excerpt Seven and half years after blocks arrived in Core, WordPress introduces a way to build blocks without React annd build pipelines. All you need is PHP. WordPress PHP-Only Block Registration originally handwritten and published with love on CSS-Tricks. You should really get the newsletter as well. ## How to configure Cloudinary video transcoding on Webflow Cloud DevFeed: [How to configure Cloudinary video transcoding on Webflow Cloud]() Original publisher: [Read original article]() Author: Ismail Ajagbe Published: 2026-08-08T00:00:00Z Content type: tutorial Language: en Sources: [Webflow Blog]() Topics: [webflow](), [Transcodings](), [Nextra](), [Streaming](), [REST API](), [Cloudflare Workers]() Tags: [edge](), [guides](), [how-to](), [next-js](), [node-js](), [rest-api](), [streaming](), [webflow]() ### AI overview A practical guide to configuring Cloudinary video transcoding on Webflow Cloud. It explains how to use the REST API, eager transformations, optimized delivery URLs, and HLS adaptive streaming on the edge runtime without the Node.js SDK. ### Source excerpt Learn how to upload videos to Cloudinary from a Webflow Cloud Next.js app and deliver optimized video over CDN using plain fetch on the edge runtime. ## Vercel Container Registry repositories can now be made public DevFeed: [Vercel Container Registry repositories can now be made public]() Original publisher: [Read original article]() Author: Luke Phillips-Sheard Published: 2026-08-07T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [REST API]() Tags: [api](), [cli](), [container-registry](), [documentation](), [images](), [registry](), [rest](), [rest-api](), [sandbox](), [update](), [vercel]() ### AI overview Vercel Container Registry repositories can now be made public. Public repositories allow any Vercel team to pull and use their images while retaining read-only access; repositories remain private by default. ### Source excerpt Vercel Container Registry now lets you make a repository public, so anyone with a Vercel account can pull and use its images. Sharing already granted read access to up to 100 teams, and making a repository public opens that access to every Vercel team rather than a named set. Public access is read-only, so anyone can pull and use the images but cannot push, delete, or otherwise change the repository. Repositories stay private by default. Make a repository public from the project dashboard under Images -> repository -> Settings -> Public Access, where confirming requires typing the repository name. You can also set visibility from the Vercel CLI: Public images work like shared images in Vercel Sandbox, which accepts a team-scoped image reference in Sandbox.create(): Update your repository visibility from the dashboard, the CLI, or the REST API, and see the Vercel Container Registry documentation to learn more. Read more ## Set your own project avatars DevFeed: [Set your own project avatars]() Original publisher: [Read original article]() Author: wits Published: 2026-08-05T17:30:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [REST API](), [GitHub](), [Back end]() Tags: [backend](), [github](), [rest-api](), [vercel]() ### AI overview Vercel now lets users set custom project avatars from the Vercel dashboard or upload them through the REST API. Avatars appear across the dashboard and in Vercel bot comments on GitHub, while projects without detectable favicons can now be assigned an explicit avatar. ### Source excerpt You can now set a project's avatar from its settings in the Vercel dashboard. Until now, Vercel set it automatically, using the favicon from the project's production deployment. That's still the default if you haven't set one. The avatar renders across the dashboard and on Vercel bot comments in GitHub. Microfrontend projects that share one favicon can now get distinct avatars, and backend projects with no favicon to detect can set one explicitly. You can change a project's avatar from its settings in the Vercel Dashboard, or upload one with the REST API. Read more ## Set Up Developer Self-service in Your Internal Developer Portal | Port DevFeed: [Set Up Developer Self-service in Your Internal Developer Portal | Port]() Original publisher: [Read original article]() Author: Yonatan Boguslavski Published: 2026-07-30T10:17:19Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Platform Engineering](), [Provisioning](), [Terraform](), [AWS Lambda](), [Jenkins](), [REST API](), [GitHub](), [Amazon S3](), [Microservice]() Tags: [api](), [aws](), [aws-lambda](), [catalog](), [cognitive-load](), [configuration](), [developer](), [developer-portal](), [github](), [infrastructure](), [internal-developer-portal](), [jenkins](), [platform-engineering](), [provisioning](), [rest-api](), [s3](), [terraform](), [tooling]() ### AI overview This article explains how to implement developer self-service actions in Port's internal developer portal. It covers provisioning, updating, and deleting software catalog entities and cloud resources, while describing webhook-based execution through tools such as AWS Lambda and REST APIs. ### Source excerpt Port supports many variations of implementing developer self service actions, including allowing for self-service RBAC, TTL and manual approvals. [Next page]()