Turns out this is intended behavior. There is specific pre-1.0 logic that makes major versions bump the minor and everything else bump the patch version. See

librarian/internal/semver/semver.go

Lines 228 to 236 in 4d30998

    
           if currentSemVer.Major == 0 { 
        
           	if highestChange == Major { 
        
           		currentSemVer.Major++ 
        
           		currentSemVer.Minor = 0 
        
           		currentSemVer.Patch = 0 
        
           	} else { // feat and fix result in a patch bump for pre-1.0.0 
        
           		currentSemVer.Patch++ 
        
           	} 
        
           } else {

Note: in release-please this versioning strategy was configurable per-repo with the bump-minor-pre-major and bump-patch-for-minor-pre-major config options (https://github.com/googleapis/release-please/blob/3cf5360f9172efe2af41890df072a202730ddd5b/schemas/config.json#L15-L22)

These configurations default to false in release-please

	if currentSemVer.Major == 0 {
	if highestChange == Major {
	currentSemVer.Major++
	currentSemVer.Minor = 0
	currentSemVer.Patch = 0
	} else { // feat and fix result in a patch bump for pre-1.0.0
	currentSemVer.Patch++
	}
	} else {

librarian release bumps minor version #2109

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions