Version mismatch between ros gbp data and tags in source code

[kunaltyagi]

Steps to reproduce and error output

$ rosinstall_generator perception --rosdistro noetic --deps --upstream  > perception.rosinstall
$ vcs import --input perception.rosinstall ./src/
=== ./src/noetic/gennodejs (git) ===
Could not checkout ref '2.0.2': fatal: invalid reference: 2.0.2

Solution:

• Add the 2.0.2 tag at the correct commit
• Release a new version for noetic with the correct tag

[chris-smith]

@sloretz any suggestions on what to do here?

@IanTheEngineer and I had talked about doing an actual release at some point. I'm not sure what came up but we could prioritize doing so if that makes the most sense here.

[kunaltyagi]

Another issue is the breakage on using --upstream option. It shows that somewhere on the ros release infra for this package, a crucial check is missing. Perhaps the person in charge of releasing gennodejs can help pinpoint the issue.

I'm not sure what came up but we could prioritize doing so if that makes the most sense here.

Adding a 2.0.3 tag to the latest (or future release) and a 2.0.2 tag retroactively would make most sense in accordance to semver

[sloretz]

#25
ros/rosdistro#23711

@chris-smith I think a 2.0.3 release is the least effor path: ros/rosdistro#23711 (comment)

It might be possible to fast-forward from my fork of this repo and my fork of the release repo, but I don't know all the branches and tags that would need to be brought over.