Is there a generic authoring tool in Perl to assist with release tasks like Minilla?

I would like a utility to assist me in developing and releasing applications and libraries.I don't know anything other than authoring tools limited to Perl, but I prefer the most generic one.

What is the authoring tool in this question? I think it helps me run git tag&git push every time I release it, and enter the version name and ChangeLog (although it may change depending on the answer, I am thinking about it now).

To put it bluntly, the image is similar to that of Perl's Minilla, which is not limited to Perl.

Minilla Reference: http://blog.64p.org/entry/2013/05/14/080423

What are some relatively versatile authoring tools that are independent of a particular development environment?

I will explain the detailed request later, but if there is one that fits well, I am thinking of changing trains. If it doesn't fit perfectly, I'm thinking about developing it myself.

We also welcome references that do not meet the following requirements, such as specific languages, specific frameworks, and authoring tools in specific environments!

It is desirable to be a collection of utilities that facilitate release preparation, not limited to the development of a specific development language framework.(To put it bluntly, I want to use a small library collection instead of a full stack framework)

Perl has Minilla, and as mentioned above, we are looking for a "generic extraction of this Minilla that is not limited to Perl."

In order to think about what you want, I have drafted the tools that you want below.Currently, only documents are not implemented.

https://github.com/ichigotake/App-Release

Read the execution image using the project command below as the image you want.

Interactive UI to Enter Version Name

## running image.When the input of the next version is confirmed, the input is ejected to the standard output.
$ project version
Next Release ?[1.0.1]: (Enter the next version here)

For example, suppose you have a project that manages version names in a text file called app/VERSION with only version names, such as "1.0.0".

I would appreciate it if you could easily use the next version of the project in the form of $project version>app/VERSION.

Managing ChangeLog

## running image.When you run changes, the editor to edit the change log appears.
### Automatically commits when editing is complete.

$ project changes

If you are managing ChangeLog with a file called Changes, edit the ChangeLog using $EDITOR.

By allowing these editing UIs to be invoked in scripts, it is easier to create flows such as entering ChangeLog and visualizing final confirmation while running release scripts.

A file name can be arbitrarily changed by a configuration file or the like.

Below is the commit image right after editing: Here.

git tag to git push

If you pass the version name x.y.z as an argument, it will do git tag x.y.x.x&git push origin x.y.z&git push origin-umaster.

High portability

It would be great if there was portability like Gradle Wrapper that would not require you to install a separate development tool immediately after doing gitclone.

The above mentioned App-Release uses Perl's App::FatPacker module to consolidate the dependent libraries into a single script, and expects the executable to be distributed independently of the external library.

I am writing an App-Release that I have created as an image of what I want, but I would like to take advantage of or refer to any general authoring tools or alternatives that meet the above requirements, goals or policies.

And I don't really know what authoring tools are in the world, so I'd like to use this question as an opportunity to learn about them.