Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Artifact Version Must Be Manually Changed in action.yml when Releasing a New Project Version #315

Open
gcw-it opened this issue Sep 1, 2024 · 0 comments · May be fixed by #316
Open

Artifact Version Must Be Manually Changed in action.yml when Releasing a New Project Version #315

gcw-it opened this issue Sep 1, 2024 · 0 comments · May be fixed by #316

Comments

@gcw-it
Copy link
Contributor

gcw-it commented Sep 1, 2024

While experimenting with the extension I found it quite error prone, to have to manually change the artifact-version for the jbang run command in the action.yml file, when releasing a new project version.

Right now the version in the action.yml is set once, when the project is created via the codestart. Any subsequent changes to the project version won't affect the version in the action.yml.

If desired, I can create a PR adjusting the codestart template for the action.yml, to read the artifact-version from the suitable pom.xml, when running the action.

@gcw-it gcw-it linked a pull request Sep 2, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant