Skip to main content
Last updated: 20 Feb 2024

Retire a gem

1. Ensure the gem is not used by any apps

Search for references to the gem in our codebase to see if any apps are still using it:


For any repos which are found to have the gem as a dependency, you should confirm that the gem is actually being used and that it’s not simply a leftover artefact that is no longer in use. Check the usage instructions in the gem’s README and then search for the corresponding code in the repo (e.g. use Rack::Logstasher::Logger). Alternatively, find the commits where the gem was added and used, and see if the corresponding code that uses the gem still exists.

If the gem is being used you will either need to replace it with a different gem or your own code before you can archive it.

If removing the gem from an app, take the usual measures of due diligence (e.g. ensuring tests pass, monitoring the release for Sentry errors, etc).

2. Update gem’s README and archive it

When the gem’s repo is ready to be archived, push a commit explaining the reasons for archiving it.


Go into the repository settings in GitHub, and archive the repo.

3. Remove references and update docs

Do a [code search on GitHub][] to find any references to the gem and update or remove them.

Mark the gem as retired in [govuk-developer-docs][].

4. Yank the gem (optional)

Once the gem has been archived you may want to yank it from Rubygems if it was published there. The Rubygems login credentials are under 2ndline/rubygems in Secrets Manager.

You should only really do this if the gem was published in error or contains a security vulnerability. If it’s simply that the gem is no longer maintained, it’s fine to leave it published.