[PR #272] [MERGED] Fix docs for v0.11.0 #363

New issue

Closed

opened 2026-02-27 20:24:25 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 20:24:25 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/ramsayleung/rspotify/pull/272
Author: @marioortizmanero
Created: 10/14/2021
Status: ✅ Merged
Merged: 10/14/2021
Merged by: @ramsayleung

Base: master ← Head: fix-docs

📝 Commits (2)

3a90df5 Fix release
66a00e3 Bump to v0.11.1

📊 Changes

4 files changed (+14 additions, -8 deletions)

View changed files

📝 Cargo.toml (+4 -4)
📝 rspotify-http/Cargo.toml (+8 -2)
📝 rspotify-macros/Cargo.toml (+1 -1)
📝 rspotify-model/Cargo.toml (+1 -1)

📄 Description

Turns out we also need #268 for rspotify-http, since the docs failed in the new release: https://docs.rs/crate/rspotify/0.11.0/builds/447703

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/ramsayleung/rspotify/pull/272 **Author:** [@marioortizmanero](https://github.com/marioortizmanero) **Created:** 10/14/2021 **Status:** ✅ Merged **Merged:** 10/14/2021 **Merged by:** [@ramsayleung](https://github.com/ramsayleung) **Base:** `master` ← **Head:** `fix-docs` --- ### 📝 Commits (2) - [`3a90df5`](https://github.com/ramsayleung/rspotify/commit/3a90df5e75ad7207d0bb36fb928e45aab4339a0c) Fix release - [`66a00e3`](https://github.com/ramsayleung/rspotify/commit/66a00e3341ebfab78b7fb8ea693a563e758b7232) Bump to v0.11.1 ### 📊 Changes **4 files changed** (+14 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `Cargo.toml` (+4 -4) 📝 `rspotify-http/Cargo.toml` (+8 -2) 📝 `rspotify-macros/Cargo.toml` (+1 -1) 📝 `rspotify-model/Cargo.toml` (+1 -1) </details> ### 📄 Description Turns out we also need #268 for `rspotify-http`, since the docs failed in the new release: https://docs.rs/crate/rspotify/0.11.0/builds/447703 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>