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

Updating Maven package version triggered with merge of a PR. #46

Open
picksitquick opened this issue Mar 30, 2024 · 0 comments · May be fixed by #47
Open

Updating Maven package version triggered with merge of a PR. #46

picksitquick opened this issue Mar 30, 2024 · 0 comments · May be fixed by #47
Labels
bug Something isn't working

Comments

@picksitquick
Copy link
Contributor

Describe the bug
Currently whenever we raise a PR and merge the code with the main branch the version number of the release and maven package does not get updated.

To Reproduce
You can check Github Actions and notice that on every merge the version Id in pom is similar in most of the cases.

Expected behavior
What we want is that whenever the code is merged and deployed, the release version should match with the version of Maven package, that is, version Id within pom.

The reason for this approach is that later when we want to debug or roll back any version it will be much easier for us to manage maven packages and release versions.

Additional context
Feel free to drop any queries related to the task,

@picksitquick picksitquick added the bug Something isn't working label Mar 30, 2024
@pratik2050 pratik2050 linked a pull request Jun 23, 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
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant