Frappe-bench

Latest version: v5.22.6

Safety actively analyzes 629765 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 11 of 12

5.0

We're moving away from continuous deployment. For production usage, it is recommended to use the PyPI package. Remove the editable install from your system and run a `pip install frappe-bench` instead. All future updates can be handled through pip.


---

So there's been a lot of changes since the last release, about 800 commits in between. Some of the noteworthy changes are mentioned categorically:

Features:

- `bench pip`: utilizes the current Python's environment to update packages
- `bench find`: find benches from the specified path(via DFS)
- cleaner UX: formatted outputs
- executing bench commands in subdirectories

Development:

- Different CI tests for basic and production bench setups and easy install runs
- Cleaner and updated API usages

Other changes:

- fixed `switch-to-branch`
- fixed git depth while `get-app`
- updated cronjob for SSL renewal
- updated bench help commands and docs
- added "rollback" feature in case of failures during `bench init`

Deprecated:
- `update_bench_on_update` from config
- `switch-to-master` command
- `bench shell` command
- Removed `auto_update` from cronjob

---

This release was previously tracked at [bench v5.0](https://github.com/frappe/bench/projects/1)

4.1

Minor fixes and moved to node6.x

4.0

Improvements for frappe/erpnext v7 release

3.1

Compatibility fixes between Celery and RQ configurations

3.0

Deprecated Celery and moved to using Python RQ

If you have a Frappé app with background jobs that are NOT called via scheduler, you need to read [Celery to Python RQ](https://github.com/frappe/frappe/wiki/Celery-to-Python-RQ)

2.1

- Fixes dev installer for Mac OS X
- Permissive sudoers
- Improved release script

Page 11 of 12

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.