Create a new bundler-audit release then figure out how to get the gem published

[jasnow]

@postmodern - You are the only one person who can publish the bundler-audit gem.
If you can publish the gem (after vetting it) or add another person to the "publish team", that would be great.

One of the @rubysec/maintainers has asked the Rubygems.org team to add him to the publish permission list but they do not have policy to cover this situation.

I will CC the other repo owners @reedloden, @mveytsman, and @phillmv as candidates too.

[jasnow]

Here is a https://rubygems.org/ discussion from 2024: rubygems/rubygems.org#5213

[jasnow]

Created some draft Changelog entries with copilot's help:

• bundler-audit 0.9.3+ ChangeLog entry (short version)
  • https://gist.github.com/jasnow/f5201ae534b2ee7914d9aafaee1daf5b
• bundler-audit 0.9.3+ ChangeLog entry (longer version)
  • https://gist.github.com/jasnow/6da30023f8ca6a7cbc2c7c721165d49c

[jasnow]

Figure last night that we could handle the release and published as two separate tasks.

[simi]

I can prepare release indeed, but I think we do lack permissions to release.

[jasnow]

I can prepare release indeed, but I think we do lack permissions to release.

Once we are ready, then we can ask one of the rubysec owners to try to publish.

[flavorjones]

@jasnow The only human on the planet with privileges is @postmodern, rubygems.org privileges are distinct and separate from github privileges. I have an open thread going with the rubygems.org maintainers on how or whether to grant additional people privileges, please be patient.

[simi]

@jasnow The only human on the planet with privileges is @postmodern, rubygems.org privileges are distinct and separate from github privileges. I have an open thread going with the rubygems.org maintainers on how or whether to grant additional people privileges, please be patient.

Let's sync at #rubysec on Slack @flavorjones. We can meanwhile release on gem.coop namespace.

[jasnow]

@jasnow The only human on the planet with privileges is @postmodern, rubygems.org privileges are distinct

So you are saying that there is only one gem owner set and @postmodern is the
only person who could run the gem owner -a NEWOWNER and assign more gem owners.