Posts from Cuenca, Ecuador

New improvements to redirects

As your documentation evolves, content is moved, and pages are renamed, leading to broken links for your users. Redirects allow you to point users to the new location of a page.

We are excited to announce significant improvements to our redirects feature to make them more flexible and powerful.

Read more ...


Introducing support for version-only projects

URLs are an important part of your documentation. Users can infer from the URL if your documentation has or supports multiple versions or translations.

Until now, Read the Docs allowed you to configure your project in two ways:

Read more ...


Security update on incoming webhooks from integrations

Webhooks from integrations (like GitHub) are used to:

Trigger builds when a new commit is pushed to a repository.

Read more ...


Language codes are now normalized

The following language codes are now normalized to be lowercase and use a dash as a separator instead of an underscore:

nb_NO is now nb-no

Read more ...


GitLab service re-connection required

Some months ago GitLab started enforcing an expiration time of two hours for all of their OAuth tokens.

Unfortunately this broke the integration with our application, so your OAuth tokens may have expired. OAuth tokens are used to interact with the GitLab API, for reporting the status of merge requests, creating webhooks, and listing repositories. In order for Read the Docs to have access to new fresh tokens, you need to re-connect your GitLab account. You can do this by:

Read more ...


Deprecation of the git:// protocol on GitHub

Last year, GitHub announced the deprecation of the unsecured Git protocol due to security reasons. This change will be made permanent on March 15, 2022.

At Read the Docs we found around 900 projects using a Git protocol URL (git://github.com/user/project) to clone their projects. To save time for our users, we have migrated those to use the HTTPS cloning URL instead (https://github.com/user/project).

Read more ...


Automation Rules

A time ago we introduced a new feature to help users to automate some tasks on Read the Docs. Automation rules.

If you manage a project with several versions, you may have noticed that Read the Docs doesn’t always activate your new versions 1. If you require to do any action over a new version, you’ll need to log in your Read the Docs account and manually do so.

Read more ...


New Configuration File

We are happy to announce the new version of the Read the Docs configuration file (v2).

If you are a recurrent Read the Docs user, chances are that you’ve configured your projects using a .readthedocs.yml file.

Read more ...