Skip to content

Bump typelit plugins#3164

Open
rowanG077 wants to merge 1 commit intomasterfrom
bump-typelit-plugins
Open

Bump typelit plugins#3164
rowanG077 wants to merge 1 commit intomasterfrom
bump-typelit-plugins

Conversation

@rowanG077
Copy link
Copy Markdown
Member

Due to quite a few regressions in the prior versions of the plugins I would like to bump them. While doing this I noticed that the bounds are not the same for all sub-projects. I made them identical. However it might be better to only put bounds on clash-prelude and remove the bounds on clash-cosim and clash-ghc as they pull in clash-prelude anyway.

Still TODO:

  • Write a changelog entry (see changelog/README.md)
  • Check copyright notices are up to date in edited files

@rowanG077 rowanG077 changed the title Bump typelit plugin Bump typelit plugins Mar 20, 2026
@rowanG077 rowanG077 requested a review from leonschoorl March 20, 2026 10:08
@DigitalBrains1
Copy link
Copy Markdown
Member

Regarding the failures of GitLab CI: you should bump index-state in /cabal.project. CI explicitly checks that a build plan can be produced without cabal.project.local. Only after that will it continue with cabal.project.local in place, which will set the index-state to the latest version.

I agree that for our own packages that depend on clash-prelude, we can omit the bounds. We do that in the starter project as well. Unless someone can think of a convincing reason that some packages need their own bounds; I'm not ruling out that I am missing some intricacy, but I think it would be okay.

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