You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* updated the logging logic when running retention delete with archiving enabled (#642)
* Corrected version to 0.236.011 (#645)
* v0.237.001 (#649)
* Use Microsoft python base image
* Add python ENV vars
* Add python ENV vars
* Install deps to systme
* Add temp dir to image and pip conf support
* Add custom-ca-certificates dir
* Logo bug fix (#654)
* release note updating for github coplilot
* fixed logo bug issue
* added 2,3,4,5,6,14 days to rentention policy
* added retention policy time updates
---------
Co-authored-by: Ed Clark <clarked@microsoft.com>
Co-authored-by: Bionic711 <13358952+Bionic711@users.noreply.github.com>
After completing a code change (bug fix, new feature, enhancement, or breaking change), always ask the user:
10
+
11
+
**"Would you like me to update the release notes in `docs/explanation/release_notes.md`?"**
12
+
13
+
## If the User Confirms Yes
14
+
15
+
Update the release notes file following these guidelines:
16
+
17
+
### 1. Location
18
+
Release notes are located at: `docs/explanation/release_notes.md`
19
+
20
+
### 2. Version Placement
21
+
- Add new entries under the **current version** from `config.py`
22
+
- If the version has changed, create a new version section at the TOP of the file
23
+
- Format: `### **(vX.XXX.XXX)**`
24
+
25
+
### 3. Entry Categories
26
+
27
+
Organize entries under the appropriate category:
28
+
29
+
#### New Features
30
+
```markdown
31
+
#### New Features
32
+
33
+
***Feature Name**
34
+
* Brief description of what the feature does and its benefits.
35
+
* Additional details about functionality or configuration.
36
+
* (Ref: relevant files, components, or concepts)
37
+
```
38
+
39
+
#### Bug Fixes
40
+
```markdown
41
+
#### Bug Fixes
42
+
43
+
***Fix Name**
44
+
* Description of what was broken and how it was fixed.
45
+
* Impact or affected areas.
46
+
* (Ref: relevant files, functions, or components)
47
+
```
48
+
49
+
#### User Interface Enhancements
50
+
```markdown
51
+
#### User Interface Enhancements
52
+
53
+
***Enhancement Name**
54
+
* Description of UI/UX improvements.
55
+
* (Ref: relevant templates, CSS, or JavaScript files)
56
+
```
57
+
58
+
#### Breaking Changes
59
+
```markdown
60
+
#### Breaking Changes
61
+
62
+
***Change Name**
63
+
* Description of what changed and why.
64
+
***Migration**: Steps users need to take (if any).
65
+
```
66
+
67
+
### 4. Entry Format Guidelines
68
+
69
+
-**Bold the title** of each entry
70
+
- Use bullet points for details
71
+
- Include a `(Ref: ...)` line with relevant file names, functions, or concepts
72
+
- Keep descriptions concise but informative
73
+
- Focus on user-facing impact, not implementation details
74
+
75
+
### 5. Example Entry
76
+
77
+
```markdown
78
+
***Custom Logo Display Fix**
79
+
* Fixed issue where custom logos uploaded via Admin Settings would only display on the admin page but not on other pages (chat, sidebar, landing page).
80
+
* Root cause was overly aggressive sanitization removing logo URLs from public settings.
81
+
* (Ref: logo display, settings sanitization, template conditionals)
82
+
```
83
+
84
+
### 6. Checklist Before Updating
85
+
86
+
-[ ] Confirm the current version in `config.py`
87
+
-[ ] Determine the correct category (New Feature, Bug Fix, Enhancement, Breaking Change)
88
+
-[ ] Write a clear, user-focused description
89
+
-[ ] Include relevant file/component references
90
+
-[ ] Place entry under the correct version section
RUN wget https://www.python.org/ftp/python/${PYTHON_MAJOR_VERSION_ARG}.${PYTHON_MINOR_VERSION_ARG}.${PYTHON_PATCH_VERSION_ARG}/Python-${PYTHON_MAJOR_VERSION_ARG}.${PYTHON_MINOR_VERSION_ARG}.${PYTHON_PATCH_VERSION_ARG}.tgz && \
29
-
tar -xzf Python-${PYTHON_MAJOR_VERSION_ARG}.${PYTHON_MINOR_VERSION_ARG}.${PYTHON_PATCH_VERSION_ARG}.tgz && \
30
-
cd Python-${PYTHON_MAJOR_VERSION_ARG}.${PYTHON_MINOR_VERSION_ARG}.${PYTHON_PATCH_VERSION_ARG} && \
0 commit comments