janderssonse/janderscripts

Intented to collect personal scripts and misc. snippets over time. If some one else finds any use for these, great.

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

janderscripts's Issues

Changelog_Release: Replace npm update of package with simpler solutin

Is your feature request related to a problem? Please describe.
Currently we pull in npm etc just to update the version. This is overkill.

Describe the solution you'd like
Replace with a simpler lightweight solution

Also commit package-lock.json

Currently, the package-lock.json file is not add upon release commit (only package-lock) for npm-based projects. Add that!

Rewrite Changelog_Release in (suggestions) go, or java with picocli, native gen

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 recivie external bugfixes, as bash is not at the highest top of the hipster chain:)

Changelog_Release: Add a Dockerfile

Is your feature request related to a problem? Please describe.
To make it easier to use, complete the wip Dockerfile.

Describe the solution you'd like
Changelog_Release runnable in a container, based on Wolfi OS.

Don't enforce gpg-signing with ssh-format, let gpg be okay.

We currently check that the user has enbled ssh-signing, however gpg should be ok.

Defaulting semver should be patch

After consulting with the maintainer, we propose to alter what version this script defaults to when creating a new tag. We suggest replacing the current default value which increases the minor version with an increase to the patch version instead eg 0.0.0 to 0.1.0 will instead become 0.0.0 to 0.0.1.
Fixing this would lead to a more expected behavior according to us, for more info about semver, see semver 2.0.0

Changelog_Release: Replace mvn versions:set with non mvn dependent solution

Is your feature request related to a problem? Please describe.
Currently, we pull in mvn/java just to be able to update the pom.xml with mvn versions:set. This is overkill.

Describe the solution you'd like
A simple version update in any way without using the mvn plugin. Even SED would make more sense.

Extract Changelog_Release to it's own project.

The Changelog Release script has proven useful enough to extraxt to it's own project. It would also make easier and less confusing for this script repository, as it should not grow to much. There are a few changes that would make sense for that separation (packaging version handling etc) and finally, a go-port could be started in a branch of that while maitaining the original script.

Extract changelog_release to a DEB-package (or snap)

Build an installable package from changelog_release so installation for users becomes easier.