Skip to content

[Chore] Update some versions#140

Merged
gromakovsky merged 7 commits intomasterfrom
gromak/maintenance-july23
Sep 22, 2023
Merged

[Chore] Update some versions#140
gromakovsky merged 7 commits intomasterfrom
gromak/maintenance-july23

Conversation

@gromakovsky
Copy link
Member

@gromakovsky gromakovsky commented Jul 13, 2023

Description

Boring PR that updates some upper bounds and version in CI config.

Related issue(s)

None

✅ Checklist for your Pull Request

Ideally a PR has all of the checkmarks set.

If something in this list is irrelevant to your PR, you should still set this
checkmark indicating that you are sure it is dealt with (be that by irrelevance).

Related changes (conditional)

  • Tests

    • If I added new functionality, I added tests covering it.
    • If I fixed a bug, I added a regression test to prevent the bug from
      silently reappearing again.
  • Documentation

    • I checked whether I should update the docs and did so if necessary:
  • Public contracts

    • Any modifications of public contracts comply with the Evolution
      of Public Contracts
      policy.
    • I added an entry to the changelog if my changes are visible to the users
      and
    • provided a migration guide for breaking changes if possible

Stylistic guide (mandatory)

✓ Release Checklist

  • I updated the version number in o-clock.cabal.
  • I updated the changelog and moved everything
    under the "Unreleased" section to a new section for this release version.
  • If any definitions (functions, type classes, instances, etc) were added,
    I added @since haddock annotations.
  • (After merging) I created a new entry in the releases page,
    with a summary of all user-facing changes.
    • I made sure a tag was created using the format vX.Y.Z
  • (After merging) I uploaded the package to hackage.

@gromakovsky gromakovsky force-pushed the gromak/maintenance-july23 branch 2 times, most recently from e31db98 to e17cdfc Compare July 13, 2023 09:00
The change log is available [on GitHub][2].

Unreleased
1.4.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should update this as well:

I updated the version number in o-clock.cabal.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, yep, actually I wanted to mark it as a draft while I'm messing with CI, but you were quite fast :D
I'll do it

@gromakovsky gromakovsky force-pushed the gromak/maintenance-july23 branch 6 times, most recently from 8408ad3 to 6b8c406 Compare July 19, 2023 09:41
Problem: CI uses old versions of stack and cabal, also tests
our package with old GHCs.

Solution: update stack and cabal to the latest ones, update GHC
versions to support the latest 4.
Also update `tested-with`.
Problem: TypeInType extension is deprecated since some recent
GHC version, but we are using it.

Solution: use DataKinds and PolyKinds instead as GHC suggests.
@gromakovsky gromakovsky force-pushed the gromak/maintenance-july23 branch from 6b8c406 to 09bda57 Compare September 22, 2023 11:33
Problem: due to
ghc/ghc@13d627b
we get different output in doctest for GHC 9.6 and 9.4.
So with 9.6 they started to fail.

Solution: force redundant promotion ticks for now. Add a comment that
we should remove it when we stop supporting older GHCs.
Another option would be to use CPP, but we already have 2 cases
and supporting 3 cases sounds too verbose.
@gromakovsky gromakovsky force-pushed the gromak/maintenance-july23 branch from 09bda57 to 28c65b7 Compare September 22, 2023 11:47
Problem: Haddock CI step tries to build haddock for everything and
fails to do it for doctest for an obscure reason.

Solution: we don't really care about Haddock for anything besides
the library, so the easiest solution seems to be to build Haddock only
for the library, which is the default.
We removed `toNum` some time ago, now it seems to be ok to release it.
Since it's a breaking change, we are increasing the middle version
component.
@gromakovsky gromakovsky force-pushed the gromak/maintenance-july23 branch from 28c65b7 to 415f1cc Compare September 22, 2023 17:13
@gromakovsky gromakovsky merged commit 9b9e4d5 into master Sep 22, 2023
@gromakovsky gromakovsky deleted the gromak/maintenance-july23 branch September 22, 2023 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants