Closed RustyNova016 closed 3 months ago
BTW, the documentation errors aren't mine, and probably better into a separate PR
Once #29 is merged, the target branch for this PR should be changed to main
, and rebased against main
.
@RustyNova016 I don't want to conflate matters, so would it be OK if I leave the rebasing to you?
Then we can look at merging.
@RustyNova016 Could you rebase this PR so that it only includes commit https://github.com/InputUsername/listenbrainz-rs/pull/32/commits/da9d776e5e8d0a21fdf8591d050038828b65f9b3? The other commits have landed in main now.
@InputUsername To save time, I've rebased locally and pushed to my fork - this look good to you?
@InputUsername To save time, I've rebased locally and pushed to my fork - this look good to you?
Looks fine to me!
Looks like CI failed. Looking into it.
Fixed.
The doctests failed due to the changes in this PR, so I feel it's OK to keep the fix here. I will squash the last two commits together, though. Rebasing now.
This might still need actioning: https://github.com/RustyNova016/listenbrainz-rs/issues/19#issue-2291466134
Should be good to go! I was busy today, and mostly forgot about doing the annotation fix.
I'm sure there might have some obscure options left missing, but the documentation not usage made me discover them.
Should be good to go! I was busy today, and mostly forgot about doing the annotation fix.
I'm sure there might have some obscure options left missing, but the documentation not usage made me discover them.
Once we resolve the review above, I'll squash the last commit, and we can merge.
Oh I thought I only put a comment, not a review. Sorry for that
I've squashed the commits in this PR into one and signed off the commit. I'll re-request a review from @InputUsername and myself, then we can merge!
Builds and tests pass on my end. Awaiting CI.
Nice! Is there's still stuff needed before do 8.0? Just wondering.
Nice! Is there's still stuff needed before do 8.0? Just wondering.
34 will be delayed as I'm busy for the next few weeks, so if y'all rather release what we have already, it's fine
I think we're good to go for the 0.8.0 release. And no worries, that was the original plan anyway I think :smile:
@shymega could you give everything a sanity check? If everything is OK I'll roll out the release.
@InputUsername I'll try and have a look, but got an interview with an embedded company this week, so need to prep everything for that. At least, I think it's an interview. Given tests pass, the main thing I can think of is breaking-changes checks. So we can announce that to downstream users.
@InputUsername I'll try and have a look, but got an interview with an embedded company this week, so need to prep everything for that. At least, I think it's an interview. Given tests pass, the main thing I can think of is breaking-changes checks. So we can announce that to downstream users.
No worries, good luck with the interview, obviously focus on that!
The version bump should already imply breaking changes - Rust "breaks" semver by treating 0.x releases as major versions - but good call, I'll check to make sure breaking changes are mentioned in the changelog. I'll also check if the added methods actually work haha.
There's the I at least know that user_listens got its api changed to remove the useless time range part
The current implementation require a full jspf struct to insert a playlist, while most of that information get discarded.
So I made a series of specialized structs for the creation specifically