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.

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

Enable dependabot #1309

Merged
merged 1 commit into from
Oct 11, 2022
Merged

Enable dependabot #1309

merged 1 commit into from
Oct 11, 2022

Conversation

akurtakov
Copy link
Contributor

No description provided.

@rgrunber
Copy link
Contributor

Looks the same as https://github.com/eclipse/eclipse.jdt.ls/blob/master/.github/dependabot.yml . @datho7561 , do you see any problems with this ?

@datho7561
Copy link
Contributor

I know that at one point a version of dependabot was running on this repository. You can see PRs that it has opened: #1250, #1288. We might need to reach out to Fred to disable the other version of dependabot once this PR has been merged. Did you deal with something similar on eclipse.jdt.ls, @rgrunber ?

Other than that, this PR looks good to me.

@rgrunber
Copy link
Contributor

Note that junit and jetty-server update pretty frequently.

When I look on a personal fork, I don't see some "other" dependabot. For version updates the config file seems to be the only way. There are options to enable dependabot for security updates which is what those may have been ?

@datho7561
Copy link
Contributor

Oh okay, so this will make PRs for version updates, even if there aren't security updates?

Copy link
Contributor

@datho7561 datho7561 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems very helpful. Thanks @akurtakov !

@datho7561 datho7561 added this to the 0.22.0 milestone Oct 11, 2022
@datho7561 datho7561 merged commit 02f8088 into eclipse-lemminx:main Oct 11, 2022
@akurtakov
Copy link
Contributor Author

You're welcome. Btw, is there a reason why JSoup and Jetty PRs dependabot opened are pending and not merged?

@datho7561
Copy link
Contributor

The JSoup update has breaking API changes, and a dependency we are using (which is deprecated) depends on the old version. I'll take a look into Jetty.

@rgrunber
Copy link
Contributor

You're welcome. Btw, is there a reason why JSoup and Jetty PRs dependabot opened are pending and not merged?

I think updating jsoup would break remark-java (#1291). Not sure about jetty.

@datho7561
Copy link
Contributor

It looks like the jetty version which fixes the vulnerability requires Java 11

@akurtakov
Copy link
Contributor Author

It looks like the jetty version which fixes the vulnerability requires Java 11

Is requiring Java 11 problem for Lemminx?

@rgrunber
Copy link
Contributor

I don't think there's any technical issues. It's mainly that clients would need to support users with only Java 1.8 on their system. Ther's a good amount of people probably still on Java 1.8. @datho7561 , If we had to switch, I think the client-side could detect when a JVM doesn't meet the minimum required version (eg. 11) and activate the binary version of LemMinX in those cases. Right ? As an example for vscode-xml, it would somewhere at https://github.com/redhat-developer/vscode-xml/blob/fcab66d6c35e497fbfb534c4f0ea6f4fa7d4f822/src/server/serverStarter.ts#L28 .

Moving to 11 would allow use to use flexmark-java though.

@datho7561
Copy link
Contributor

If we had to switch, I think the client-side could detect when a JVM doesn't meet the minimum required version (eg. 11) and activate the binary version of LemMinX in those cases. Right?

Yep, looking through the code that seems to be what vscode-xml will do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants