After the launch

Chrome Extension Maintenance: Updates, Policy Changes and the Permission Prompt That Switches Your Extension Off

When we checked on November 16, 2026, the code for DataCram's own extension was at version 0.1.1 and the Chrome Web Store listing still showed 0.1.0. That gap, between the version you wrote and the version your users run, is where extension maintenance happens.

November 17, 2026 · 10 min read

acmeroofingsupply.com · staff quote extension
A staff extension, before and after one update
The week an update asked for one more permission
Enabled installs, weekly-53%
Augupdate adds a permission with a warningNov
Illustrative: a sample install trend for a fictional roofing supplier's internal extension

The short answer

Maintaining a Chrome extension means testing it against browser and store policy changes, shipping each update through the same review as a new submission, and never adding a warning-triggering permission casually, because Chrome disables the extension until each user accepts it. DataCram maintains extensions it built and ones it inherits. Updates are quoted in writing before work starts, with no monthly price.

On this page
  1. The version you wrote and the version your users run
  2. What breaks an extension that nobody touched
  3. The permission increase that switches your extension off
  4. Our test run before any update reaches the store
  5. The publisher account is part of the extension
  6. What a maintenance quote covers, and what you can do alone
  7. Inheriting an extension from a developer who left

The version you wrote and the version your users run

An extension update is not a deploy. On a website, you push and the change is live. On the Chrome Web Store, Google's review process page says every submission, a new item or an update to an existing one, goes through the same review process. A one-line fix waits in the same line as a brand-new extension. The same page says "For most extensions, review is completed within a few days, but it can take up to a few weeks." That is Google's wording as of November 2026, and we promise nothing faster.

Approval does not publish the update by itself, either. Chrome's publishing guide says that once review is complete, "you will have up to 30 days to publish. After that period expires, the staged submission will revert to a draft which will have to be submitted again for review." Someone has to be watching the dashboard. In a small company, that someone is often nobody.

Our own extension is a fair example of the gap. GatorCrawl Keywords, DataCram's keyword research app, has a Chrome extension whose repository read 0.1.1 on November 16, 2026, while the store listing showed "Version 0.1.0", "Updated November 15, 2026". Nothing was wrong. Code and store simply move on different clocks, and maintenance means keeping track of both. The build itself is described in how we built the GatorCrawl extension.

What breaks an extension that nobody touched

Extensions rarely break because someone changed them. They break because the ground moved. Here are the forces we watch, with the dated examples their owners published.

The browser platform

Google's Manifest V2 timeline records that on August 31, 2026 all remaining Manifest V2 extensions were removed from the Chrome Web Store, and existing installs on Chrome 138 or earlier "can no longer receive updates or be reinstalled if removed." An extension nobody migrated simply stopped.

Store policy

Google announced on March 11, 2025 that extensions cannot inject affiliate links when no real value is provided, with enforcement beginning June 10th 2025. Policies change, and existing listings are expected to follow.

Periodic review

Google says "Existing items are also reviewed periodically for compliance." For minor violations found later, publishers "are typically given 7 to 30 days to address the issue(s)." Someone has to read that email and act.

The other browsers

Mozilla's data collection declaration became required for new AMO submissions from November 3, 2025. Microsoft's Edge timeline lists Manifest V2 warnings in Partner Center in August 2026 and enterprise deprecation "expected to begin" in early 2027.

The pages it reads

A content script reads and changes a web page through its structure. When that site redesigns, the script can stop finding what it looks for. No policy changed, and the extension still breaks.

Your own systems

A renamed field in your CRM or a new version of your web app's API can break the extension without touching its code. Fixes on the server side often ship without a store review at all.

That last card is a design argument, not a coincidence. When the logic lives on your server and the extension stays thin, more fixes happen where you deploy instantly. Chrome's store policy allows calls such as "Syncing user account data with a remote server" while requiring that all executable code ship in the package, so the thin-client design is the one the rules favor. Our Manifest V3 guide explains the remote code rule in full.

The permission increase that switches your extension off

Here is the trap that catches teams who treat an extension update like a website release. Chrome's permission warnings page says: "When a new permission that triggers a warning is added, the extension will be disabled until the user accepts the new permission." And: "The extension will be re-enabled only after the user agrees to accept the new permission." The store's update guide puts it from the user's side: they "will be prompted to accept them or disable the extension."

Picture the morning after. A sales team opens Chrome and the tool they use forty times a day is grayed out, with a prompt asking them to approve reading their browsing history. Some click accept. Some call IT. Some decide the extension has turned sinister and remove it. Nobody meant harm. Someone added the tabs permission to get a page title.

Glowing cyan line running flat across a deep blue and violet field with a thin data grid, broken by one sharp spike before it settles again
A permission increase can switch an extension off for everyone at once, and only each user's click turns it back on.

Before we ship an update that changes permissions at all, we test the prompt. Google's Extension Update Testing Tool, described on the same warnings page, lets a developer "Add a new permission with warning", "Increase the extension version number" and see exactly what users will see. Our permissions and privacy page covers which permissions warn and which do not.

