Try pinning Octokit to v6.0.0 in build.fsx#2810
Merged
Merged
Conversation
xperiandri
approved these changes
Aug 29, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I think (/am guessing) that the error in the release build at https://github.com/fsprojects/FAKE/actions/runs/10605838278/job/29395428955#step:10:618 is because the Paket restore for build.fsx is restoring version 13 of Octokit, along side a release package of Fake.Api.GitHub which doesn't work with that version due to breaking API changes, and that's causing problems.
So - try pinning the Octokit nuget reference in build.fsx to 6.0.0 to match the released FAKE packages.