Skip to content

chore(release): Bump version to 0.4.2-SNAPSHOT#23

Merged
arcaputo3 merged 1 commit intomainfrom
chore/bump-0.4.2-snapshot
Mar 17, 2026
Merged

chore(release): Bump version to 0.4.2-SNAPSHOT#23
arcaputo3 merged 1 commit intomainfrom
chore/bump-0.4.2-snapshot

Conversation

@arcaputo3
Copy link
Copy Markdown
Contributor

Summary

  • Bump build.mill fallback version to 0.4.2-SNAPSHOT
  • Bump package.json version to 0.4.2-SNAPSHOT

Post-release snapshot bump after v0.4.1 tag.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@claude
Copy link
Copy Markdown

claude bot commented Mar 17, 2026

PR Review: chore(release): Bump version to 0.4.2-SNAPSHOT

This is a straightforward post-release snapshot bump. The changes are minimal and correct.

Code Quality / Correctness

  • build.mill: The fallback version string correctly reflects the next development snapshot (0.4.2-SNAPSHOT). Using Task.Input ensures the env var is re-evaluated each run (not cached), which is the right approach for CI-driven version injection.
  • package.json: Version bump aligns with the Scala/Mill version. Good to keep these in sync.

Minor Observations

  1. Snapshot suffix convention: 0.4.2-SNAPSHOT is standard Maven/SBT convention. Since this is a Mill + Scala.js project publishing to npm as well, it's worth confirming that downstream npm consumers are OK with a -SNAPSHOT suffix — npm semver treats this as a pre-release identifier (it is valid, but tools parsing semver may sort it unexpectedly relative to 0.4.1). If npm publishing is ever automated, you may want 0.4.2-SNAPSHOT.0 or a consistent pre-release scheme.

  2. No version file drift: There doesn't appear to be any other place (e.g., a VERSION file, docs, or README badge) that needs updating — looks clean.

Summary

No bugs, no security concerns, no test coverage gaps (this is a pure version bump). The PR does exactly what it says. Ready to merge once CI passes.

Generated with Claude Code

@arcaputo3 arcaputo3 merged commit 65fce1f into main Mar 17, 2026
3 checks passed
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