# registry Published articles for registry. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Automate Docker Registry Creation with Harness and Terraform DevFeed: [Automate Docker Registry Creation with Harness and Terraform]() Original publisher: [Read original article]() Author: Shibam Dhar Published: 2026-09-16T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [docker registry](), [Kubernetes](), [Provisioning](), [Terraform](), [Infrastructure as code](), [CI/CD](), [Dockerfile]() Tags: [ci-cd](), [container-image](), [deployment](), [docker-registry](), [infrastructure-as-code](), [kubernetes](), [registry](), [terraform]() ### AI overview A tutorial shows how to use Harness Pipelines and the Harness Terraform Provider to provision a uniquely named Docker Registry, build and push a container image, and deploy it to Kubernetes. It covers Terraform execution in a CI step, passing output variables between stages, and rolling updates with automatic rollback. ### Source excerpt Provision a fresh Docker Registry with Terraform, build your container image into it, and deploy to Kubernetes in one | Blog ## Kubernetes Changed Block Tracking API - Beta Differences DevFeed: [Kubernetes Changed Block Tracking API - Beta Differences]() Original publisher: [Read original article]() Author: Prasad Ghangal Published: 2026-09-14T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [API](), [gRPC]() Tags: [2026](), [compatibility](), [container-image-registry](), [developer](), [documentation](), [kubernetes](), [registry](), [release](), [snapshots](), [storage](), [streaming](), [update]() ### AI overview This Kubernetes developer article explains the Beta changes to Changed Block Tracking (CBT) support for CSI drivers. The SnapshotMetadataService CRD moved from v1alpha1 to v1beta1, with no automatic conversion, and CBT remains limited to block volumes. It also outlines compatibility requirements and the steps for upgrading and trying the feature. ### Source excerpt Changed Block Tracking (CBT) support for CSI drivers shipped as Alpha in September 2025. With the March 2026 v1.0.0 release of the external-snapshot-metadata project, the feature moved to Beta. If you aren't yet familiar with changed block tracking for storage in Kubernetes, the Alpha announcement covers the motivation, the three primary components (the CSI SnapshotMetadata gRPC service, the SnapshotMetadataService CRD, and the external-snapshot-metadata sidecar), and a walkthrough of how to use the API. CBT currently applies to block volumes; file-volume and network file-share changed-list tracking is not covered by this feature. This post focuses on what is different in Beta. What's new in Beta The main change in that release was the promotion of the SnapshotMetadataService CRD from v1alpha1 to v1beta1. The CRD used to advertise a driver's metadata service now serves cbt.storage.k8s.io/v1beta1. The schema itself is unchanged, but this release removed v1alpha1 (rather than serving it alongside the new version). If you are upgrading from Alpha, you need to: Re-apply the CRD definition shipped with v1.0.0. Update SnapshotMetadataService manifests to use apiVersion: cbt.storage.k8s.io/v1beta1. Update any client or controller code that talks to the CRD. This is a one-time change. There is no automatic conversion between the two versions. Compatibility Minimum Kubernetes version: 1.33 CSI spec: 1.10 or newer Container image: registry.k8s.io/sig-storage/csi-snapshot-metadata:v1.0.0 Trying it out The Getting Started section in the Alpha blog still applies. In short: Make sure your CSI driver supports volume snapshots and ships the external-snapshot-metadata sidecar. Install the SnapshotMetadataService CRD (the v1beta1 definition from the v1.0.0 release). Create a SnapshotMetadataService resource for your driver. Use a client -- snapshot-metadata-lister, or your own implementation -- to call GetMetadataAllocated and GetMetadataDelta. If you want to see the full flow end-to-e ## Manage Vercel Container Registry with Vercel CLI DevFeed: [Manage Vercel Container Registry with Vercel CLI]() Original publisher: [Read original article]() Author: Andy Waller Published: 2026-08-20T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [Docker](), [Tooling]() Tags: [buildah](), [cli](), [container-registry](), [docker](), [images](), [podman](), [registry](), [vercel]() ### AI overview Vercel CLI now provides a vcr command group for managing Vercel Container Registry. Developers can connect existing container tools, authenticate with a short-lived project-scoped token, build and push images, create repositories, and inspect repositories, images, and tags. ### Source excerpt You can now manage Vercel Container Registry with Vercel CLI. The new vercel vcr command group lets you: Connect your existing container tooling Build and push images in one step Create and inspect repositories, images, and tags Authenticate your container tooling, such as Docker, Podman, or Buildah, with a short-lived token scoped to your project. Then build and push: The credentials go to Docker itself, so your existing tooling can push to VCR with standard commands: Repositories are created automatically the first time you push, or explicitly with vercel vcr add. From there, you can list what's stored and inspect individual images and tags: Update to the latest Vercel CLI with pnpm i -g vercel@latest and read the Container Registry docs to get started. Read more ## Agent Registry vs Agent Hub: Which one do you need? DevFeed: [Agent Registry vs Agent Hub: Which one do you need?]() Original publisher: [Read original article]() Author: Matar Peles Published: 2026-08-10T11:40:18Z Content type: comparison Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [AI Agent](), [Microsoft](), [Security](), [bedrock](), [Claude](), [cursor]() Tags: [agent](), [agentic](), [agents](), [ai](), [apis](), [bedrock](), [claude](), [cursor](), [enterprise](), [governance](), [hub](), [microsoft](), [policy](), [registry](), [workflow]() ### AI overview The article compares AI agent registries and agent hubs. Registries provide governance by tracking agent identity, ownership, access boundaries, versions, lifecycle state, and policy approvals, while hubs help teams discover and reuse existing agents. It argues that organizations need both capabilities and can build them as one system to address agent sprawl. ### Source excerpt Compare agent registries and agent hubs to understand their roles, key differences, and which one your team actually needs. ## 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 ## A guided tour of Terraform state, hosted modules, and HCL in Pulumi DevFeed: [A guided tour of Terraform state, hosted modules, and HCL in Pulumi]() Original publisher: [Read original article]() Author: Christian Nunciato Published: 2026-08-04T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Terraform](), [opentofu](), [Amazon S3](), [Command-line interface](), [Cloud](), [GitHub](), [Template]() Tags: [amazon-s3](), [aws](), [cli](), [github](), [hcl](), [how-to](), [infrastructure-as-code](), [modules](), [opentofu](), [pulumi-cloud](), [registry](), [s3](), [terraform](), [tutorials]() ### AI overview A hands-on walkthrough shows how to move a Terraform project that provisions an Amazon S3 bucket into Pulumi Cloud. It covers Pulumi Cloud as a Terraform state backend, hosted Terraform modules, and HCL authoring support, with references to OpenTofu and AWS. ### Source excerpt Today's big release contains a whole new set of features designed for seamless interoperability with the Terraform and OpenTofu ecosystems, and there's a lot there -- so much that it can be tough to get your head around all of it. But it generally falls into three major categories: Support for Pulumi Cloud as a Terraform state backend, including remote execution with human approvals A Terraform module registry in Pulumi Cloud that lets you publish, document, and share your modules even across language boundaries First-class support for HCL as an authoring language in the Pulumi engine To make this release a little easier to appreciate holistically, I've put together a quick end-to-end walkthrough that doesn't quite cover everything, but does cover the big stuff, and should give you a sense of how it all comes together. We'll start with a simple Terraform project that you'll deploy to AWS, and then one step at a time, bring it into Pulumi Cloud and kick the tires on each of these new features as we go. It'll take a bit, but all you'll need are a free Pulumi account and the ability to deploy an S3 bucket to AWS. We've got a bunch to cover, so let's jump right in. Start with a Terraform project Our tour begins with a tiny Terraform project that provisions a single Amazon S3 bucket using a locally defined module that we'll publish later. The project is available on GitHub as a template, and the easiest way to use it is with the GitHub CLI: $ gh repo create my-tf-project \ --template cnunciato/simple-tf-template \ --public \ --clone && cd my-tf-project We'll use the local Terraform backend to start. Set your AWS credentials (preferably with environment variables), then deploy the project with Terraform or OpenTofu. (This walkthrough uses the terraform CLI, but you can swap in tofu if that's your preference.) $ terraform init && terraform apply ... Apply complete! Resources: 2 added, 0 changed, 0 destroyed. Outputs: bucket_arn = "arn:aws:s3:::my-tf-project-bucket-14d19ece" ## Share Vercel Container Registry repositories across teams DevFeed: [Share Vercel Container Registry repositories across teams]() Original publisher: [Read original article]() Author: Andy Waller Published: 2026-08-03T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [Authorization]() Tags: [cli](), [container-registry](), [images](), [npm](), [registry](), [vercel]() ### AI overview Vercel Container Registry now supports sharing repositories across Vercel teams with read-only access to all images. Recipients can pull and use images but cannot push, delete, or re-share them. ### Source excerpt Vercel Container Registry now lets you share a repository with other Vercel teams to grant read access to its images. Sharing is read-only and covers the whole repository. Recipients can pull and use every image, but cannot push, delete, or re-share. You can also share a repository with your own team. Each repository can be shared with up to 100 teams. Share from the project dashboard under Images -> repository -> Settings -> Repository Sharing, or with the Vercel CLI: # Share a repository with a team vercel vcr permissions my-repository add other-team # List teams with access vercel vcr permissions my-repository ls # Revoke a team's access vercel vcr permissions my-repository rm other-team # Remove all shared access vercel vcr permissions my-repository clear Shared images can be used in Vercel Sandbox, accepting a team-scoped image reference in Sandbox.create() : import { Sandbox } from '@vercel/sandbox'; const sandbox = await Sandbox.create({ image: 'other-team/their-project/shared-repository:latest', }); Repository sharing is available on all plans. Update the Vercel CLI to v58.3.0 or later with npm i -g vercel@latest to get started and see the Vercel Container Registry documentation to learn more. Read more ## What's new in Graph Artifacts DevFeed: [What's new in Graph Artifacts]() Original publisher: [Read original article]() Author: Zack Warnimont Published: 2026-07-27T09:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [Platform API](), [Deployment](), [Command-line interface](), [Containers](), [CI/CD]() Tags: [announcement](), [api](), [apis](), [ci-cd](), [cli](), [container-registry](), [deployment](), [graphos](), [oci](), [registry](), [release](), [router]() ### AI overview This release adds GraphOS artifact tag management across Rover and Studio. Teams can assign, list, fetch, and delete tags from Rover, view tags alongside artifact digests in Studio, and use OCI-compliant registry APIs. User-managed tags support promotion and rollback workflows, while tag reassignment hot-reloads automatically on Router v2.11.0 and later. ### Source excerpt When we launched Graph Artifacts, we gave teams a way to pin their GraphOS Router to a specific, immutable supergraph schema version using SHA digests. Graph artifacts are stored using OCI-compliant registries, and tagging is a native concept at that layer. A tag is just a mutable pointer to an immutable digest. In principle, nothing stopped a team from tagging an artifact prod and having their router resolve it. ## The missing link in developer velocity: Virtual registries and the rise of the Artifact Platform DevFeed: [The missing link in developer velocity: Virtual registries and the rise of the Artifact Platform]() Original publisher: [Read original article]() Author: Adrian Herrera Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Caching](), [CI/CD](), [developer velocity](), [Latency](), [Developer Platform]() Tags: [article](), [caching](), [ci-cd](), [cost](), [developer](), [developer-velocity](), [latency](), [packages](), [performance](), [platform](), [registry](), [saas](), [time]() ### AI overview The article explains how artifact retrieval slows CI/CD pipelines and reduces developer velocity. It presents virtual registries combined with high-performance caching as an acceleration layer that serves artifacts locally, reduces repeated downloads and latency, and lowers cloud egress costs. ### Source excerpt Virtual registries and high-performance caching cut CI/CD artifact download time, reduce egress costs, and boost developer velocity by turning artifact delivery into a core platform capability. ## Vercel Sandbox now support Custom Images DevFeed: [Vercel Sandbox now support Custom Images]() Original publisher: [Read original article]() Author: Tom Lienard Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [toolchain](), [Docker](), [boot]() Tags: [boot](), [compute](), [container-registry](), [dependencies](), [docker](), [documentation](), [filesystem](), [images](), [os](), [performance](), [registry](), [sandbox](), [sandboxes](), [snapshots](), [toolchain](), [vercel]() ### AI overview Vercel Sandboxes now support custom images in public beta. Users can provide a custom root filesystem with their own operating system, toolchain, and dependencies. Images are pulled from Vercel Container Registry, and the feature is designed to preserve cold start performance through precompiled snapshots. ### Source excerpt Vercel Sandboxes now supports custom images. Launching in public beta today, images allow Sandboxes to start with your own custom root filesystem. Images are pulled from Vercel Container Registry, so anything you docker push is immediately available. Bring your own OS, toolchain and dependencies into the Sandbox without needing to spin up compute and create Snapshots. Images in the background for Fluid Compute and boot from a precompiled snapshot in the same format as our Sandbox Snapshots - so you get the convenience of a custom filesystem without sacrificing cold start performance. Read more about running images with Sandbox in the documentation. Read more ## Introducing VCR: Vercel Container Registry DevFeed: [Introducing VCR: Vercel Container Registry]() Original publisher: [Read original article]() Author: Wilson Wang Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Dockerfile](), [Containers](), [Authorization](), [OpenID connect (OIDC)](), [dashboards]() Tags: [authorization](), [container-images](), [container-registry](), [docker](), [infrastructure](), [oci](), [oidc](), [operations](), [registry](), [vercel](), [workflows]() ### AI overview Vercel introduces Vercel Container Registry, an OCI-compliant registry for pushing, pulling, and managing container images through standard Docker workflows. It supports project-scoped authorization, OIDC or access-token authentication, automatic optimization for Sandboxes and Functions, and integration with Vercel build and deployment workflows. ### Source excerpt You can now push, pull, and manage container images directly on Vercel. Vercel Container Registry is an OCI-compliant image registry hosted on Vercel infrastructure. It works with standard workflows like docker push, docker pull, and docker tag, so there's nothing new to learn or tooling to migrate. A Vercel project can have unlimited repositories. You can create and manage them through the Vercel dashboard, or push directly to VCR, which creates the repository for you on the fly. Operations use the same authorization controls as the rest of Vercel. You can authenticate with OIDC or an access token, provided the token has access to the project scope. Optimized for Fluid Compute When you push an image, VCR automatically optimizes it in the background for use in Sandboxes and Functions. VCR stores a precompiled snapshot and serves that snapshot when the image is requested. These snapshots use the same format as Sandbox Snapshots, which are optimized to run on Fluid Compute. Build and deploy on Vercel The Vercel build environment is automatically set up with authentication for the current project, so you can build and store images as part of the build and deploy process. You can also bring your Dockerfile to Vercel directly and host it with Vercel Functions or Vercel Sandboxes. Read more about VCR in the documentation. Read more ## Podman 6 Configuration File Changes DevFeed: [Podman 6 Configuration File Changes]() Original publisher: [Read original article]() Author: Paul Holzinger Published: 2026-06-22T16:14:55Z Content type: article Language: en Sources: [blog.podman.io]() Topics: [podman](), [configuration](), [Containers]() Tags: [announcement](), [blog](), [buildah](), [code](), [configuration](), [containers](), [files](), [git](), [go](), [image](), [libraries](), [podman](), [registry](), [releases](), [root](), [skopeo](), [storage]() ### AI overview This article introduces the major configuration-file rework planned for Podman 6. The changes affect Podman, Buildah, Skopeo, and shared container libraries, including how files such as containers.conf, registries.conf, storage.conf, policy.json, registries.d, and certs.d are handled and parsed. ### Source excerpt Podman 6 is about to be released soon, so I would like to talk about the biggest change we made: a major rework of how we handle and parse our configuration files. This does not just affect Podman but also Buildah, Skopeo, and many other tools building on top of our underlying go.podman.io/image and go.podman.io/storage [...] ## The Hidden Technical Debt Of Agentic Engineering DevFeed: [The Hidden Technical Debt Of Agentic Engineering]() Original publisher: [Read original article]() Author: Zohar Einy Published: 2026-06-20T18:56:57Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [AI Development](), [systems](), [Software](), [observability](), [CI/CD](), [Cloud]() Tags: [agentic](), [ai-agents](), [autonomous](), [ci](), [cloud](), [complexity](), [engineering](), [evals](), [governance](), [infrastructure](), [integrations](), [observability](), [registry](), [technical]() ### AI overview The article examines hidden technical debt in agentic engineering. It argues that building an AI agent is relatively easy, but deploying and operating agents in production introduces substantial infrastructure and maintenance complexity. It identifies surrounding concerns such as integrations, observability, governance, human-in-the-loop workflows, evaluations for non-deterministic systems, and agent registries. ### Source excerpt Uncover the hidden technical debt of agentic engineering and how autonomous systems introduce complexity and maintenance challenges. ## Chainguard Agent Skills is now open to everyone, with a private registry to manage your internal skills DevFeed: [Chainguard Agent Skills is now open to everyone, with a private registry to manage your internal skills]() Original publisher: [Read original article]() Published: 2026-06-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Agent Skills](), [chainguard](), [Security](), [audit trail](), [Open Source]() Tags: [agent-skills](), [ai-agent-skills](), [audit-trail](), [chainguard](), [chainguard-agent-skills](), [chainguard-ai-agents](), [chainguard-skills](), [cursor](), [hardening](), [private-registry](), [registry](), [security]() ### AI overview Chainguard Agent Skills is now available to all users with more than 1,000 hardened community skills, a private registry for internal skills, and a closed beta for hardening first-party skills. The service is intended to help organizations securely standardize, distribute, and manage AI agent skills. ### Source excerpt Chainguard Agent Skills now offers 1,000+ hardened community skills, private registries, and beta hardening for first-party AI agent skills. ## Eliminating Kubernetes Image Signature Replication DevFeed: [Eliminating Kubernetes Image Signature Replication]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2026-06-05T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [Replication](), [container images](), [Routing (disambiguation)](), [Latency](), [Google]() Tags: [cloud](), [container-images](), [cosign](), [kubernetes](), [latency](), [manifest](), [oidc](), [registry](), [replication](), [route](), [routing](), [sha256](), [signing](), [verify]() ### AI overview This article explains how Kubernetes eliminated replication of image signatures across 22 regional registries. Because signatures are small and regional latency is negligible, archeio now routes signature requests to a canonical registry while image layers continue using geo-routing. ### Source excerpt The image promoter rewrite laid the groundwork for simplifying how Kubernetes delivers container image signatures. One of the rewrite phases (Phase 6) separated image signing from signature replication into distinct pipeline stages. This follow-up covers the next step: eliminating signature replication entirely. The problem After promoting container images to registry.k8s.io, the promoter signs them using cosign with keyless (OIDC) signatures. These signatures are stored as OCI artifacts alongside the images, tagged with the convention sha256-.sig and sha256-.att. The registry.k8s.io domain is backed by archeio , a thin redirector that routes container image requests to the nearest regional Google Artifact Registry backend. When a user in Europe pulls an image, archeio redirects them to europe-west2-docker.pkg.dev; a user in Asia gets redirected to asia-east1-docker.pkg.dev, and so on across 22 regional backends. This geo-routing is great for image layers, where download locality matters for performance. But it created a problem for signatures: if the promoter only wrote a signature to one region, cosign verify would fail for users redirected to any other region. The solution was a dedicated replication pipeline that copied every .sig and .att tag to all 22 regional backends. This pipeline ran as a periodic Prow job every 2 hours on weekdays, performing thousands of API calls per run: listing tags across all repositories, diffing what existed where, and copying the missing signatures. The insight Signatures and attestations are small metadata artifacts, typically a few kilobytes each. Unlike image layers where geo-locality provides meaningful download performance improvements, fetching a signature from a non-local region adds negligible latency. The entire replication pipeline existed to optimize for a latency difference that users would never notice. The solution Instead of replicating signatures everywhere, archeio was taught to route signature req ## Axios package compromise and remediation steps DevFeed: [Axios package compromise and remediation steps]() Original publisher: [Read original article]() Author: Vercel Security Published: 2026-03-31T13:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [npm](), [vulnerability](), [API keys](), [Databases]() Tags: [2026](), [axios](), [dependency](), [package-compromise](), [registry](), [supply-chain](), [tokens](), [update](), [vercel](), [vulnerability]() ### AI overview Vercel describes the compromise of the axios npm package in an active supply chain attack discovered on March 31, 2026. The affected versions are axios@1.14.1 and axios@0.30.4, with plain-crypto-js@4.2.1 also identified in compromised dependency chains. Vercel says its systems, infrastructure, and applications were not affected, and reports that the malicious versions were blocked and unpublished while the latest tag points to axios@1.14.0. ### Source excerpt The axios npm package was compromised in an active supply chain attack discovered on March 31, 2026. Vercel investigated this issue and implemented remediation actions to protect the platform. No Vercel systems were affected. The npm registry removed the compromised package versions, and the latest tag now points to the safe axios@1.14.0 release. We've blocked outgoing access from our build infrastructure to the Command & Control hostname sfrclak.com. The malicious version of the package has been blocked and unpublished from npm. Vercel's own infrastructure and applications have been unaffected. We recommend checking your supply chain for exposure. Affected versions Projects using axios@1.14.1 or axios@0.30.4 in their build environments are affected by this vulnerability. Check your dependencies and lockfiles for: axios@1.14.1 axios@0.30.4 plain-crypto-js@4.2.1 Resolution If your deployments used the malicious package version listed above in your build environment, take the following actions: Search your lockfiles and node_modules for plain-crypto-js to identify compromised installations Redeploy your project to ensure your build uses a clean version of axios Rotate API keys, database credentials, tokens, and any other sensitive values present in your build environment Review your dependency tree for references to axios@1.14.1 or axios@0.30.4 and update them to axios@1.14.0 Read more ## Introducing the Apache Airflow Registry DevFeed: [Introducing the Apache Airflow Registry]() Original publisher: [Read original article]() Author: Apache Airflow Published: 2026-03-19T00:00:00Z Content type: release Language: en Sources: [Apache Airflow Blog]() Topics: [airflow](), [Data pipelines](), [API](), [JSON]() Tags: [airflow](), [apache](), [apache-airflow](), [community](), [data-pipelines](), [messaging](), [notifications](), [openai](), [registry]() ### AI overview Apache Airflow launches the Airflow Registry, a searchable catalog of official providers and modules. It includes provider and module search, installation and compatibility details, connection generation in URI, JSON, and environment-variable formats, ecosystem statistics, and a structured JSON API. ### Source excerpt Today we're launching the Apache Airflow Registry -- a searchable catalog of every official Airflow provider and its modules, live at airflow.apache.org/registry/. Need an S3 operator? A Snowflake hook? An OpenAI sensor? The Registry helps you find, compare, and configure the right components for your data pipelines -- without digging through docs or PyPI pages. By the Numbers 98 Official providers 1,602 Modules (operators, hooks, sensors, triggers, transfers, and more) 329M+ Monthly PyPI downloads across all providers 125+ Integrations with cloud platforms, databases, ML tools, and messaging services Search Everything Hit Cmd+K from any page and start typing. Results show up instantly, grouped by Providers and Modules, with type badges so you can tell a hook from an operator at a glance. Provider Pages Each provider gets a dedicated page with everything in one place: install command with copy-to-clipboard, version selector, extras dropdown, compatibility info, connection types, and the full module listing organized by type. The Amazon provider, for example, has 372 modules across operators, hooks, sensors, triggers, transfers, and more. Module type tabs let you filter to exactly what you're looking for, and a category sidebar groups modules by AWS service (S3, Lambda, Glue, Step Functions, etc.). Connection Builder Click any connection type badge on a provider page, fill in the fields, and the builder generates the connection in three formats -- URI, JSON, and Env Var -- ready to copy into your configuration. No more guessing URI encoding or JSON structure. Explore by Category Not sure which provider you need? The Explore page organizes providers into categories: Cloud Platforms, Databases, Data Warehouses, Messaging & Notifications, AI & Machine Learning, Data Processing, and more. Statistics The Stats page breaks down the ecosystem: 848 operators, 298 hooks, 164 triggers, 157 sensors, 83 transfers, and more -- plus top providers by downloads and module count. JSON API ## How To Publish To NPM From GitHub Actions DevFeed: [How To Publish To NPM From GitHub Actions]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-02-23T05:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [npm](), [GitHub Actions](), [GitHub](), [releases]() Tags: [2026](), [github](), [github-actions](), [how-to](), [modular-development](), [npm](), [process](), [published](), [registry](), [workflow]() ### AI overview A tutorial explains how to replace revoked personal NPM tokens with trusted publishing from GitHub Actions. It covers configuring the NPM package, repository, and workflow, then updating the CI workflow to use limited permissions and publish releases without the old token. ### Source excerpt At the end of 2025, NPM registry ## Introducing Multiple Registry Support on DigitalOcean Container Registry DevFeed: [Introducing Multiple Registry Support on DigitalOcean Container Registry]() Original publisher: [Read original article]() Author: Ravish Ahmad Khan Published: 2026-01-09T21:12:58Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [container](), [Development](), [Kubernetes]() Tags: [announce](), [availability](), [container](), [digitalocean](), [feature](), [kubernetes](), [product-updates](), [registry]() ### AI overview DigitalOcean announces multiple registry support for DigitalOcean Container Registry, allowing teams to create and manage separate registries for distinct environments or distributed teams. The article describes benefits including environment isolation, regional placement, and support for data-residency requirements. ### Source excerpt Introducing Multiple Registry Support on DigitalOcean Container Registry At DigitalOcean, we're dedicated to enhancing our container registry experience, providing users with a simple, powerful tool to organize, manage, and deploy containerized applications. Today, we're excited to announce the General Availability (GA) of a major enhancement to our container registry: the ability to create and manage multiple registries under a single team. Available to customers on the Professional Plan at no additional cost, this feature enables the creation of up to 10 registries per team, delivering great flexibility of image rollout on DigitalOcean. What is Multi-Registry support, and why does it matter? Previously, although one DigitalOcean Container Registry (DOCR) account could create multiple teams, each team was limited to a single container registry. With this update, Professional Plan customers can now create up to 10 registries under a single team, each housing its own independent set of repositories and configurations. This architecture is designed for users managing distinct environments (like development, staging, production) or distributed teams, allowing for compartmentalized registry management. Benefits of Multiple Registries Environment isolation: Segregate different deployment stages (such as dev vs. prod). Regional performance: Provision registries in specific regions (like fra1 or nyc3) to co-locate images with your Kubernetes clusters. This reduces latency and data transfer costs during image pulls. Regulatory compliance: For users with strict data residency requirements (such as GDPR), multiple registries enhance compliance by ensuring container artifacts are stored within a specific geographical jurisdiction. Ready for DOCR's future enhancements: This multi-registry foundation paves the way for DOCR's future advanced capabilities like registry mirroring and geo-replication. How to use the new Multi-Registry feature on DigitalOcean 1. Via the Control Panel ## Santa's Python Pitfalls: A Java Developer's Guide to Staying Safe This Christmas DevFeed: [Santa's Python Pitfalls: A Java Developer's Guide to Staying Safe This Christmas]() Original publisher: [Read original article]() Author: Steve Poole Published: 2025-12-24T03:03:09Z Content type: tutorial Language: en Sources: [Java Advent Calendar]() Topics: [Python](), [pip](), [PyPI](), [Maven Central](), [Java](), [Maven]() Tags: [2025](), [attacks](), [dependency](), [developer](), [guide](), [install](), [internet](), [java](), [maven-central](), [mirror](), [model](), [packaging](), [pitfalls](), [pypi](), [python](), [registry](), [trust]() ### AI overview A Java-focused guide to Python package-management risks. It contrasts Maven Central with PyPI, highlighting flat package naming, trusting dependency resolution, typosquatting, dependency confusion, and unsafe installation commands. It recommends version pins, known sources, private registries, and lock files. ### Source excerpt Just like that it happened. You, a disciplined Java developer, are now installing Python. Like everything in 2025, it just arrived. One day, you were running a tidy mvn install, the next, you're learning about virtual environments and fighting an unfriendly pip install that won't explain what it just pulled from the internet. Good news: [...] The post Santa's Python Pitfalls: A Java Developer's Guide to Staying Safe This Christmas appeared first on JVM Advent. ## I made Windows use UTC with Linux dual boot DevFeed: [I made Windows use UTC with Linux dual boot]() Original publisher: [Read original article]() Author: Tom Published: 2025-12-14T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Linux](), [Windows](), [boot](), [Hardware]() Tags: [best-practices](), [debian](), [dual-boot](), [hardware](), [hardware-clock](), [linux](), [registry](), [time-synchronization](), [timedatectl](), [utc](), [windows]() ### AI overview A tutorial explains how to configure Windows and Linux to use UTC for the hardware clock in a dual-boot setup, helping avoid clock conflicts and time synchronization issues. ### Source excerpt Configure Windows to use UTC for the hardware clock when dual-booting with Linux, avoiding time synchronization issues and maintaining Linux defaults. ## Introducing New Updates to the Chainguard Images Directory DevFeed: [Introducing New Updates to the Chainguard Images Directory]() Original publisher: [Read original article]() Published: 2025-11-12T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard images](), [container images](), [Containers](), [Kubernetes](), [Deployment](), [Open Source]() Tags: [bitnami-helm-charts](), [chainguard](), [chainguard-catalog](), [chainguard-console](), [chainguard-containers](), [chainguard-helm-charts](), [chainguard-images](), [chainguard-images-directory](), [compare](), [container-images](), [containers](), [cost](), [cve](), [demo](), [deployment](), [helm](), [helm-charts](), [kubernetes](), [oci](), [registry](), [secure-by-design](), [updates](), [zero-cve-containers]() ### AI overview Chainguard has updated its Images Directory with an embedded ROI calculator, Helm Charts for Kubernetes deployments, and refreshed data about the Chainguard Factory. The calculator compares CVE counts and remediation costs, while the Helm Charts provide drop-in replacements for popular open source applications using Chainguard Containers and OCI delivery. ### Source excerpt We've improved the Chainguard Images Directory with Helm charts for faster deployments, an ROI calculator, and more refreshed data to improve your experience. ## Introducing the Self-Serve Catalog Experience DevFeed: [Introducing the Self-Serve Catalog Experience]() Original publisher: [Read original article]() Published: 2025-11-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [container images](), [API](), [Provisioning]() Tags: [catalog](), [chainguard](), [chainguard-catalog-pricing](), [chainguard-console](), [chainguard-custom-assembly](), [chainguard-migration](), [chainguard-self-serve-experience](), [container-images](), [provisioning](), [registry](), [self-serve-chainguard]() ### AI overview Chainguard has generally released its Self-Serve Experience for Catalog customers. Organization owners can browse the catalog and add, rename, or remove container images directly through the Chainguard Console, API, or chainctl, without provisioning requests or approval delays. ### Source excerpt Chainguard launches the Self-Serve Experience for Catalog customers: instantly add, rename, or remove container images from our catalog, no tickets required. ## Securely Signing WebAssembly Components with Cosign (OIDC) DevFeed: [Securely Signing WebAssembly Components with Cosign (OIDC)]() Original publisher: [Read original article]() Author: Liam Randall Published: 2025-09-02T00:00:00Z Content type: tutorial Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [sigstore](), [GitHub Container Registry](), [OpenID connect (OIDC)](), [Rust](), [Command-line interface](), [Authentication](), [Security]() Tags: [authentication](), [cli](), [cosign](), [github-container-registry](), [integrity](), [oci-registry](), [oidc](), [registry](), [security](), [signing](), [sigstore](), [supply-chain](), [supply-chain-security](), [verify](), [wasi](), [wasm-components](), [wasmcloud](), [webassembly](), [webassembly-wasmcloud-security-cosign-oidc-signing-oci-registry-supply-chain-security-wasi-wasm-comp]() ### AI overview A tutorial showing how to build a Rust-based WebAssembly component, sign it with Sigstore Cosign using OIDC identity, push it to GitHub Container Registry, and verify it before execution. ### Source excerpt Build, sign, and verify WebAssembly component artifacts using Sigstore's cosign with OIDC identity--secure, registry-native signatures for wasmCloud. [Next page]()