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

[BUG] Implement GH action to sync deps in analyzer lsp and all external providers #610

Open
1 task done
fbladilo opened this issue May 28, 2024 · 2 comments
Open
1 task done

[BUG] Implement GH action to sync deps in analyzer lsp and all external providers #610

fbladilo opened this issue May 28, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fbladilo
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

release-0.4

Priority

Major

Current Behavior

We need to run go mod tidy in analyzer-lsp and all external providers when cutting a new release branch, this will sync deps properly for downstream building

Expected Behavior

All components deps are synced with go mod tidy when a new release branch is cut

How Reproducible

Always (Default)

Steps To Reproduce

No response

Environment

- **Analyzer Image SHA** 
- **JDTLS  base image SHA**
- **Provider Settings JSON**

Anything else?

No response
@fbladilo fbladilo added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 28, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning May 28, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label May 28, 2024
@djzager djzager added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels May 29, 2024
@konveyor-ci-bot konveyor-ci-bot bot removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. labels May 29, 2024
@pranavgaikwad pranavgaikwad moved this from 🆕 New to 🔖 Ready in Planning Jun 6, 2024
@Veer0x1
Copy link

Veer0x1 commented Dec 8, 2024

I would like to work on this issue. Could you please provide more details? As I am new to the codebase, any assistance from your side would be greatly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Planning
Status: 🔖 Ready
Milestone
No milestone
Development

No branches or pull requests
3 participants
@djzager @fbladilo @Veer0x1