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.

Sign up for GitHub

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

Jump to bottom

Update to latset GitReleaseManager (currently 0.19.0) #195

Open
2 tasks done
gep13 opened this issue Feb 21, 2025 · 0 comments
Open
2 tasks done

Update to latset GitReleaseManager (currently 0.19.0) #195

gep13 opened this issue Feb 21, 2025 · 0 comments
Assignees
@gep13
Labels
1 - Ready Issue is accepted, milestone added and are ready to be worked on Improvement Issues that enhances existing functionality, or adds new features
Milestone
0.30.0

Comments

@gep13
Copy link
Member

gep13 commented Feb 21, 2025

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

When attempting some operations on GitLab repositories, there is a mapping issue between int and long. This is a known issue with the NGitLab library that GitReleaseManager uses. A newer version of NGitLab is now being used in GitReleaseManager, which has been proven to fix the problem, we just need to update to the newly available version.

Describe The Solution. Why is it needed?

We need to update the gitReleaseManagerGlobalTool and gitReleaseManagerTool strings in the toolsettings.cake file to use 0.19.0 as a minimum. This is the first version that addresses an issue preventing some operations on GitLab repositories due to a mapping issue between int and long.

Additional Context

N/A

Related Issues

N/A
@gep13 gep13 added this to the 0.30.0 milestone Feb 21, 2025
@gep13 gep13 added Improvement Issues that enhances existing functionality, or adds new features 1 - Ready Issue is accepted, milestone added and are ready to be worked on labels Feb 21, 2025
@gep13 gep13 self-assigned this Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gep13 gep13

Labels
1 - Ready Issue is accepted, milestone added and are ready to be worked on Improvement Issues that enhances existing functionality, or adds new features
Projects
None yet
Milestone
0.30.0
Development

No branches or pull requests
1 participant
@gep13