Search code, repositories, users, issues, pull requests...
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.
Developers using CI may also use a dependency bumping solution such as Renovate. Those users may also use haskell-actions to run tests.
Since Haskell libraries often have wide bounds, if there is no integration between Renovate and the test run, the test run might not actually use the newly released dependency. For example, the new version could be incompatible with the GHC version that they have configured.
The way I see it, the use of git trailers to relay constraints is a protocol. Ideally, that protocol would be specified somewhere, though I am not sure where this would be. Maybe it is a bit early to pin down these details. If you accept, we could use the haskell-actions repo to iterate on this, as we gather experience.
I'd like to contribute a sectionto the README. The section would be below Model Cabal workflow with caching. The new section would make suggestions on how to configure Renovate and Github Actions.
