⏫️ Publish an Update?

[zicklag]

I'm using a fork of this crate using a git dependency in a project of mine and I would now like to publish my crate to crates.io. In order to publish my crate I need to have an updated release of the bdf crate. Will you be able to help publish a new version of this crate with a couple PRs of mine, or should I publish a new BDF crate using my fork with a different name to crates.io?

[zicklag]

I'm going to publish my own BDF crate forked from this crate. @meh, if you ever get the chance and don't mind, I would be glad to be a collaborator on this repo so that I could merge PRs and publish updates. I might not have a lot of time, but two maintainers without a lot of time is still better than one. :)

[meh]

Yo, I can make you collaborator, but how do I do that with the crate as well?

[zicklag]

Cool!

You have a few options for how to grant me access to publish the crate:

• You can make me a fellow owner of the crate. This bears a certain risk because I then have just as much permission as you and could then later remove you as an owner. Being that we don't know each-other and just met on GitHub probably not the safest option if you care about owning the crate. ;) You can do that with: cargo owner --add zicklag
• You can grant access to the crate using a GitHub team. When you are in a team with access to a crate you can't remove other owners, so that is safer than making an individual an owner. Because teams are an organization feature in GitHub you would have to either:
  • Create a new organization, create a team in that organization, and add me to the team
  • Just add my organization's team, @katharostech/crates-io-publishers as an owner so that anyone in my organization authorized to publish our crates will be able to publish your crate as well.
    You can add team acces like this: cargo owner --add github:katharostech:crates-io-publishers

[meh]

I'm gonna go with adding the whole organization, you seem like good guys.

But, I'm gonna do it tomorrow because I'm about to sleep, if I do not do it, and it is likely, please just ping me again, hopefully I'll see the message while I'm at my laptop.

[meh]

Wait I lied, my laptop is right here on the bed and turned on, don't ask me how I didn't realize.

[meh]

> cargo owner --add github:katharostech:crates-io-publishers
    Updating crates.io index
error: failed to invite owners to crate bdf: api errors (status 200 OK): could not find the github team katharostech/crates-io-publishers

[zicklag]

One second, I'm looking into it. I just created the team so maybe it hasn't refreshed yet or something.

[zicklag]

OK, I'm going to try to get it working with team ownership on my own crate and I'll let you know when I figure it out. Feel free to go to sleep and get to this tomorrow. :)

[meh]

Aight, good night!

[zicklag]

Ok, I fixed it. You should be able to run the same command again whenever you get the chance and it should work. It was permissions that I had to grant crates.io to read our organization teams.

[zicklag]

OK @meh I pushed a bunch of updates, added tests, fixed issues parsing a couple of fonts I've used in my game engine, and updated the docs slightly.

I think we're ready to publish a new version whenever you get the chance.

[meh]

You should be able to publish now.

[zicklag]

Awesome, thanks!

[zicklag]

Looks like the owners for the crate still haven't been updated. 🤷‍♂️

[msrd0]

Any update on this? It looks like there is still no new version published on crates.io

[tommythorn]

In fact, this crate is now broken, see rust-lang/cargo#14643