Skip to content

Conversation

edmundnoble
Copy link
Contributor

No description provided.

Change-Id: Id000000075e199b0cd2fa975ec515a46a9f57f99
@edmundnoble edmundnoble requested a review from larskuhtz May 6, 2025 01:52
Copy link
Contributor

Choose a reason for hiding this comment

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

I think, eventually we'll have to decide whether we want to get rid of cabal.project.freeze or whether we want to keep it. Otherwise we'll keep deleting it (which breaks CI) and readding it (to unbreak CI).

If we decide to get rid of it, we should do that in a separate commit to master and update CI (and the release workflows) accordingly.

@edmundnoble edmundnoble force-pushed the pp/evm branch 2 times, most recently from babf798 to e5977dc Compare May 22, 2025 18:20
@larskuhtz larskuhtz force-pushed the pp/evm branch 2 times, most recently from 8776687 to e5977dc Compare May 22, 2025 19:00
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