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

Update to Cake.Issues 0.9.0 #26

Closed
pascalberger opened this issue Jul 12, 2020 · 3 comments · Fixed by #27
Closed

Update to Cake.Issues 0.9.0 #26

pascalberger opened this issue Jul 12, 2020 · 3 comments · Fixed by #27
Assignees
Milestone

Comments

@pascalberger
Copy link
Member

Update to build against Cake.Issues 0.9.0

@pascalberger
Copy link
Member Author

@janniksam There's a beta version of Cake.Issues 0.9.0 available. Do you want to update this addin to the latest version or should I take care of it?

@janniksam
Copy link
Contributor

@pascalberger
Cool. Is this already the version with the column-specification in warnings?

I will see what I can do in this week / the next couple of days.

@pascalberger
Copy link
Member Author

@janniksam Yes, this is the version with support for line ranges, columns and an identifier. See release notes. You can see this PR as an example what to do for update (update NuGet packages and documentation).

Afterwards you can implement support for new features (I would suggest to create individual issues for every new feature, since issues are used to create release notes).

I saw that there was never a final release for 0.8.0. Do you want to create the release or should I do this?
Also there are several dependency updates pending: https://github.com/cake-contrib/Cake.Issues.DupFinder/pulls. Cake.Core and Cake.Testing should not be updated (best practice is to build against lowest version with a compatible API). You can comment with @dependabot ignore this minor version to tell Depandabot to ignore this version.

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

Successfully merging a pull request may close this issue.

2 participants