packages feed

bytestring-lexing 0.5.0.8 → 0.5.0.9

raw patch · 2 files changed

+24/−10 lines, 2 filesdep ~basePVP ok

version bump matches the API change (PVP)

Dependency ranges changed: base

API changes (from Hackage documentation)

Files

CHANGELOG view
@@ -1,3 +1,7 @@+0.5.0.9 (2021-08-28):+    - Updated version bounds for GHC 9.4+0.5.0.8 (2021-11-02):+    - Updated version bounds for GHC 9.2.1 0.5.0.7 (2021-10-16):     - Switching from TravisCI to GithubActions 	- Linting Haddock warnings
bytestring-lexing.cabal view
@@ -1,20 +1,25 @@+Cabal-Version:  2.2+-- Cabal >=2.2 is required for:+--    <https://cabal.readthedocs.io/en/latest/cabal-package.html#common-stanzas>+-- Since 2.1, the Cabal-Version must be the absolutely first thing+-- in the file, even before comments.  Also, no longer uses ">=".+--    <https://github.com/haskell/cabal/issues/4899>+ ------------------------------------------------------------------- wren gayle romano <wren@cpan.org>                ~ 2021.11.02+-- wren gayle romano <wren@cpan.org>                ~ 2022.08.28 ---------------------------------------------------------------- --- Cabal >=1.10 is required by Hackage.-Cabal-Version:  >= 1.10-Build-Type:     Simple- Name:           bytestring-lexing-Version:        0.5.0.8+Version:        0.5.0.9+Build-Type:     Simple Stability:      provisional Homepage:       https://wrengr.org/software/hackage.html Bug-Reports:    https://github.com/wrengr/bytestring-lexing/issues Author:         wren gayle romano, Don Stewart Maintainer:     wren@cpan.org-Copyright:      Copyright (c) 2012–2021 wren gayle romano, 2008–2011 Don Stewart-License:        BSD3+Copyright:      2012–2022 wren romano, 2008–2011 Don Stewart+-- Cabal-2.2 requires us to say "BSD-3-Clause" not "BSD3"+License:        BSD-3-Clause License-File:   LICENSE  Category:       Data@@ -39,8 +44,11 @@ Extra-source-files:     AUTHORS, CHANGELOG, README.md --- This should work as far back as GHC 7.4.1, but we don't verify that by CI.+-- This should work as far back as GHC 7.4.1 (== the lower-bound+-- on base), but we don't verify that by CI therefore we don't list it. -- <https://github.com/wrengr/bytestring-lexing/actions?query=workflow%3Aci>+-- For older versions of GHC and older versions of this library, see:+-- <https://matrix.hackage.haskell.org/#/package/bytestring-lexing/> Tested-With:     GHC ==8.0.2,     GHC ==8.2.2,@@ -67,13 +75,15 @@     -- These lower bounds are probably more restrictive than     -- necessary.  But then, we don't maintain any CI tests for     -- older versions, so these are the lowest bounds we've verified.+    -- (Version 0.5.0.2 had base>=4, and according to the matrix+    -- link above, that does build on GHC 7.0.4 == base-4.3.1.0).     --     -- TODO(2021-10-23): bytestring 0.11.0.0 changed the internal     --   representation of ByteStrings to remove the offset.  While     --   they do offer pattern synonyms for backwards combatibility,     --   we should re-verify that our code doesn't depend on the details.     --   <https://github.com/haskell/bytestring/pull/175>-    Build-Depends:  base              >= 4.5      && < 4.17+    Build-Depends:  base              >= 4.5      && < 4.18                  ,  bytestring        >= 0.9.2.1  && < 0.12  ----------------------------------------------------------------