so i will continue working on my PRs on top of 1.16

no worries, you should be fine

master is failing because of the version mismatch

it has to be that way 😢

i think hachish release might not alwys be good.. would be nice to have that state in source control, in a extra branch or so

well yeah

i didn’t want to do this too but ¯\_(ツ)_/¯

i think i want to be nice to everyone that uses our library 😺

let’s not do this again though

its fine, guess it just means my PRs will in 1.16.1 earliest

i use a bit of git hackish on my local machine

does not matter since they are really just buildscript cleanups

sure

thanks bro!

inconsistency fuel-coroutines vs fuel-kotlinx-serialization

I'd really like to use inline classes in buildSrc for versions and dependenciies, so i do not mix up strings by accident

but for that to be useful i'd have to add overloads to compile() and such functions

@kittinunf https://github.com/kittinunf/Fuel/pull/471

and another issue #473 and PR to fix it in #474

the 1.16 tag and github release were removed ? why ?

it wasn’t removed … i forgot to press “publish” 😅

😌

Is Fuel not meant for non-Android Kotlin usage? I found a bug that I would like to fix and create a PR for, but the project wants me to have an Android SDK to work in Idea. (I don't have an Android SDK, and I don't want an Android SDK.)

it can be used without

but for development you have to complie the android modules too

I guess I can comment out all the android stuff in

settings.gradle.kts

and

build.gradle.kts

.

hopefully, did not work for me so i gave in and installed AS

If it comes to that, I'm just going back to Apache HttpComponents. ):

well that would just be sad, whats the bug ?

Which would be too bad, because otherwise I really like Fuel.