nnichols / maven-version-bump-action

A simple GitHub Actions to bump the version of Maven projects

Hello, World!

👩‍💻 I'm currently working on: brewtility, common-beer-format, lein-sealog

🧠 I'm currently learning: Japanese Language, ChatOps

💬 Ask me about: Clojure, Clojurescript, GitHub Actions

😄 Pronouns: he/him/his

To see information on the library of the same name, please visit LIBRARY.MD instead

maven-version-bump-action's Issues

Didn't work for me

Tried using this didn't work for me didn't change pom file

Does not work for multi-module maven project

Bug Report

Describe the Bug

Does not work for multi-module maven project

Steps to Reproduce

Steps to reproduce the behavior:

1. Create an multi-module maven project
2. Execute this action for update the project version in github
3. See error, only the root pom is updated

Expected Behavior

Make it work for multi-module maven project by updating all related poms

User Information

• OS: Linux
• Browser Firefox
• Version 107.0

Possible Solution

maven-version-bump-action/version-bump.sh
modify
git add $POMPATH/pom.xml
to
git add pom.xml

working on older version of java as well as deleting older tags

Hello is it possible to make this work with older versions of java like java 6, also is their way to add functionality to delete older tags as well?

Incorrect Version: Parent Version is considered instead of artefact version

Incorrect Version

Description

My current artefact version is 1.0.1 whereas my spring-boot-starter-parent version is 2.4.2. The action is considering the current version of my artefact as 2.4.2 instead of 1.0.1

Expected Behavior

The action should consider the current version of my artefact as 1.0.1 instead of 2.4.2

Re-Write as a Babashka action

Feature Request

Problem Statement

This action has quickly accreted complexity from it's initial implementation, and is hard to test and verify in it's current state. To improve argument verification, iterability, and to test components of the application - I believe it is best to rewrite the action in Babashka.

Ideal Solution

Re-Write this action as a Babashka script

Alternative solutions

Implement bash tests or leverage awk/jq more

The `set-output` command is deprecated and will be removed soon

Bug Report

Describe the Bug

When using the maven-version-bump-action, you get a warning on the command line that says that set-output is deprecated and should be replaced with the new GITHUB_STATE environment files.

Steps to Reproduce

Steps to reproduce the behavior:

1. Use maven-version-bump-action@v4 as mentioned in the README
2. Run your GitHub Actions job
3. See warning inside the version bump section

Expected Behavior

A warning should not be seen

User Information

• OS: MacOS
• Browser FIrefox
• Version 109.0

Additional Context

The issue can be mitigated by following the example here. I can implement it if this project is still being maintained and someone could approve my merge request.