janderssonse/changelog-tag

An opinionated util for generating a Changelog from Conventional commits, bumping semver and so on.

Doing stuff, breaking things

I'm a developer with a passion for Open Source. In recent years I have shifted gears slightly (still developing though) and helped organisations improve Open Source Processes, in a practical agile way. My focus and ❤️ is slightly to the tech side, as opposed to the enterprise overview side, as I like to get my hands dirty.

Having been involved in the Open Source communities, since the early days when one traded Fred Fish floppydisks with Source Code on them (having exotic licenses as "send me a postcard", It has been such an interesting, incredible journey to see the ideas of sharing solutions - a.k.a Open Source - mature on all levels, from being an academia and hobbyist interest, to grow, mature and become an essential part of our Global Infrastructure.

🌱 I have a soft ❤️ for translations/languages, developer tooling, Open Source practices and licensing and retro computing.

🕰️ Well, I'm always eager to get together and hack, or discuss solving problems and how to improve Open Source or agility.

Have fun, happy hacking!

Socials

Badges

My GitHub Stats

changelog-tag's Issues

Release workflow: Add an automatic (GH) release option

What benefits does the suggestion solve?

Makes a packaged release. Nice to have rather than a must, but still makes the project more professional.

Feature suggestion description

Should use the API release feature to also package a nice release. It could be done with a workflow, or better with internal app support so that we can use this project in a ci pipe regardless of github/gitlab etc.

Alternative solutions

Using CI workflows vs API call from the app itself.

Additional information

No response

Should parse npm version with library instead of pulling in full npm/node

What benefits does the suggestion solve?

We should not demand that npm is installed as a dependency, it will make the app more lightweight and maintainable.

Feature suggestion description

For a more lightweight take, we should be able to just parse the package version with a npm lib, example https://github.com/aquasecurity/go-npm-version or alike. Port the mainflow to go first?

Alternative solutions

No response

Additional information

No response

Port the project to Golang or other fitting solution

What benefits does the suggestion solve?

Improves maintenance, stability etc.

Feature suggestion description

Currently, changelog_release is a bash script. It works, and the code is structured ,fairly tested... but It is starting to reach the point where it most likely makes more sense to rewrite it a go binary, or possible a java picocli app, native graalvm generation.

Also, it would certainly make it more appealing to recieve external bugfixes, as bash is not at the highest top of the hipster chain:)

Alternative solutions

No response

Additional information

No response

Should parse maven project with parse library instead of dependency on full mvn

What benefits does the suggestion solve?

Make the project lightweight and loose the dependency to jvm, maven.

Feature suggestion description

Use a lightweight parser lib for mvn projects, for example https://github.com/vifraa/gopom. Needs port to golang first (preferable at least)

Alternative solutions

No response

Additional information

No response

Snap: Only works in --devmode (does not connect to ssh-agent)

What happened?

The Snap package only works when installed in --devmode. Due to https://forum.snapcraft.io/t/examples-of-snap-running-ssh-agent/36044

Steps To Reproduce

Install it with with --devmode vs regular mode

What did you expect?

It should work with ssh-add in non devmode also

Version

No response

Optional Screenshots

No response

Relevant log output

No response

README: clearify run examples

What happened?

In the README, clearify that script, snap and docker run are different ways to run it, so that user is not confused and try to run them all.

Steps To Reproduce

See the README

What did you expect?

Alternative 1: Run bla..
Alternative 2: Run bla..

Version

No response

Optional Screenshots

No response

Relevant log output

No response

If git-chglog tag is installed by asdf but not pinned, the script runs happily but does not generate a changelog

What happened?

As title

Steps To Reproduce

have git-chglog installed but not pinned, script runs, no changelog

What did you expect?

A warning that the call to git-chglog failed, and that the run fails.

Version

No response

Optional Screenshots

No response

Relevant log output

No response

README image examples is outdated

What happened?

The image examples are outdated, showing changelog_release instaed of changelog_tag.sh.

Steps To Reproduce

Look at the image examples in the README

What did you expect?

The images should show current names

Version

No response

Optional Screenshots

No response

Relevant log output

No response