-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Post: deprecate config files without sphinx or mkdocs configuration #342
Open
stsewd
wants to merge
3
commits into
main
Choose a base branch
from
deprecate-conf-file
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Binary file added
BIN
+43.2 KB
content/images/deprecated-config-file-without-sphinx-or-mkdocs-config.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
47 changes: 47 additions & 0 deletions
47
content/posts/deprecate-config-files-without-sphinx-or-mkdocs-config.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
title: Deprecation of projects using Sphinx or MkDocs without an explicit configuration file | ||
date: December 16, 2024 | ||
description: Announcing the deprecation of projects using Sphinx or MkDocs without an explicit configuration in their configuration file. | ||
category: Changelog | ||
tags: deprecation, configuration-file | ||
authors: Santos Gallegos | ||
status: published | ||
image: /images/deprecated-config-file-without-sphinx-or-mkdocs-config.jpg | ||
image_credit: Photo by <a href="https://unsplash.com/@jernejgraj?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Jernej Graj</a> on <a href="https://unsplash.com/photos/photo-of-seashore-during-golden-hour-n44KHcbp1_E?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Unsplash</a> | ||
|
||
We are announcing the deprecation of projects using Sphinx or MkDocs without an explicit configuration in their `.readthedocs.yaml` configuration file. | ||
|
||
If you are using Sphinx or MkDocs in your project, | ||
and your `.readthedocs.yaml` configuration file doesn't contain a `sphinx.configuration` or `mkdocs.configuration` key, | ||
make sure to add it. For example, for a Sphinx project, your configuration file should look like this: | ||
|
||
```yaml | ||
version: 2 | ||
sphinx: | ||
# Path to your Sphinx configuration file. | ||
configuration: docs/conf.py | ||
``` | ||
|
||
For a MkDocs project, your configuration file should look like this: | ||
|
||
```yaml | ||
version: 2 | ||
mkdocs: | ||
# Path to your MkDocs configuration file. | ||
configuration: mkdocs.yml | ||
``` | ||
|
||
We used to automatically try to find the configuration file for your project, | ||
but in order to make builds more explicit and predictable, we are deprecating this behavior. | ||
This will also allows us to better support projects that don't use Sphinx or MkDocs in the near future. | ||
|
||
If you are using the `build.commands` feature, you don't need to make any changes, | ||
as the `sphinx` and `mkdocs` options are not required when using `build.commands`. | ||
|
||
Deprecation timeline | ||
-------------------- | ||
|
||
We will disallow building projects using Sphinx or MkDocs without an explicit Sphinx or MkDocs configuration in their configuration file on the following dates: | ||
|
||
- **Monday, January 6, 2025**: Temporarily disallow building projects for 12 hours, from 00:01 PST to 11:59 PST. | ||
- **Monday, January 20, 2025**:Temporarily disallow building projects for 24 hours, from 00:01 PST to 23:59 PST. | ||
- **Monday, February 3, 2025**: Permanently disallow building projects. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd move faster here. This deprecation is very small and it's pretty easy to adapt those YAML files. That will allow us to deploy
build.jobs.build.html
quicker and support workflows people have been trying to run on Read the Docs and they are currently using hacky approaches.