Skip to content

Cut a new release for v0.5.2? #101

@cbisnett

Description

@cbisnett

Due to the default usage of C23 in Fedora 42, I've run into a few issues with gems that fail to build native extensions, rbtrace being one of them. The work done in #100 has fixed the issue and I was able to confirm this by building and installing a gem from the master branch, but because the gem hasn't been tagged and pushed to RubyGems, I can't update Gemfile.lock and have to work around this by starting each new workflow with bundle update rbtrace to identify the custom 0.5.2 version that I installed and then reverting Gemfile.lock before committing so that the build doesn't break for others.

Would it be possible for someone to cut a new v0.5.2 release to avoid these workarounds?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions