Your Package Repo

Package Hosting for RubyGems, npm, and more. Visit or email [email protected] if you have questions.

[Your Package Repo @Gemfury]

A look inside: exploring package content
https://t.co/0DFOUaqhii

[Your Package Repo @Gemfury]

🤔

[Your Package Repo @Gemfury]

Happy 30 years of Ruby! The language, ecosystem, and community have had a lasting influence on how we built @Gemfury. #rubyrelease30th #ruby4

[Your Package Repo @Gemfury]

An AWS incident is causing some issues including our inability to update the status page https://t.co/plpRoGof6G

[Your Package Repo @Gemfury]

Our most scenic stop on the way to #RubyKaigi2025

[Your Package Repo @Gemfury]

@othello We’re on it. Please check your email.

[Your Package Repo @Gemfury]

@george_kettle We suspect an authentication issue here. If Bundler does not auth correctly to Gemfury, it will query your public repo, rather than your private one, resulting in “not found” errors for private gems.

[Your Package Repo @Gemfury]

@Control_Alt_Dev @jarredsumner We’ve done some quick tests and put together an initial guide. Please let us know if it works for you. https://t.co/v7S7ugUl8I

[Your Package Repo @Gemfury]

@galtzo Still under active development, but have been quiet recently due a sizable backend migration. Bundler has seen bugs recently in their marshaling code, which version is manifesting issues for you? Please email us, and about the other issues too - we’ll take a look.

[Your Package Repo @Gemfury]

Gemfury turns 10! https://t.co/C7WKLdPFM7

[Your Package Repo @Gemfury]

@ianelantzy We are fixing this. Incident report coming.

[Your Package Repo @Gemfury]

@venriq We are fixing this. Incident report coming.

[Your Package Repo @Gemfury]

@leopard_me Thanks for catching this. Yes, we misconfigured our nameservers for “https://t.co/9uNFEPGFBi”, but now it is fixed. If you’re still seeing errors, you may need to clear your DNS cache.

[Your Package Repo @Gemfury]

@rhymiz We’ve deployed a bug that rejected packages with larger metadata. This is fixed now.

[Your Package Repo @Gemfury]

@collimarco We do some caching and so does @github. Looks like in this case, the old image is being held by GitHub’s CDN.

[Your Package Repo @Gemfury]

@BrendaS94595953 We’re on it. Please check your email & account.

[Your Package Repo @Gemfury]

@w3guy One of our services failed over, so there was a brief spike in errors. Sorry about that.

[Your Package Repo @Gemfury]

@rauldipeas Hmm. We’ll take a look.

[Your Package Repo @Gemfury]

@rauldipeas @RonoaldoPereira No problem. We just fixed it today.

[Your Package Repo @Gemfury]

@rauldipeas @RonoaldoPereira Thanks for the bug report. We will fix this.

[Your Package Repo @Gemfury]

@jagthedrummer Sorry about that. We have been dealing with scaling issues in the past couple of weeks. We will solve these sporadic errors soon.

[Your Package Repo @Gemfury]

@blaken Sorry about that. We have been dealing with scaling issues in the past couple of weeks. We will solve these sporadic errors soon.