# Manifest Published articles for Manifest. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Agent Plugins package your skills, tools, and more DevFeed: [Agent Plugins package your skills, tools, and more]() Original publisher: [Read original article]() Author: Kevin Hou; Haoyu Wang; Alan Blount Published: 2026-09-12T11:04:33.891311Z Content type: article Language: en Sources: [Google Developers Blog]() Topics: [Agent Skills](), [Model Context Protocol (MCP)](), [MCP Server](), [Google](), [amazon](), [Microsoft](), [OpenAI](), [Vercel]() Tags: [agent-skills](), [amazon](), [google](), [maintainers](), [manifest](), [mcp](), [mcp-server](), [microsoft](), [openai](), [plugin](), [portable](), [skills](), [vercel]() ### AI overview The article introduces Agent Plugins 1.0.0, a vendor-neutral specification for packaging Agent Skills and MCP servers into portable plugins. It standardizes the manifest and directory layout so developers can distribute one package across clients while preserving client-specific flexibility. Google is joining the Core Maintainers and beginning support in its products. ### Source excerpt Agent Plugins 1.0.0 is a new, vendor-neutral directory specification--backed by Google, Amazon, Microsoft, and others--for packaging Agent Skills and MCP servers into a single portable unit. By standardizing the manifest (plugin.json) and utilizing a fixed directory layout, it eliminates the need for developers to maintain separate wrappers or configurations to support different AI coding agents and IDEs. Google has officially joined as a Core Maintainer and already rolled out support in the Agents CLI and Data Agent Kit, allowing developers to start building and distributing interoperable plugins today. ## Deployment step now 10% faster DevFeed: [Deployment step now 10% faster]() Original publisher: [Read original article]() Author: Javi Velasco Published: 2026-09-08T22:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [CI/CD]() Tags: [manifest](), [routing]() ### AI overview Vercel made its deployment step about 10% faster by combining per-function routing metadata into one manifest upload. The improvement applies automatically to all builds. ### Source excerpt The deployment step is now about 10% faster, saving one second on average. Large applications can save up to 12 seconds. Previously, Vercel uploaded a separate routing metadata file for each function path. That metadata is now combined into a single manifest and uploaded once. This improvement applies automatically to all builds. No changes are required. Learn more about builds in the documentation. Read more ## Kubernetes v1.37: Storage Version Migration Enabled by Default DevFeed: [Kubernetes v1.37: Storage Version Migration Enabled by Default]() Original publisher: [Read original article]() Author: Michael Aspinwall Published: 2026-08-31T18:30:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [migration](), [API](), [Encryption](), [releases]() Tags: [api](), [encryption](), [kubernetes](), [manifest](), [migration](), [releases](), [support](), [v1]() ### AI overview Kubernetes v1.37 makes Storage Version Migration generally available and enables it by default. The built-in API and control-plane controller migrate existing stored resources to the current storage version, addressing stale versions, encryption-at-rest changes, and key rotation. ### Source excerpt I am excited that storage version migration (SVM) has graduated to General Availability (GA) in Kubernetes v1.37! After a number of releases of work and testing, the built-in StorageVersionMigration API (storagemigration.k8s.io/v1) and control plane controller are now fully stable and enabled by default across all v1.37 Kubernetes clusters. The problem with stale storage versions In Kubernetes, stored API resources are written using a specific storage version (schema representation). The way Kubernetes interacts with object storage fundamentally requires mutation of a resource in order to ensure that the latest storage version is used for all resources. This creates problems when you want to change the storage version of a resource. One example of a scenario where you may want to change the storage version of a resource is when you are promoting a CRD to drop an older API version (such as v1alpha1) to a newer version (leaving just v1beta1 and v1). It's a problem to drop the older API version whilst there are still resources stored with the old alpha version. To avoid problems, you designate v1 as the new storage version; but, on it's own, that's not enough. While new writes are stored as v1, any existing resource could remain stored as v1alpha1 or v1beta1 in storage. You cannot safely remove v1alpha1 from the CRD's .status.storedVersions or drop serving support until every single resource in storage has been re-written to not be serialized and stored with the alpha version. Another relevant example is encryption at rest and, related, key rotation. When you configure encryption at rest or rotate encryption keys, existing resources in storage remain unencrypted (or encrypted under old keys) until they are actively re-written through the Kubernetes API server. Historically, cluster administrators and CRD authors had to rely on manual kubectl get / kubectl replace scripts, or to deploy the out-of-tree kube-storage-version-migrator component to force re-writes. These app ## Optimizing Kubernetes pods for reliability with topology spread constraints DevFeed: [Optimizing Kubernetes pods for reliability with topology spread constraints]() Original publisher: [Read original article]() Author: Andre Newman Published: 2026-08-13T00:00:00Z Content type: tutorial Language: en Sources: [Gremlin Blog]() Topics: [Kubernetes](), [Availability]() Tags: [availability](), [blog](), [how-to](), [kubernetes](), [manifest]() ### AI overview This blog explains how Kubernetes topology spread constraints distribute pods across failure domains such as availability zones, regions, and nodes. It covers their reliability benefits, configuration through spec.topologySpreadConstraints, and the main constraint fields and behaviors. ### Source excerpt Topology spread constraints let you determine how Kubernetes spreads pod replicas across failure domains, such as availability zones and regions. This blog explains how they work, how to configure them, and how to scan for missing constraints. ## Visual Studio Code 1.133 DevFeed: [Visual Studio Code 1.133]() Original publisher: [Read original article]() Author: Visual Studio Code Team Published: 2026-08-12T17:00:00Z Content type: release Language: en Sources: [Visual Studio Code - Code Editing. Redefined.]() Topics: [Visual Studio Code](), [GitHub Copilot CLI](), [GitHub Copilot app](), [MCP Server](), [SDKs](), [API keys](), [EJS]() Tags: [api](), [claude](), [copilot](), [github-copilot](), [html](), [manifest](), [mcp-server](), [plugin](), [plugins](), [release](), [sdk](), [visual-studio](), [vs-code]() ### AI overview Visual Studio Code 1.133 introduces more flexible Claude sessions, including provider switching between turns and API-key access when GitHub sign-in is unavailable. It also adds an agent host for sharing sessions across VS Code windows, support for the Agent Plugins standard, and automatic reloading for HTML previews. ### Source excerpt Learn what's new in Visual Studio Code 1.133 Read the full article ## Moving the Microsoft Edge extensions ecosystem forward with Manifest Version 3 DevFeed: [Moving the Microsoft Edge extensions ecosystem forward with Manifest Version 3]() Original publisher: [Read original article]() Author: Microsoft Edge Team Published: 2026-08-07T15:54:07Z Content type: news Language: en Sources: [Microsoft Edge Blog]() Topics: [Edge](), [Extension](), [migration](), [Chromium](), [Microsoft](), [Security]() Tags: [chromium](), [developer](), [ecosystem](), [edge](), [extensions](), [manifest](), [microsoft](), [microsoft-edge](), [migration](), [security](), [uncategorized]() ### AI overview Microsoft Edge announces the next phase of its transition from Manifest V2 to Manifest V3 for extensions. Consumer migration begins in August 2026 and is expected to finish by the end of 2026, followed by enterprise deprecation in early 2027. ### Source excerpt Back in 2020, we committed to Manifest Version 3 (MV3) as the future direction of the Chromium extensions platform. Since then, we've worked with developer The post Moving the Microsoft Edge extensions ecosystem forward with Manifest Version 3 appeared first on Microsoft Edge Blog. ## Introducing Agent Plugins DevFeed: [Introducing Agent Plugins]() Original publisher: [Read original article]() Author: Jonathan Hefner Published: 2026-08-06T00:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Agent Skills](), [Model Context Protocol (MCP)](), [MCP Server](), [JSON](), [Artificial Intelligence](), [Extension]() Tags: [agent-skills](), [json](), [manifest](), [mcp](), [mcp-server](), [plugin](), [plugins](), [validation]() ### AI overview Agent Plugins 1.0.0 is an open, vendor-neutral standard for packaging Agent Skills and MCP servers into distributable plugins. It defines a directory structure with a plugin.json manifest and fixed component locations, while leaving installation, distribution, policy, user experience, and client-specific capabilities to individual clients. ### Source excerpt Today, Agent Plugins 1.0.0 is publicly available. Agent Plugins is an open, vendor-neutral standard for plugins that extend AI agents. Agent Skills provide reusable instructions and resources for AI agents. MCP servers connect agents to tools and services. Both can be reused across clients, but clients often package and discover them differently. Agent Plugins gives compatible clients a common format: a directory with a plugin.json manifest and fixed locations for its components. The format is intentionally small and easy to implement, and it leaves installation, distribution, policy, user experience, and client-specific capabilities to each client. One package for the portable parts Extension authors often adapt the same component to several client formats. Even though the underlying Skill or MCP server is identical, clients often expect different top-level metadata, discovery paths, or MCP configuration. Agent Plugins gives those shared components one predictable, structured home: A minimal JSON manifest (plugin.json) identifies the specification version and names the plugin: Those two fields are the minimum requirement for the manifest, and the rest of the contract is represented in the file structure of the directory itself. A reusable component should not need to be repackaged for every client, so the format specifies only what a client needs to discover and load what is inside. Every compatible client checks for plugin.json at the plugin root. Clients that support Skills discover them under skills/. Clients that support MCP servers read their configuration from mcp.json. A client can support either component type or both. After the client validates the manifest, components are validated independently, so one invalid component does not disable unrelated ones. For plugin authors, that means fewer client-specific conventions for the same component. For client implementers, the specification defines a small, deterministic contract for discovery, validation, and lo ## Introducing Agent Plugins 1.0.0 DevFeed: [Introducing Agent Plugins 1.0.0]() Original publisher: [Read original article]() Author: Jonathan Hefner Published: 2026-08-06T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Agent Skills](), [Model Context Protocol](), [client](), [JSON](), [ChatGPT](), [codex](), [cursor](), [GitHub](), [Kiro](), [vs-code]() Tags: [agent](), [agent-skills](), [announcement](), [chatgpt](), [codex](), [cursor](), [distribution](), [github](), [github-copilot](), [guide](), [kiro](), [manifest](), [mcp](), [plugins](), [policy](), [portable](), [skills](), [user-experience](), [vs-code]() ### AI overview Agent Plugins 1.0.0 is an open, vendor-neutral standard for packaging Agent Skills and MCP servers into portable plugins. It defines a common root manifest and fixed component locations while allowing each compatible client to control installation, distribution, policy, user experience, and client-specific capabilities. ### Source excerpt Agent Plugins 1.0.0 is now available. It is an open, vendor-neutral standard for packaging Agent Skills and MCP servers into portable plugins. Compatible agent clients can discover and load them. Agent Plugins defines a common format: a root plugin.json manifest, plus fixed locations for portable components. Each client keeps control of installation, distribution, policy, user experience, and client-specific capabilities. At launch, Agent Plugins is supported across the following clients: ChatGPT and Codex Cursor GitHub Copilot Kiro VS Code Read the specification and implementation guides, learn more in the announcement post, and follow our guide to build a plugin on the new standard. Read more ## Inside the keyv npm Compromise: preinstall Malware, Trusted Provenance, and IDE Hooks DevFeed: [Inside the keyv npm Compromise: preinstall Malware, Trusted Provenance, and IDE Hooks]() Original publisher: [Read original article]() Author: Liran Tal; Lion Kontorer Published: 2026-08-04T04:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [incident](), [releases]() Tags: [awareness](), [blog](), [ci](), [ci-cd](), [code](), [developer](), [devops](), [embedded](), [enablement](), [ide](), [incident](), [javascript](), [malware](), [manifest](), [node-js](), [npm-packages](), [open-source-security](), [payload](), [persistence](), [releases](), [research](), [scm](), [secrets](), [security](), [security-labs](), [snyk-learn](), [snyk-open-source](), [snyk-security-intel](), [software](), [supply-chain](), [supply-chain-security](), [vulnerability-insights]() ### AI overview Snyk reports an active supply-chain incident in which keyv 6.0.0 and ten related npm releases contained install-time malware. The article describes the malicious preinstall hook, its second-stage payload, affected-release investigation, and remediation guidance. ### Source excerpt keyv 6.0.0 and ten related npm releases shipped install-time malware. See affected versions, hashes, detection steps, and safe remediation order. ## Dry-run deployments with Vercel CLI DevFeed: [Dry-run deployments with Vercel CLI]() Original publisher: [Read original article]() Author: Melkey Moksyakov Published: 2026-07-01T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [CI/CD]() Tags: [agents](), [automation](), [manifest]() ### AI overview Vercel CLI adds dry-run deployments that preview the framework preset and deployment file manifest before code is uploaded or a deployment is created. ### Source excerpt You can now preview the framework preset and files that Vercel CLI includes in a deployment before creating one. Run vercel deploy --dry from a linked project: For automation or further inspection, return the complete file manifest as JSON: JSON output includes the detected framework, included and ignored paths, directory size distribution, largest files, file modes, and content hashes. Piped and other non-TTY output automatically uses JSON. Agents can use this manifest as a pre-deployment check, verifying framework detection, identifying unexpected or missing files, flagging oversized assets or unusual file modes, and updating .vercelignore or project configuration. Agents can rerun the check until the manifest matches the intended deployment, without uploading code or creating a deployment. Update the Vercel CLI to v54.17.2 or later to get started. Learn more in the vercel deploy documentation. Read more ## Agentic Resource Discovery: Let agents search DevFeed: [Agentic Resource Discovery: Let agents search]() Original publisher: [Read original article]() Author: ben burtenshaw; shaun smith Published: 2026-06-17T00:00:00Z Content type: article Language: en Sources: [Hugging Face - Blog]() Topics: [AI Bots](), [MSP MCP]() Tags: [agentic](), [agents](), [announcement](), [api](), [artificial-intelligence](), [compliance](), [hub](), [hugging-face](), [manifest](), [mcp](), [mcp-server](), [open](), [resource](), [search](), [skills](), [tool](), [tools]() ### AI overview The article introduces Agentic Resource Discovery (ARD), a draft open specification for cataloging and searching agent capabilities across federated registries. It describes Hugging Face's Discover Tool as a reference implementation that lets agents discover skills, ML applications, and MCP servers dynamically. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## 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 ## Seamless PWA origin migration: Change domains without losing users DevFeed: [Seamless PWA origin migration: Change domains without losing users]() Original publisher: [Read original article]() Author: Dibyajyoti Pal LinkedIn Dan Murphy X LinkedIn Marijn Kruisselbrink LinkedIn Published: 2026-06-03T07:00:00Z Content type: article Language: en Sources: [developer.chrome.com: Blog]() Topics: [PWA](), [migration](), [Chrome](), [Security](), [User Experience](), [Web](), [Web app]() Tags: [chrome](), [dialog](), [feature](), [how-to](), [manifest](), [migration](), [security](), [update](), [user-experience](), [web](), [web-apps]() ### AI overview Chrome 150 introduces PWA Origin Migration, allowing installed Progressive Web Apps to transition to a new same-site origin while keeping users informed through an update dialog. The article explains the old and destination manifest requirements, the migration handshake, rollout behavior, and update considerations. ### Source excerpt From Chrome 150 you can seamlessly transition a PWA to a new same-site origin. ## Kubernetes v1.36: Admission Policies That Can't Be Deleted DevFeed: [Kubernetes v1.36: Admission Policies That Can't Be Deleted]() Original publisher: [Read original article]() Author: Anish Ramasekar; Benjamin Elder Published: 2026-05-04T18:35:00Z Content type: article Language: en Sources: [Kubernetes Blog]() Topics: [Kubernetes](), [Security](), [configuration](), [API](), [Authorization]() Tags: [api](), [kubernetes](), [manifest](), [operations](), [policy](), [resources](), [security](), [server]() ### AI overview Kubernetes v1.36 introduces an alpha manifest-based admission control feature. Admission webhooks and CEL-based policies can be stored as files, loaded by the API server at startup, and applied before it serves requests. The approach addresses bootstrap gaps and helps prevent privileged users from deleting critical admission configuration. ### Source excerpt If you've ever tried to enforce a security policy across a fleet of Kubernetes clusters, you've probably run into a frustrating chicken-and-egg problem. Your admission policies are API objects, which means they don't exist until someone creates them, and they can be deleted by anyone with the right permissions. There's always a window during cluster bootstrap where your policies aren't active yet, and there's no way to prevent a privileged user from removing them. Kubernetes v1.36 introduces an alpha feature that addresses this: manifest-based admission control. It lets you define admission webhooks and CEL-based policies as files on disk, loaded by the API server at startup, before it serves any requests. The gap we're closing Most Kubernetes policy enforcement today works through the API. You create a ValidatingAdmissionPolicy or a webhook configuration as an API object, and the admission controller picks it up. This works well in steady state, but it has some fundamental limitations. During cluster bootstrap, there's a gap between when the API server starts serving requests and when your policies are created and active. If you're restoring from a backup or recovering from an etcd failure, that gap can be significant. There's also a self-protection problem. Admission webhooks and policies can't intercept operations on their own configuration resources. Kubernetes skips invoking webhooks on types like ValidatingWebhookConfiguration to avoid circular dependencies. That means a sufficiently privileged user can delete your critical admission policies, and there's nothing in the admission chain to stop them. We - Kubernetes SIG API Machinery - wanted a way to say "these policies are always on, full stop." How it works You add a staticManifestsDir field to the AdmissionConfiguration file that you already pass to the API server via --admission-control-config-file. Point it at a directory, drop your policy YAML files in there, and the API server loads them before it start ## How to Use Transformers.js in a Chrome Extension DevFeed: [How to Use Transformers.js in a Chrome Extension]() Original publisher: [Read original article]() Author: Nico Martin Published: 2026-04-23T00:00:00Z Content type: tutorial Language: en Sources: [Hugging Face - Blog]() Topics: [Chrome extension](), [transformers.js](), [gemma4](), [Artificial Intelligence](), [Local AI](), [Open Source](), [Code]() Tags: [artificial-intelligence](), [chrome](), [chrome-extension](), [code](), [extension](), [github](), [guide](), [inference](), [javascript](), [local](), [local-ai](), [manifest](), [on-device](), [open](), [open-source](), [transformers](), [transformers-js](), [ui](), [web]() ### AI overview A developer guide to building a local AI Chrome extension with Transformers.js under Manifest V3. It explains an architecture with a background service worker hosting models, a side-panel chat interface, and a content script for page extraction and highlighting, using the Gemma 4 Browser Assistant as a reference. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## Streamlining Security Investigations with Agents DevFeed: [Streamlining Security Investigations with Agents]() Original publisher: [Read original article]() Author: Dominic Marks Published: 2025-12-01T16:00:42Z Content type: article Language: en Sources: [Engineering at Slack]() Topics: [AI Chat](), [MSP MCP]() Tags: [agents](), [ai](), [ai-agents](), [coding](), [data](), [design](), [development](), [engineering](), [events](), [infrastructure](), [manifest](), [mcp](), [mcp-server](), [performance](), [security](), [series](), [slack](), [software-engineering](), [uncategorized]() ### AI overview Slack Security Engineering describes an AI-agent prototype for investigating security alerts. To improve consistency and control beyond prompt refinement, the team decomposes investigations into chained model invocations with defined purposes and output structures, and exposes selected data sources through an stdio MCP server. ### Source excerpt Slack's Security Engineering team is responsible for protecting Slack's core infrastructure and services. Our security event ingestion pipeline handles billions of events per day from a diverse array of data sources. Reviewing alerts produced by our security detection system is our primary responsibility during on-call shifts. We're going to show you how we're using AI... ## The mysterious supply chain concern of string-width-cjs npm package DevFeed: [The mysterious supply chain concern of string-width-cjs npm package]() Original publisher: [Read original article]() Author: Liran Tal Published: 2024-10-03T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [npm](), [supply-chain-security](), [Security](), [Pull Request](), [Open Source]() Tags: [awareness](), [blog](), [code-security](), [dependencies](), [developer](), [devrel](), [javascript](), [malicious-packages](), [manifest](), [node-js](), [npm](), [open-source-security](), [pull-request](), [security](), [snyk](), [snyk-code](), [snyk-open-source](), [supply-chain](), [supply-chain-security]() ### AI overview The article explains how npm package aliasing works and how it can create supply-chain security risks. It describes a benign pull request that prompted an investigation using lockfile-lint, which uncovered suspicious package names and potential malicious look-alikes on the public npm registry. ### Source excerpt Npm package aliasing can be a security threat. Learn about how malicious actors can exploit this feature to introduce fake packages into your projects. Protect your projects with best practices and stay vigilant against supply chain attacks. ## Manifest V2 phase-out begins DevFeed: [Manifest V2 phase-out begins]() Original publisher: [Read original article]() Author: Chromium Blog (noreply@blogger.com) Published: 2024-05-30T16:45:00Z Content type: article Language: en Sources: [Chromium Blog]() Topics: [Extension](), [Chrome](), [migration](), [Security](), [Security & Privacy](), [Document Object Model (DOM)](), [uBlock Origin Filters]() Tags: [chrome](), [collaboration](), [community](), [extension](), [extensions](), [feature](), [manifest](), [migration](), [none](), [performance](), [security](), [security-privacy](), [update]() ### AI overview Chrome has begun disabling extensions that still use Manifest V2. The article describes the transition to Manifest V3, which is intended to improve extension security, privacy, performance, and trustworthiness while preserving existing functionality. It highlights community-driven improvements, including user scripts, offscreen documents for DOM APIs, larger declarativeNetRequest rulesets, faster review of safe rule updates, and version rollback. More than 85% of actively maintained Chrome Web Store extensions were reported to use Manifest V3. ### Source excerpt Update (10/10/2024): We've started disabling extensions still using Manifest V2 in Chrome stable. Read more details in the MV2 support timeline documentation. In November 2023, we shared a timeline for the phasing out of Manifest V2 extensions in Chrome. Based on the progress and feedback we've seen from the community, we're now ready to roll out these changes as scheduled. We've always been clear that the goal of Manifest V3 is to protect existing functionality while improving the security, privacy, performance and trustworthiness of the extension ecosystem as a whole. We appreciate the collaboration and feedback from the community that has allowed us - and continues to allow us - to constantly improve the extensions platform. Addressing community feedback We understand migrations of this magnitude can be challenging, which is why we've listened to developer feedback and spent years refining Manifest V3 to support the innovation happening across the extensions community. This included adding support for user scripts and introducing offscreen documents to allow extensions to use DOM APIs from a background context. Based on input from the extension community, we also increased the number of rulesets for declarativeNetRequest, allowing extensions to bundle up to 330,000 static rules and dynamically add a further 30,000. You can find more detail in our content filtering guide. This month, we made the transition even easier for extensions using declarativeNetRequest with the launch of review skipping for safe rule updates. If the only changes are for safe modifications to an extension's static rule list for declarativeNetRequest, Chrome will approve the update in minutes. Coupled with the launch of version roll back last month, developers now have greater control over how their updates are deployed. Ecosystem progress After we addressed the top issues and feature gaps blocking migration last year, we saw an acceleration of extensions migrating successfully to Manifest V ## Scaling with Deeplinks on Android DevFeed: [Scaling with Deeplinks on Android]() Original publisher: [Read original article]() Author: Doximity Published: 2024-04-08T11:34:00Z Content type: tutorial Language: en Sources: [Doximity]() Topics: [Android](), [Kotlin](), [Code](), [Library]() Tags: [android](), [annotation-processor](), [build](), [code](), [complexity](), [deeplinks](), [dependencies](), [kotlin](), [library](), [manifest](), [mapping](), [module](), [pipeline](), [route]() ### AI overview This tutorial explains how to scale Android deeplink handling as definitions grow from a small set to dozens. It describes reducing router boilerplate with annotations and build-time code generation, and simplifying order-sensitive routing by mapping top-level paths to deeplink definitions. ### Source excerpt Deeplinking support in Android is relatively straightforward. You declare your deeplinks in the app's manifest, receive the incoming Intent passed in to your Activity and then navigate the user to the associated destination. This pipeline works just fine when you only need to support a handful of deeplinks. What happens though as the number of deeplinks grow? How do you deal with several dozen, or possibly even hundreds, of deeplinks? First Stab at Deeplinks When we first implemented deeplinking in our app, we only had to support 12 different deeplinks. We introduced a DeeplinkRouter class that would take the incoming Intent and determine where to navigate the user: interface Deeplink { fun route(uri: Uri): Boolean } class NotificationsDeeplink(val navigator: Navigator) : Deeplink { override fun route(uri: Uri): Boolean { return if (uri.path == "/notifications") { navigator.goToNotifications() true } else { false } } class ProfileDeeplink( val navigator: Navigator, val userRepository: UserRepository ) : Deeplink { override fun route(uri: Uri): Boolean { val profileId = uri.getQueryParameter("id") val isCurrentUser = userRepository.getCurrentUser().id == profileId return if (uri.path == "/profile" && profileId != null) { navigator.goToProfile(profileId, showColleagues = isCurrentUser) true } else { false } } } // ... more deeplink definitions ... class DeeplinkRouter( notificationsDeeplink: NotificationsDeeplink, profileDeeplink: ProfileDeeplink, // ... ) { private val deeplinks = listOf( notificationsDeeplink, profileDeeplink, // ... ) fun route(intent: Intent) { intent.data?.let { uri -> deeplinks.find { it.route(uri) } } } } Problems at Scale As the number of deeplinks and the complexity of their definitions grew, two big issues started to emerge. The first was managing the sheer number of deeplinks - we had nearly 50 at one point! Each of these had to be injected into DeeplinkRouter and then passed to its internal deeplinks list. We decided to resolve this by int ## Nuxt 3.8 DevFeed: [Nuxt 3.8]() Original publisher: [Read original article]() Published: 2023-10-19T00:00:00Z Content type: release Language: en Sources: [The Nuxt Blog]() Topics: [releases](), [Developer Tools]() Tags: [cli](), [manifest](), [node](), [performance](), [reactive](), [release](), [release-notes](), [testing](), [update](), [vue]() ### AI overview Nuxt 3.8 adds built-in DevTools, automatic Nuxt Image installation, an app manifest, composable caching and reactivity options, and layer-loading improvements. ### Source excerpt Nuxt 3.8 is out, bringing built-in DevTools, automatic Nuxt Image install, a new app manifest and much more. ## Building towards OCI v1.1 support in cosign DevFeed: [Building towards OCI v1.1 support in cosign]() Original publisher: [Read original article]() Published: 2023-02-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [releases](), [pull-requests](), [Maintainers]() Tags: [cosign](), [http](), [maintainers](), [manifest](), [oci](), [oci-registry](), [oci-v1-1](), [pull-requests](), [registry](), [releases](), [security](), [sha256](), [supply-chain]() ### AI overview The article discusses progress toward OCI v1.1 and its implications for cosign. It explains how OCI proposals and approved pull requests address relationships between objects in registries, and introduces the Referrers Tag Schema as a more interoperable alternative to cosign's existing tag-based approach. ### Source excerpt Learn about OCI, which is inching closer to a v1.1 release which provides official guidance on how to connect things in a registry. ## Developing User Interfaces for Custom Boards with ESP microcontrollers DevFeed: [Developing User Interfaces for Custom Boards with ESP microcontrollers]() Original publisher: [Read original article]() Author: John Lee Published: 2022-10-10T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [User Interfaces](), [Espressif](), [Microcontroller](), [configuration](), [GitHub](), [Code]() Tags: [blog](), [bsp](), [c](), [configuration](), [esp](), [espressif](), [github](), [i2c](), [lcd](), [lvgl](), [manifest](), [project](), [screen](), [spi](), [squareline](), [user-interfaces](), [waveshare]() ### AI overview This tutorial explains how to add a custom ESP-based board with a custom LCD to SquareLine Studio. It uses a WaveShare 7-inch display example and covers creating a board-support component, configuring display and touch communication, updating build and dependency files, and editing the board manifest. ### Source excerpt A few weeks ago in this article we have introduced SquareLine Studio and how it can be used to develop user interfaces. This feature was available only for Espressif's boards. But what if we wanted to use this tool for our custom designed board based on an ESP chip with a custom LCD? Here is the solution! What is the best way to add a custom board into SquareLine Studio? Start with the custom_waveshare_7inch example on from esp-bsp repository on GitHub. ## Interpreting voice results for Android media apps in cars DevFeed: [Interpreting voice results for Android media apps in cars]() Original publisher: [Read original article]() Author: Danny Preussler Published: 2022-01-10T21:33:42Z Content type: tutorial Language: en Sources: [Stories by Danny Preussler on Medium]() Topics: [Android](), [App](), [Code](), [Query (disambiguation)](), [Google]() Tags: [android](), [android-app-development](), [android-auto](), [androiddev](), [apps](), [audio](), [callback](), [car](), [code](), [google](), [google-assistant](), [integration](), [manifest](), [voice]() ### AI overview This article explains how Android Auto voice searches are delivered to a music app such as SoundCloud. It compares the documented use of MediaStore.EXTRA_MEDIA_FOCUS with observed behavior, reporting that Assistant currently returns a focus value that is not defined as an SDK constant. ### Source excerpt When working on the Android Auto integration for SoundCloud, I stumbled upon an interesting issue. When it comes to implementing voice actions, things you read in the documentation might differ a bit from reality. Voice commands are very critical while driving a car. You want the driver to keep looking at the street, keep his hands on the steering wheel, instead of interacting with any screen. This is why when building for Android Auto, Automotive OS, and Assistant Driving Mode you have to support basic voice searches. For a music app like ours, the idea is simple. A user can say something like: "Play Moderat on SoundCloud" Under the hood The Assistant will break down our sentence for interpretation: " " The verb (Play) and the app (SoundCloud) in the above command were meant for the system. It will then wake up the app mentioned (if it declared auto support via manifest) and, as we asked for verb "Play", the method MediaSessionCompat.Callback.onPlayFromSearch() will be called with the remaining query ("Moderat") as the argument. This query of "what to play" can still mean different things though. How do you know if Moderat is a band or a song? Don't worry, the Assistant will help us also here. It already got some idea what our query could mean, if we asked for an artist, an album, or a specific track. But be aware, it behaves slightly differently than officially documented. According to documentation we are supposed to write code like this: val mediaFocus = extras?.getString(MediaStore.EXTRA_MEDIA_FOCUS) if (mediaFocus == MediaStore.Audio.Artists.ENTRY_CONTENT_TYPE) { isArtistFocus = true artist = extras.getString(MediaStore.EXTRA_MEDIA_ARTIST) We are suppose to check for a bundle entry with the key MediaStore.EXTRA_MEDIA_FOCUS . This will give us a hint on how best to interpret the query. The value of the constant MediaStore.EXTRA_MEDIA_ARTIST checked above is vnd.android.cursor.item/artist and there are similar constants related to ## Setting Trace Flags and Configuring SQL Server in Kubernetes DevFeed: [Setting Trace Flags and Configuring SQL Server in Kubernetes]() Original publisher: [Read original article]() Author: Anthony Nocentino Published: 2021-09-12T12:24:45Z Content type: tutorial Language: en Sources: [Kubernetes on Anthony Nocentino's Blog]() Topics: [Kubernetes](), [sql-server](), [configuration](), [Deployment]() Tags: [blog](), [blog-post](), [code](), [configuration](), [containers](), [deployment](), [kubernetes](), [manifest](), [running](), [sql-server](), [sqlserver](), [trace]() ### AI overview A tutorial showing how to configure SQL Server in Kubernetes. It demonstrates overriding a container command to set a Database Engine Service Startup Option and using a ConfigMap to inject an mssql.conf configuration file. ### Source excerpt In this blog post, we will walk through a few examples of configuring SQL Server in Kubernetes. First, we will create a Deployment for SQL Server, override the container's command, and specify a Database Engine Service Startup Option. Second, we will create a Deployment for SQL Server using a ConfigMap to inject an mssql.conf configuration file. Creating a SQL Server Deployment and Overriding the Container's Command and Arguments First up, let's create a Deployment for SQL Server and override the container's command specify a Database Engine Service Startup Option. [Next page]()