PHPackages                             duzun/verup - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. duzun/verup

ActiveLibrary[Utility & Helpers](/categories/utility)

duzun/verup
===========

Increment and update version in all project files

v1.2.0(1y ago)15MITPHP

Since Nov 3Pushed 1y ago1 watchersCompare

[ Source](https://github.com/duzun/verup.php)[ Packagist](https://packagist.org/packages/duzun/verup)[ RSS](/packages/duzun-verup/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (1)Versions (3)Used By (0)

verup.php [![Latest Stable Version](https://camo.githubusercontent.com/2a58be27e4296ee8141d99093741ee8d3c75a31263d7ed024ca00836fc3e092d/68747470733a2f2f706f7365722e707567782e6f72672f64757a756e2f76657275702f762f737461626c65)](https://packagist.org/packages/duzun/verup)
============================================================================================================================================================================================================================================================================

[](#verupphp-)

Increment and update version in all project files according to semver.

> Note: This is a port to PHP of [verup.js](https://github.com/duzun/verup).

**v1.2.0**

Installation
------------

[](#installation)

```
composer require duzun/verup --dev
```

Usage
-----

[](#usage)

### Basic Examples

[](#basic-examples)

```
# Increment revision (patch) version by 1 (1.2.3 -> 1.2.4)
composer exec verup 1

# Increment minor version by 1 (1.2.3 -> 1.3.0)
composer exec verup 1.0

# Increment major version by 1 (1.2.3 -> 2.0.0)
composer exec verup 1.0.0
```

### Options

[](#options)

```
-n, --name       Package name to bump (finds package in parent directories)
-p, --package  Package file to use (default: composer.json)
                     Supported: composer.json, package.json
-h, --help          Show help message

```

### Examples with Options

[](#examples-with-options)

If you have subprojects, and want to avoid confusion as of which project to patch, use `-n ` option:

```
# Update version in a specific package (search in parent folders)
composer exec verup -n my/pkg 1.0
```

This will look for `package.json` with `name == 'my/pkg'` in all parent folders, until it finds the right level, and patch the files at that level.

You can also use `-p ` option to specify a different package file:

```
# Use package.json instead of composer.json
composer exec verup -p package.json 1
```

In your composer.json (or package.json)
---------------------------------------

[](#in-your-composerjson-or-packagejson)

The minimum setup for your project is to add the list of file names that contain version string to `composer.json` at `extra.verup.files`. Here is a sample:

```
...
"extra": {
  "verup": {
    "files": [
      "manifest.json",
      "index.js",
      "README.MD" ...
    ]
  }
}
...
```

If the file is a `.json`, version is expected to be at key `extra.verup.version` or `version`.

You can define you own list of regular expressions in `package.json` at `extra.verup.regs`:

```
...
"extra": {
  "verup": {
    "regs": [
      "((?:\\$|(?:\\s*\\*?\\s*@)|(?:^\\s*(?:var|,)?\\s+))ver(?:sion)?[\\s\\:='\"]+)([0-9]+(?:\\.[0-9]+){2,2})",
      "^(\\s*\\$(?:_)?version[\\s='\"]+)([0-9]+(?:\\.[0-9]+){2,2})",
      "^(\\s?\\*.*v)([0-9]+(?:\\.[0-9]+){2,2})"
    ]
  }
}
...
```

### Configuration Options

[](#configuration-options)

- `version`: Current version of your package
- `files`: List of files to update when version changes
- `regs`: List of regular expressions to match version strings in files

###  Health Score

33

—

LowBetter than 75% of packages

Maintenance46

Moderate activity, may be stable

Popularity5

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity64

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~3439 days

Total

2

Last Release

406d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/5300c81d91f72d21119a70370ddf7810d64c38c81b677390eb2d63afe90e255d?d=identicon)[duzun](/maintainers/duzun)

---

Top Contributors

[![duzun](https://avatars.githubusercontent.com/u/321424?v=4)](https://github.com/duzun "duzun (7 commits)")

###  Code Quality

TestsPest

### Embed Badge

![Health badge](/badges/duzun-verup/health.svg)

```
[![Health](https://phpackages.com/badges/duzun-verup/health.svg)](https://phpackages.com/packages/duzun-verup)
```

###  Alternatives

[dotmarn/laravel-error-views

A set of customised error pages/screens designed using the TailwindCSS for use in Laravel projects.

123.2k](/packages/dotmarn-laravel-error-views)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)