PHPackages                             gajdaw/stamp - 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. gajdaw/stamp

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

gajdaw/stamp
============

Versioning tool to bump version.

v0.2.0(11y ago)0191[40 issues](https://github.com/gajdaw/stamp/issues)MITPHPPHP >=5.3.3

Since Jan 14Pushed 10y ago1 watchersCompare

[ Source](https://github.com/gajdaw/stamp)[ Packagist](https://packagist.org/packages/gajdaw/stamp)[ Docs](http://github.com/gajdaw/stamp)[ RSS](/packages/gajdaw-stamp/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (4)Dependencies (9)Versions (16)Used By (0)

STAMP
=====

[](#stamp)

[![Build Status](https://camo.githubusercontent.com/b62b3b718ac03f8b2dda5c3dc668ea7d28b81c71af41e4f2ac7e4c1cf085c564/68747470733a2f2f7472617669732d63692e6f72672f7374616d702d6170706c69636174696f6e2f7374616d702e7376673f6272616e63683d6d6173746572)](https://travis-ci.org/stamp-application/stamp)

Application that makes versioning a little easier.

1. Example
----------

[](#1-example)

Suppose your application contains a file name `metadata.json` with the following contents:

```
{
  "name": "gajdaw-php_phars",
  "version": "0.1.4",
  "author": "gajdaw"
}

```

To release a new version you would probably:

- increase the version in `metadata.json` from `0.1.4` to `0.1.5`
- commit the change setting the commit's message to `Version 0.1.5`
- create an annotated tag `v0.1.5` with message `Release 0.1.5`

To perform the above operations with `stamp` application start with the configuration file named `stamp.yml`(in your project's root directory):

```
filename:    'metadata.json'
regex:       '/"version": "(?P[\d\.]+)",/'
replacement: '"version": "{{ version }}",'

```

The `filename` parameter sets the file to be searched for version.

The `regex` parameter sets the regular expression used to parse the file for version number. Please note that `?P`sets the name of the variable to `version`.

The `replacement` parameter is a Twig template for the string that represents the new version. This string will be stored in the file defined by `filename`.

2. How to install?
------------------

[](#2-how-to-install)

### 2.1. Manual download

[](#21-manual-download)

Download the latest release available at:

```
https://github.com/gajdaw/stamp/releases/download/v0.2.0/stamp.phar

```

You can do this with:

```
wget -O stamp.phar http://github.com/gajdaw/stamp/releases/download/v0.2.0/stamp.phar

```

2. Running `stamp`
------------------

[](#2-running-stamp)

Since `stamp` is not yet stable, I suggest using `--dry-run` and `--verbose` options for start.

Here is the list of available commands:

```
$ stamp patch:up --dry-run --verbose
$ stamp minor:up --dry-run --verbose
$ stamp major:up --dry-run --verbose

```

The command `patch:up` performs the following transformation:

```
1.2.3        =>  1.2.4
77.234.654   =>  77.234.655

```

The command `minor:up` increases the number in the middle and sets the patch number to 0:

```
1.2.3        =>  1.3.0
77.234.654   =>  77.235.0

```

The last command, `major:up` increases the first number and sets the other numbers to 0:

```
1.2.3        =>  2.0.0
77.234.654   =>  78.0.0

```

3. Reading list
---------------

[](#3-reading-list)

-
-
-
-
-
-
-

4. How to run the tests?
------------------------

[](#4-how-to-run-the-tests)

```
$ vagrant up
$ composer update
$ bin/phpspec run
$ bin/behat

```

5. How to build dev version?
----------------------------

[](#5-how-to-build-dev-version)

```
git checkout master
git checkout -b build
vagrant ssh
bin/stamp version:dev
./build.bash

git checkout master
git branch -D build

```

6. Credits
----------

[](#6-credits)

Many concepts in this application, especially when it comes to testing, came from:

Great many thanks to [all contributors](https://github.com/phpspec/phpspec/graphs/contributors)!

I used some of the files, like for example matchers in `features/bootstrap/Matcher/` folder, directly (i.e. without any modifications).

In case of other fragments (e.g. `parseConfigurationFile`method in `Stamp\Console\Application`) I changed the code that I found in phpspec.

###  Health Score

25

—

LowBetter than 37% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity7

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity56

Maturing project, gaining track record

 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 ~2 days

Total

15

Last Release

4112d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/fcf1a8b22370cbccb65ec4f26adf304b4c63455d3edd5cef99891b480d7dbcd3?d=identicon)[gajdaw](/maintainers/gajdaw)

---

Top Contributors

[![gajdaw](https://avatars.githubusercontent.com/u/676675?v=4)](https://github.com/gajdaw "gajdaw (150 commits)")

---

Tags

gittagversioncommitvcsbump

###  Code Quality

TestsBehat

### Embed Badge

![Health badge](/badges/gajdaw-stamp/health.svg)

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

###  Alternatives

[sylius/sylius

E-Commerce platform for PHP, based on Symfony framework.

8.4k5.6M651](/packages/sylius-sylius)[shopware/platform

The Shopware e-commerce core

3.3k1.5M3](/packages/shopware-platform)[sulu/sulu

Core framework that implements the functionality of the Sulu content management system

1.3k1.3M152](/packages/sulu-sulu)[prestashop/prestashop

PrestaShop is an Open Source e-commerce platform, committed to providing the best shopping cart experience for both merchants and customers.

9.0k15.4k](/packages/prestashop-prestashop)[symplify/monorepo-builder

Not only Composer tools to build a Monorepo.

5205.3M82](/packages/symplify-monorepo-builder)[contao/core-bundle

Contao Open Source CMS

1231.6M2.4k](/packages/contao-core-bundle)

PHPackages © 2026

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