chore: regenerate .opam files for the 0.3.0 version bump - #338
Merged
Conversation
dune-project was bumped to 0.3.0 for the release, but the committed dune-generated forge.opam, march.opam, and march-lsp.opam still said 0.2.0, so any dune invocation that regenerates opam files dirtied unrelated worktrees with this diff.
The 0.3.0 release bumped dune-project but not the committed dune-generated .opam files, so every subsequent dune build dirtied the working tree with the 0.2.0->0.3.0 version diff. Make regenerating and committing the opam files an explicit step of cutting a release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 0.3.0 release commit (3206b31) bumped
dune-projectto 0.3.0 but left the committed dune-generatedforge.opam,march.opam, andmarch-lsp.opamat 0.2.0. Since those files are regenerated by dune, anydune buildthat touches them dirtied the working tree with the version diff — observed polluting three unrelated worktree sessions on 2026-08-24.dune build --root . forge.opam march.opam march-lsp.opam); the diff is exactly the threeversion:lines, nothing else.specs/github_release_builds.mdso this doesn't recur at the next release.