Skip to content

Conversation

@jackkoenig
Copy link
Contributor

Type of Improvement

  • Internal or build-related (includes code refactoring/cleanup)

Desired Merge Strategy

  • Squash

Release Notes

Reviewer Checklist (only modified by reviewer)

  • Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
  • Did you mark the proper milestone (Bug fix: 3.6.x, 5.x, or 6.x depending on impact, API modification or big change: 7.0)?
  • Did you review?
  • Did you check whether all relevant Contributor checkboxes have been checked?
  • Did you do one of the following when ready to merge:
    • Squash: You/ the contributor Enable auto-merge (squash) and clean up the commit message.
    • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

@jackkoenig jackkoenig added the Internal Internal change, does not affect users, will be included in release notes label Nov 24, 2025
@@ -1,4 +1,4 @@
//| mill-version: 1.0.3
//| mill-version: 1.0.6-jvm
Copy link
Member

Choose a reason for hiding this comment

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

Giving up, I see. 😉 This makes sense to me, though.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not happy about it lol but alas

@jackkoenig jackkoenig merged commit 0f6b7fe into main Nov 24, 2025
19 checks passed
@jackkoenig jackkoenig deleted the bump-mill branch November 24, 2025 22:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Internal Internal change, does not affect users, will be included in release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants