Skip to content

Tags/Releases don't match what's been released #61

@myronmarston

Description

@myronmarston

On rubygems.org I see that 3.1.3 and 3.2.0 have both been released, but I don't see any tags for those versions or releases--the tags and releases stop at 3.1.2.

Can you tag the SHAs that were used by those versions, add GH releases for them, and improve your release process to do both for future versions?

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions