Skip to content

Upgrade ormolu from 0.7.2.0 to 0.8.0.2#3931

Draft
cprecioso wants to merge 4 commits intocprecioso/minnetonka-v2from
cprecioso/upgrade-ormolu
Draft

Upgrade ormolu from 0.7.2.0 to 0.8.0.2#3931
cprecioso wants to merge 4 commits intocprecioso/minnetonka-v2from
cprecioso/upgrade-ormolu

Conversation

@cprecioso
Copy link
Member

@cprecioso cprecioso commented Mar 18, 2026

Description

Upgrade ormolu to the latest version (0.8.0.2) via mise. Updates mise.toml to track latest and regenerates mise.lock with the new binary URLs and checksums. Builds on #3930, which introduced mise for tool management.

Then, ran format with the new version.

Type of change

  • 🔧 Just code/docs improvement
  • 🐞 Bug fix
  • 🚀 New/improved feature
  • 💥 Breaking change

Checklist

  • I tested my change in a Wasp app to verify that it works as intended.

  • 🧪 Tests and apps:

    • I added unit tests for my change.
    • (if you fixed a bug) I added a regression test for the bug I fixed.
    • (if you added/updated a feature) I added/updated e2e tests in examples/kitchen-sink/e2e-tests.
    • (if you added/updated a feature) I updated the starter templates in waspc/data/Cli/templates, as needed.
    • (if you added/updated a feature) I updated the example apps in examples/, as needed.
      • (if you updated examples/tutorials) I updated the tutorial in the docs (and vice versa).
  • 📜 Documentation:

    • (if you added/updated a feature) I added/updated the documentation in web/docs/.
  • 🆕 Changelog: (if change is more than just code/docs improvement)

    • I updated waspc/ChangeLog.md with a user-friendly description of the change.
    • (if you did a breaking change) I added a step to the current migration guide in web/docs/migration-guides/.
    • I bumped the version in waspc/waspc.cabal to reflect the changes I introduced.

@cprecioso cprecioso self-assigned this Mar 18, 2026
@cprecioso cprecioso had a problem deploying to railway-deploy-test March 18, 2026 09:28 — with GitHub Actions Failure
@cprecioso cprecioso changed the title Upgrade ormolu Upgrade ormolu from 0.7.2.0 to 0.8.0.2 Mar 18, 2026
@pkg-pr-new
Copy link

pkg-pr-new bot commented Mar 18, 2026

Open in StackBlitz

@wasp.sh/wasp-cli

npx https://pkg.pr.new/@wasp.sh/wasp-cli@3931

@wasp.sh/wasp-cli-darwin-arm64-unknown

npx https://pkg.pr.new/@wasp.sh/wasp-cli-darwin-arm64-unknown@3931

@wasp.sh/wasp-cli-darwin-x64-unknown

npx https://pkg.pr.new/@wasp.sh/wasp-cli-darwin-x64-unknown@3931

@wasp.sh/wasp-cli-linux-x64-glibc

npx https://pkg.pr.new/@wasp.sh/wasp-cli-linux-x64-glibc@3931

@wasp.sh/wasp-cli-linux-x64-musl

npx https://pkg.pr.new/@wasp.sh/wasp-cli-linux-x64-musl@3931

commit: 17908bd

@cprecioso cprecioso temporarily deployed to railway-deploy-test March 18, 2026 09:46 — with GitHub Actions Inactive
[tools]
cabal-gild = "1.5.0.1"
ormolu = "0.7.2.0"
ormolu = "latest"
Copy link
Member Author

Choose a reason for hiding this comment

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

Uses latest so that Mise can prompt us to upgrade this version when using mise upgrade. The version is pinned in the lockfile (to the current latest 0.8.0.2) and won't update under our feet.

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.

1 participant