PHPackages                             daltcore/release-tools - 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. daltcore/release-tools

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

daltcore/release-tools
======================

Release Tools for projects

0.1.10(8y ago)0361MITPHP

Since Aug 15Pushed 8y agoCompare

[ Source](https://github.com/DALTCORE/ReleaseTools)[ Packagist](https://packagist.org/packages/daltcore/release-tools)[ RSS](/packages/daltcore-release-tools/feed)WikiDiscussions master Synced 4w ago

READMEChangelog (10)Dependencies (10)Versions (19)Used By (0)

Release tools for Projects
--------------------------

[](#release-tools-for-projects)

[![FOSSA Status](https://camo.githubusercontent.com/de6aea0eb09922c50c32e7c0d30c85d35a9ed6840ebc806c4f44169a2bbca181/68747470733a2f2f6170702e666f7373612e696f2f6170692f70726f6a656374732f6769742532426769746875622e636f6d25324644414c54434f524525324652656c65617365546f6f6c732e7376673f747970653d736869656c64)](https://app.fossa.io/projects/git%2Bgithub.com%2FDALTCORE%2FReleaseTools?ref=badge_shield)

### Installation

[](#installation)

Via composer:

```
composer global require daltcore/release-tools
```

or
Via executable: [Go to releases](https://github.com/DALTCORE/ReleaseTools/releases/latest) and add this executable to your $PATH environment.

Initialize ReleaseTools on current running repo. Creates .release-tools directory and .release-tool file.

```
release-tool init
```

Check if ReleaseTools is ready for use

```
release-tool status
```

*If you want to know more about thestructure behind ReleaseTools
then you can use the `-v` flag behind every command to see the
verbose info*

\_If a error occurs then you can add the `-vvv` parameter to the tool. A stack-trace will be shown.

### Usage

[](#usage)

#### Development

[](#development)

In development you should make a new branch for all your features/changes.
Release tools makes use of the current branch name for file naming for the changelog files.

Adding a new changelog file to the repo, this command is interactive.
*For testing you can use `--dry-run` as parameter*

```
release-tool changelog
```

Implement git hook to force you to make a changelog entry

```
release-tool hooks:made-changelog
```

#### Releasing

[](#releasing)

In development you want to run the prepare command which will create a issue in the repo that is specified in the .release-tools file
*For testing you can use `--dry-run` as parameter*

```
release-tool release:prepare
```

Building changelog file
*For testing you can use `--dry-run` as parameter*

```
release-tool build:changelog
```

List all pending changelogs

```
release-tool list:changelog
```

```
+-------------------+------------+---------------+--------------+
| Title             | Author     | Merge Request | Type         |
+-------------------+------------+---------------+--------------+
| this is a test MR | Ramon Smit | 1             | Security fix |
+-------------------+------------+---------------+--------------+

```

#### Building a stub:

[](#building-a-stub)

If you need to create a custom stub for `release-tool prepare` you can
create a file called `prepare.stub` in the directory `.release-tools/stubs`

These files are markdown files and the following variables are available:

- :version This represents the version you fill when askes
- :reop This represents the `repo` variable from the `.release-tool` file

This wil override as the issue template pushed to GitLab when releasing.

Example:

```
**Release `:repo` version `:version`**

*Pre flight checks*
* [ ] - Notify in `5_Releases`
* [ ] - A
* [ ] - B
  * [ ] - C
```

#### Building playbooks:

[](#building-playbooks)

If you need to create a custom playbook for `release-tool playbook ` you can
create a file called `.rtp` in the directory `.release-tools/playbooks`

These files are yaml files and the following variables are available:

- :version This represents the version you fill when askes
- :reop This represents the `repo` variable from the `.release-tool` file

Example:

```
playbook:
  gitlab:
    make_branch:
      from: develop
      to: releases/:version

    tag:
      from: releases/:version
      version: v:version

    merge_request:
      branches: releases/:version > master

    merge_request:
      branches: master > develop

  mattermost:
    notify:
      channel: 'releases'
      message: '@channel We''re about to release version :version of the project :repo. Please stop merging now into develop until next announcement'
```

The example contains all available methods for playbooks.

#### .release-tools file example

[](#release-tools-file-example)

```
repo: group/repo
api_url: https://gitlab.com
api_key: AbC123DeF456Ghi789
mattermost_webhook: https://mattermost.server.com/hooks/hook-uri
```

License
-------

[](#license)

[![FOSSA Status](https://camo.githubusercontent.com/a8013722fe29c8376588f48b895cbadbbbc346ad6ec037a019cea5915980f874/68747470733a2f2f6170702e666f7373612e696f2f6170692f70726f6a656374732f6769742532426769746875622e636f6d25324644414c54434f524525324652656c65617365546f6f6c732e7376673f747970653d6c61726765)](https://app.fossa.io/projects/git%2Bgithub.com%2FDALTCORE%2FReleaseTools?ref=badge_large)

###  Health Score

27

—

LowBetter than 47% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity8

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity62

Established project with proven stability

 Bus Factor1

Top contributor holds 97.8% 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

Recently: every ~7 days

Total

18

Last Release

3203d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/1906631?v=4)[Monn](/maintainers/RamonSmit)[@RamonSmit](https://github.com/RamonSmit)

---

Top Contributors

[![RamonSmit](https://avatars.githubusercontent.com/u/1906631?v=4)](https://github.com/RamonSmit "RamonSmit (45 commits)")[![fossabot](https://avatars.githubusercontent.com/u/29791463?v=4)](https://github.com/fossabot "fossabot (1 commits)")

---

Tags

daltcorepharreleasetools

### Embed Badge

![Health badge](/badges/daltcore-release-tools/health.svg)

```
[![Health](https://phpackages.com/badges/daltcore-release-tools/health.svg)](https://phpackages.com/packages/daltcore-release-tools)
```

###  Alternatives

[drupal/core-recommended

Locked core dependencies; require this project INSTEAD OF drupal/core.

6941.5M398](/packages/drupal-core-recommended)[drupal/core

Drupal is an open source content management platform powering millions of websites and applications.

19664.8M1.6k](/packages/drupal-core)[sulu/sulu

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

1.3k1.4M196](/packages/sulu-sulu)[friendsoftypo3/content-blocks

TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML

101466.4k45](/packages/friendsoftypo3-content-blocks)[open-dxp/opendxp

Content & Product Management Framework (CMS/PIM)

9417.2k58](/packages/open-dxp-opendxp)[tempest/framework

The PHP framework that gets out of your way.

2.2k31.1k12](/packages/tempest-framework)

PHPackages © 2026

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