Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Chore] Use LTS-21 #290

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open

[Chore] Use LTS-21 #290

wants to merge 9 commits into from

Conversation

gromakovsky
Copy link
Member

@gromakovsky gromakovsky commented Sep 25, 2023

Description

This PR updated the Stackage resolver to the latest one and does some related cleaning.

Related issue(s)

Resolves #285

✅ 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 package.yaml.
  • I updated the changelog and moved everything
    under the "Unreleased" section to a new section for this release version.
  • (After merging) I edited the auto-release.
    • Change the tag and title using the format vX.Y.Z.
    • Write a summary of all user-facing changes.
    • Deselect the "This is a pre-release" checkbox at the bottom.
  • (After merging) I updated xrefcheck-action.
  • (After merging) I uploaded the package to hackage.

@serokell-bot
Copy link
Contributor

1 Warning
⚠️ Bad issue ID in branch name.
Valid format for issue IDs: #123 or chore.

Generated by 🚫 Danger

Problem: we take nyan-interpolation from GitHub, which is harder
to manage than if we take it from Hackage.
Fortunately, the latest version is now available and suits us.

Solution: specify Hackage version of nyan-interpoation[-core]
in extra-deps.
@Martoon-00
Copy link
Member

CI is failing due to warnings / compilation errors also related to LTS-21. Other than that, LGTM.

@gromakovsky
Copy link
Member Author

@Martoon-00 if you volunteer to fix them by any chance, feel free to go ahead 😉

@Martoon-00
Copy link
Member

Okay, I fixed the errors that I saw (note there are fixup commits, you may want to squash them after reviewing them).

However now some really scary errors bumped up, and I have to switch to other activities, so giving up on this right now.

gromakovsky and others added 7 commits March 29, 2024 17:21
Problem: we use lts-19.13 which is getting somewhat old.
It's a good practice to update versions from time to time.
Solution: use lts-21.25.
1. The project no longer uses `niv`, so the comment about it is
irrelevant. Dependencies are normally updated by the update-daemon
nowadays.
2. cmark-gfm is available in lts-21.13.
Problem: this is a new warning which wants us to provide an explicit
kind signature for each type we define. It sounds too verbose to do.

Solution: disable this warning.
Problem: retryAfterInfo doesn't compile because the type of
readMaybe got more polymorphic in Universum.

Solution: specify explicitly that the argument is Text.
N.B. In the previous version it was String (due to the old type of
readMaybe), but Text is generally preferable, so we're changing it.
Problem: some lens-related things that we use got deprecated in
Universum.
Solution: do not use them, import them from Control.Lens instead.
Problem: CI job for Windows compiles against specific GHC version.

Solution: update it to match LTS version.
Problem: somehow, after the previous commits one test broke, now
xrefcheck outputs location where previously it didn't.

Solution: it seems for good, so update the expected output in that test.
@gromakovsky
Copy link
Member Author

gromakovsky commented Mar 29, 2024

note there are fixup commits, you may want to squash them after reviewing them

Reviewed, squashed.

Also updated the resolved to a bit newer one, so that a newer minor GHC version is used. Let's see if it helps with any of scary errors.
UPD: there are still some weird errors, not sure if it helped with any of them, but definitely not with all of them.

Problem: Cross-compilation to windows is broken.

Solution:
1) Build 'bitvec' without 'simd' flag since it causes the build to fail.
2) Remove old workaround for 'iserv-proxy-interprete' because the
   aforementioned issue was fixed in newer GHC versions.
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.

Update stack setup for upgrading GHC
4 participants