Initial Hackage release

Author: georgefst

CHANGELOG.md

@@ -1,5 +1,5 @@
 # Revision history for spotify
 
-## 0.1.0.0 -- 2020-03-18
+## 0.1.0.0 -- 2023-06-22
 
-* First version. Released on an unsuspecting world.
+* First release. Unstable.

README.md

@@ -1,11 +1,7 @@
 # Spotify Web API bindings for Haskell
 
-Built around Servant + Aeson.
+Designed to be very high-level (eg. handling token refresh etc. automatically). Though it should be possible to expose more of the lower level functionality if anyone requests it. At the very least, the raw Servant encoding of the API is available in `spotify-servant`, on which the main library depends.
 
-Work in progress. Will be put on Hackage once remotely stable.
+Designed for use with lenses and/or modern record extensions (`OverloadedRecordDot` etc.), e.g. to work around duplicated identifiers. This allows us to mirror the Spotify API in a methodical way without being too verbose.
 
-Designed to be very high-level (eg. handling token refresh etc. automatically). I can think about exposing the lower level functionality if anyone requests it.
-
-Designed for use with lenses and/or modern record extensions, eg. to work around duplicated identifiers. This allows us to mirror the Spotify API in a methodical way without being too verbose. `RecordDotSyntax` will suit us nicely whenever it lands.
-
-All request take place inside a monad implementing `MonadSpotify`. In particular, this abstracts away authentication - we don't need to explicitly pass tokens around. A concrete monad `Spotify` is provided, though you'll often want to roll your own. There is also an instance `MonadSpotify IO` - this caches authentication data to disk, so one should be careful about security. It also creates a new connection `Manager` for every request, which can be expensive. Thus a `State`-like monad is preferred for serious code. Nonetheless, being able to run the functions directly in `IO` can be very convenient, especially from `GHCI`.
+All requests take place inside a monad implementing `MonadSpotify`. In particular, this abstracts away authentication, meaning that we don't need to explicitly pass tokens around. A concrete monad `Spotify` is provided, though you'll often want to roll your own. There is also an instance `MonadSpotify IO`, which caches authentication data to disk, so one should be careful about security. It also creates a new connection `Manager` for every request, which can be expensive. Thus a `State`-like monad is preferred for serious code. Nonetheless, being able to run the functions directly in `IO` can be very convenient, especially from `GHCI`.

spotify.cabal

@@ -20,7 +20,7 @@ source-repository head
 
 common common
     build-depends:
-        base >= 4.16,
+        base >= 4.16 && < 5,
         aeson ^>= 2.1.0,
         bytestring ^>= 0.11.3,
         composition ^>= 1.0.2,