Skip to content

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

@picksitquick

Description

@picksitquick

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,

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions