Skip to content

Commit ca5fc36

Browse files
committed
build: Release version 4.0.0; add a changelog
1 parent d6421dc commit ca5fc36

2 files changed

Lines changed: 43 additions & 1 deletion

File tree

CHANGELOG.rst

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
Changelog
2+
#########
3+
4+
..
5+
All enhancements and patches to codejail will be documented
6+
in this file. It adheres to the structure of https://keepachangelog.com/ ,
7+
but in reStructuredText instead of Markdown (for ease of incorporation into
8+
Sphinx documentation and the PyPI description).
9+
10+
This project adheres to Semantic Versioning (https://semver.org/).
11+
12+
.. There should always be an "Unreleased" section for changes pending release.
13+
14+
Unreleased
15+
**********
16+
17+
*
18+
19+
4.0.0 - 2025-06-13
20+
******************
21+
22+
Changed
23+
=======
24+
25+
* **BREAKING**: Require an explicit opt in to unsafety; defer decision to call
26+
time rather than module load time.
27+
28+
* Calling ``safe_exec`` without having configured the codejail library will
29+
now raise an exception rather than passing execution to ``not_safe_exec``.
30+
(Note: This does not prevent other kinds of dangerous misconfiguration, such
31+
as a bad or missing AppArmor profile.)
32+
* In installations that are intended to always run in safe mode, and have been
33+
properly configured to do so, this should have no effect.
34+
* In installations where codejail sometimes needs to run with no sandboxing
35+
(e.g. in unit tests), developers will need to set
36+
``codejail.safe_exec.ALWAYS_BE_UNSAFE`` to ``True``. This can be set from a
37+
unit test harness, for example.
38+
39+
Added
40+
=====
41+
42+
* Support for Django 5.2

codejail/__init__.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
"""init"""
22

3-
__version__ = '3.5.2'
3+
__version__ = '4.0.0'

0 commit comments

Comments
 (0)