skills.rest
DemchaAV
DemchaAVCOMMUNITY
Explore all skills by this author →
Website𝕏@DemchaAVGitHub

app-version-bump

Bump manifest.json version to refresh PWA and service worker caches.

Updated Aug 27, 2026
Search Tags:#automation#versioning#manifest#pwa#service-worker#build-pipeline#release-process
One-click install
npx skills add https://github.com/DemchaAV/Cockatails-list --skill app-version-bump
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-version-bump
Source: https://github.com/DemchaAV/Cockatails-list/tree/main/.agent/skills/app-version-bump
Command: npx skills add https://github.com/DemchaAV/Cockatails-list --skill app-version-bump

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Bump the Cockatails-list application version after meaningful changes so the PWA and service worker fetch new data and assets. Use this skill whenever files are changed in the app pipeline, including database-like data files, category files, HTML, CSS, JS, manifest, or service worker related changes.

Core Features & Use Cases

  • Automatically bump manifest.json.version after meaningful changes to ensure users receive fresh data.
  • Trigger cache refresh of service worker and PWA by updating the version string following the project's versioning rules.
  • Applied when data, category files, HTML, CSS, JS, or pipeline configurations are modified to keep the deployment in sync.

Quick Start

Run the bump_app_version.py script to advance manifest.json version after changes.

Frequently Asked Questions about app-version-bump

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I force a PWA service worker to refresh cached data after app changes?▼

To force a PWA service worker to refresh cached data, bump the manifest.json version string. Updating this version after modifying HTML, CSS, JS, or data files triggers the service worker to fetch fresh assets for users.

Why does my service worker keep serving stale assets after a build pipeline update?▼

Your service worker serves stale assets because the manifest.json version was not bumped. You must advance the version string after updating pipeline configurations or application files to invalidate old caches and sync deployments.

What is the best way to automate manifest version bumping in a release process?▼

To automate manifest version bumping in a release process, run a dedicated versioning script. This automatically advances the manifest.json version according to predefined daily versioning rules whenever meaningful app changes occur.

When do I need to update the manifest version for my progressive web app?▼

You need to update the manifest version whenever meaningful changes occur in your progressive web app. This includes modifications to database-like data files, category files, HTML, CSS, JS, or service worker configurations to ensure users get fresh assets.

Does bumping the manifest version work for both data and UI asset updates?▼

Yes, bumping the manifest version works for both data and UI asset updates. Advancing the manifest.json version string triggers cache refresh for service worker and PWA updates across data, category files, HTML, CSS, and JS modifications.

Related Skills

Explore More Software Engineering Skills→
jls42jls42
1

PWA Service Worker Manager

Manage Service Worker versioning, caching strategies, and offline testing for PWAs.

Community
Intermediate
baxriddin0317baxriddin0317

pwa-patterns

Configure next-pwa service workers with runtime caching and offline fallbacks for Next.js projects.

Community
Advanced
terrylicaterrylica

data-pipeline-monitoring

Monitor Cloud Platform dual-pipeline health, logs, and alerts via scripts.

Community
Advanced
SlaiaaSlaiaa

pwa-troubleshooting

Diagnose PWA service worker, caching, offline, storage, and install issues.

Official
Intermediate