Our test run before any update reaches the store

  1. 1

    Unit tests on the plain code

    Chrome's unit testing guide says code without extension APIs "can be tested as normal, using a framework such as Jest", with mocks for the rest.

  2. 2

    End-to-end tests on the built package

    The built extension loaded into a real browser and driven by Puppeteer or Playwright, the libraries Chrome's end-to-end guide names, headless where it can be.

  3. 3

    Reload the parts that need it

    Chrome's own table says manifest, service worker and content script changes need an extension reload, and content scripts need the host page reloaded too. We test from a clean reload every time.

  4. 4

    Check the permission prompt

    If the permission list changed, run the update testing tool and look at the warning a user will get.

  5. 5

    Ship to testers first

    Chrome lets you publish a "BETA" or "TESTING" version in parallel with production, so staff or friendly customers see the update before everyone.

  6. 6

    Roll out in stages when allowed

    Partial rollout is available to items with over 10,000 seven-day active users, as of November 2026. Below that, an update reaches every user together, so the earlier steps carry more weight.

One shortcut exists, for a narrow case. Chrome's skip review page says that for Declarative Net Request rule changes meeting its criteria, "Changes will usually go live within a few minutes." It applies to rule updates, not to code. Everything else waits for review.

The publisher account is part of the extension

Maintenance is also custody. Google states that "2-Step Verification is required for all developer accounts prior to publishing an extension or updating an existing extension," and its security guidance warns: "If developers' accounts are compromised, an attacker could push malicious code directly to all users," recommending two-factor authentication, "preferably with a security key."

That warning is not theoretical. In its own post dated December 27, 2024, which we read in an archived copy, Cyberhaven wrote that "a phishing attack compromised a Cyberhaven employee's access to the Google Chrome Web Store" and that the attacker published a malicious version of its extension. Cyberhaven reported removing the malicious package within 60 minutes of detecting it. The browser extension security page covers the rest of that story and what a build can do to limit the damage.

  • The developer account belongs to your company, on a shared company address, not a contractor's personal Gmail. Chrome's register page notes that after an account is created, you cannot change its email address.
  • Two-step verification is on, with a security key where possible.
  • If you ever pack the extension yourself, the .pem key is stored the way Google advises: "in a secret and secure place; it will be needed to update the extension."
  • Someone reads the store's emails. Google also notes that when malware is found, "notification is not sent to the publisher's email address," which is one more reason to check the dashboard, not only the inbox.

What a maintenance quote covers, and what you can do alone

We do not sell extension maintenance as a monthly plan with a published price. The work is lumpy: some months nothing changes, then a policy update or a browser release needs a day of careful work. Each round is quoted in writing before we start, so you see the number first. WordPress owners will recognize the idea from our plugin maintenance page.

Free, and yours to do

  • Keep the developer account in the company's name with two-step verification on
  • Read every store email the day it arrives
  • Publish approved updates within the 30-day window
  • Tell us when the site your extension reads gets redesigned

Quoted before we start

  • Code changes a browser release or store policy requires
  • Any update that touches the permission list
  • Ports to Firefox, Safari or Edge
  • New features, and changes to the APIs the extension calls
  • Taking over an extension someone else built, after we read it

Inheriting an extension from a developer who left

Bring us the extension, ours or someone else's. We read the manifest and the code, check the manifest version and the permission list, and find out who owns the developer account. If it is still on Manifest V2, the conversation is about a migration or a rebuild, not maintenance. If the account belongs to a former contractor, getting the listing into your company's hands comes before any code.

A rebuild is quoted like any new extension: from $1,500 to build, depending on complexity, with a fixed written estimate, store submission and privacy disclosures included. See custom Chrome extension development for the process, the extension pricing page for what moves the number, and cross-browser extensions if the inherited extension runs in more than one browser. Connections to your own systems go live the same day through API integrations. If the extension is one of several systems nobody owns anymore, a fractional CTO can sort the whole stack.

DataCram is a web studio in San Antonio, Texas, building for the web since 1999, working with businesses across the US by phone, video and a shared project page. Browse our work, read more in the custom browser extensions section, or call (210) 346-0848.

Questions owners ask about custom browser extensions

Yes. Google says all submissions, new items and updates alike, go through the same review process. For most extensions review finishes within a few days but can take up to a few weeks, per Google as of November 2026. A narrow exception lets some Declarative Net Request rule changes go live without review.

Most likely the update added a permission that triggers a warning. Chrome's documentation says the extension is disabled until each user accepts the new permission. Requesting the permission as optional, at run time, avoids this, because Chrome does not disable an extension whose upgrade adds only optional permissions.

We quote it per piece of work rather than as a monthly plan, because the work comes in bursts tied to browser releases, policy changes and your own systems. You see a written number before we start. Rebuilds are quoted like new extensions, from $1,500, depending on complexity.

Google's timeline says all remaining Manifest V2 extensions were removed from the Chrome Web Store on August 31, 2026. Existing installs on Chrome 138 or earlier keep running, but they cannot receive updates or be reinstalled if removed. The fix is a Manifest V3 migration or a rebuild.

Chrome lets you publish a BETA or TESTING version in parallel with production, so a small group gets it first. Partial rollout is available to items with over 10,000 seven-day active users, as of November 2026. Before either, we run unit tests, end-to-end tests on the built package and, for permission changes, Google's update testing tool.

Usually. We read the code and the manifest, check the permissions and the manifest version, and confirm who controls the developer account before quoting. If the account sits with a former contractor, moving it to your company comes first.

Keep reading

Free · No obligation

Get your extension's next update checked

Tell us what the extension does, who built it and what changed. Someone at DataCram replies with what we would test, what we expect to find and a written quote.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote