Skip to content

[pull] develop from freqtrade:develop #1586

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.

Sign up for GitHub

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

Merged
pull merged 2 commits into from
Dec 30, 2025
+9 −10
Merged

[pull] develop from freqtrade:develop #1586

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
31269c7
docs: Update docs date to 2025
xmatthias Dec 30, 2025
70834b6
chore: update release template structure
xmatthias Dec 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions docs/developer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -432,7 +432,6 @@ freqtrade download-data --timerange 20250625-20250801 --config tests/testdata/co
freqtrade backtesting --config tests/testdata/config.tests.usdt.json -s SampleStrategy --userdir user_data_bttest/ --cache none --timerange 20250701-20250801
```


## Continuous integration

This documents some decisions taken for the CI Pipeline.
Expand Down Expand Up @@ -464,10 +463,10 @@ git checkout -b new_release <commitid>
Determine if crucial bugfixes have been made between this commit and the current state, and eventually cherry-pick these.

* Merge the release branch (stable) into this branch.
* Edit `freqtrade/__init__.py` and add the version matching the current date (for example `2019.7` for July 2019). Minor versions can be `2019.7.1` should we need to do a second release that month. Version numbers must follow allowed versions from PEP0440 to avoid failures pushing to pypi.
* Edit `freqtrade/__init__.py` and add the version matching the current date (for example `2025.7` for July 2025). Minor versions can be `2025.7.1` should we need to do a second release that month. Version numbers must follow allowed versions from PEP0440 to avoid failures pushing to pypi.
* Commit this part.
* Push that branch to the remote and create a PR against the **stable branch**.
* Update develop version to next version following the pattern `2019.8-dev`.
* Update develop version to next version following the pattern `2025.8-dev`.

### Create changelog from git commits

Expand Down
14 changes: 7 additions & 7 deletions docs/includes/release_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,28 +1,28 @@
## Highlighted changes
# Highlighted changes

- ...

### How to update
## How to update

As always, you can update your bot using one of the following commands:

#### docker-compose
### docker-compose

```bash
docker-compose pull
docker-compose up -d
```

#### Installation via setup script
### Installation via setup script

```
``` bash
# Deactivate venv and run
./setup.sh --update
```

#### Plain native installation
### Plain native installation

```
``` bash
git pull
pip install -U -r requirements.txt
```
Expand Down
Loading