การจัดการเวอร์ชัน การอัปเดต และการบำรุงรักษาหลังเปิดตัว

Getting accepted to the store is just the start. Real success comes from steady updates, responsive support, and staying compliant as policies evolve.

The manifest version must increase with every update. A common scheme is MAJOR.MINOR.PATCH to communicate the size of a change.

Stores reject an upload whose version is not higher than the published one. Bump it before every submission, even for tiny fixes.

Once you publish a new version, browsers fetch and install it automatically within hours. Users do not need to do anything.

This makes a broken release dangerous, so test thoroughly.

Both stores let you release to a percentage of users first. Roll out to a small slice, watch for crash reports, then expand.

Use the onInstalled event to run migrations or show a what's-new page when the version changes.

When your data shape changes between versions, migrate old stored values on update so existing users do not break.

Keep a public changelog and update the store listing notes each release. Users trust extensions that communicate clearly about changes.

Reply to store reviews, especially negative ones. A thoughtful reply and a follow-up fix can turn a one-star reviewer into a loyal user.

Store policies change. Periodically re-read the developer policies, tighten permissions, and update your privacy disclosures to avoid sudden removal.

Browser APIs get deprecated over time. Watch developer announcements and migrate before removed APIs break your extension for everyone.

You learned post-launch maintenance:

• Bump the manifest version every release
• Use staged rollouts and test before publishing
• Run migrations in onInstalled
• Keep a changelog and reply to reviews
• Stay compliant and ahead of deprecations

Consistent maintenance keeps your extension healthy long after launch.