From where are coming 1.0.4 and 2.0.beta-1
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 84
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
Interesting work, thanks! However, this repository states about the latest version being 1.0.1, while in [the mvnrepository, there are 2 new versions](https://mvnrepository.com/artifact/com.linkedin.migz/migz): `1.0.4` and `2.0.beta-1`.
I'm wondering if you forgot to create the tag in github ? I would more trust the mvnrepository's version if there is the corresponding tag in github, so it would be awesome if you push the latest tags (and even release the 2.0 😄 )
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by checking the repository's existing tags, version metadata, and release instructions, then compare them with the 1.0.4 and 2.0.beta-1 artifacts on Maven Repository; done means the intended tags and release state are present on GitHub, or the discrepancy is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, java
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100