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

Support Ignoring Specific Versions #375

Closed
Lwiczyn opened this issue Oct 18, 2019 · 5 comments
Closed

Support Ignoring Specific Versions #375

Lwiczyn opened this issue Oct 18, 2019 · 5 comments

Comments

@Lwiczyn
Copy link

Lwiczyn commented Oct 18, 2019

I am running dependabot-script against https://mvnrepository.com/artifact/org.springframework.cloud/spring-cloud-stream-dependencies . The problem I am running into is that this repository began being versioned like this:

1.0.2
1.0.1

Then transitioned to being versioned like this:

Chelsea.RELEASE
Brooklyn.RELEASE

Consequently, the dependabot-script ends up thinking that I should update from Fishtown.SR2 (released March 2019) to 1.0.3 (released September 2016) which is incorrect.

I was wondering if there was any current or planned way to pass a list of ignored versions to dependabot-script so we could clean up this confusion manually.

@ju5t
Copy link

ju5t commented Oct 21, 2019

I don't think a .dependabot/config.yml is supported, unfortunately. We've tried that but it didn't work.

@greysteil
Copy link
Contributor

No plans for supporting config.yml files in Dependabot script - those are for the Dependabot application, and this script is really just a reference for how to use Dependabot Core. Would be happy to accept a PR for it if someone really wants to add it, though!

@ju5t
Copy link

ju5t commented Oct 21, 2019

If I had a clue about Ruby I probably would, unfortunately, I'm not a massive Ruby fan so wouldn't know where to begin. I hope someone can find the time to implement this.

@Lwiczyn
Copy link
Author

Lwiczyn commented Oct 21, 2019

@greysteil I'm on github enterprise at the moment and might not have access to the official dependabot goodness for some time. If I can free up some bandwidth for a PR, is there any preference as far as yaml format? Also, given other features here might also want to leverage a config.yml, does the dependabot team have any asks regarding implementation?

@greysteil
Copy link
Contributor

I'd go for compatibility with the format the main application uses - docs for that are at https://dependabot.com/docs/config-file/. Maybe start with just the bits you need and leave it to others to extend further :octocat:

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

No branches or pull requests

3 participants