Skip to content

Move main to the 10.1-runic prerelease line after 10.0.0 - #45

Merged
ViktorJannicke merged 1 commit into
mainfrom
runic/next-10.1
Oct 30, 2026
Merged

ViktorJannicke merged 1 commit into
mainfrom
runic/next-10.1

Conversation

@ViktorJannicke

Copy link
Copy Markdown

10.0.0 is published (release, nuget.org). This moves main off the exact 10.0.0 so later pushes never produce the released version again.

  • version.json: 10.0.0 → 10.1-runic.{height}. Verified locally with dotnet pack -p:PublicRelease=true: RunicArtifex.DynamicData.10.1.0-runic.1.nupkg.
  • Why 10.1: the fork's scheme is major.minor-runic.{height} (as 10.0-runic.{height} was). 10.1.0-runic.N sorts above 10.0.0, keeps NBGV's height-based numbering, and leaves 10.0.x for fixes of the stable release; the next stable from this line would be 10.1.0.
  • Maintenance guide notes the current line.

Public API: none.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ViktorJannicke
ViktorJannicke merged commit dcf9a39 into main Oct 30, 2026
7 checks passed
@ViktorJannicke
ViktorJannicke deleted the runic/next-10.1 branch October 30, 2026 13:13
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