Skip to content

Conversation

@GrantBirki
Copy link
Contributor

Summary

Since there have been important bug fixes made to this project, we should cut a new release and publish a new version of the Gem so folks can use this Gem again.

Release Note

Important bug fixes were made via #266 and #269. This release includes them!

Documentation

N/A

@landongrindheim
Copy link
Contributor

@GrantBirki This will be 🤏 easier to merge if your commit is signed. Rebasing onto main should take care of the smoke tests failures as well.

@GrantBirki GrantBirki force-pushed the grantbirki/cut-new-release branch from 0058368 to 9b29517 Compare October 22, 2025 16:16
@GrantBirki
Copy link
Contributor Author

@landongrindheim Commit sign-off should be good now and I see the DCO check is now passing.

@landongrindheim
Copy link
Contributor

@segiddins @woodruffw What do you think about cutting a release with these fixes?

@woodruffw
Copy link
Member

No objection from me, but @segiddins has final say here (I'm just a triager / second person operator for this repo).

@segiddins segiddins enabled auto-merge (squash) October 25, 2025 02:02
Signed-off-by: GrantBirki <grant.birkinbine@gmail.com>
@segiddins segiddins force-pushed the grantbirki/cut-new-release branch from 83165b8 to 290c8a2 Compare October 25, 2025 02:02
@segiddins segiddins merged commit a8e5cc8 into sigstore:main Oct 25, 2025
42 checks passed
@GrantBirki GrantBirki deleted the grantbirki/cut-new-release branch October 27, 2025 16:32
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.

4 participants