1.. _zephyr_release_notes:
2
3Releases
4########
5
6Zephyr project is provided as source code and build scripts for different target
7architectures and configurations, and not as a binary image. Updated versions of
8the Zephyr project are released approximately every four months.
9
10All Zephyr project source code is maintained in a `GitHub repository`_. In order
11to use a released version of the Zephyr project, it is recommended that you use
12:ref:`west` to :ref:`get_the_code` of the release you are interested in.
13
14The technical documentation for current and past releases is available at
15https://docs.zephyrproject.org/ (use the version selector to select your release
16of interest).
17
18.. _zephyr_release_cycle:
19
20Release Life Cycle and Maintenance
21**********************************
22
23Periodic Releases
24=================
25
26The Zephyr project provides periodic releases every 4 months leading to the
27long term support releases approximately every 2 years. Periodic and non-LTS
28releases are maintained with updates, bug fixes and security related updates
29for at least two cycles, meaning that the project supports the most recent two
30releases in addition to the most recent LTS.
31
32Long Term Support and Maintenance
33=================================
34
35A Zephyr :ref:`Long Term Support (LTS) <release_process_lts>` release is
36published every 2 years and is branched and maintained independently from the
37main tree for at least 2.5 years after it was released.
38
39Support and maintenance for an LTS release stops at least half a year
40after the following LTS release is published.
41
42Security Fixes
43==============
44
45Each security issue fixed within Zephyr is backported or submitted to the
46following releases:
47
48- Currently supported Long Term Support (LTS) release.
49
50- The most recent two releases.
51
52For more information, see  :ref:`Security Vulnerability Reporting <reporting>`.
53
54
55Supported Releases
56******************
57
58+------------------------+----------------+---------------+
59| Release                | Release date   | EOL           |
60+========================+================+===============+
61| `Zephyr 4.1.0`_        | 2025-03-07     | 2025-11-14    |
62+------------------------+----------------+---------------+
63| `Zephyr 4.0.0`_        | 2024-11-15     | 2025-07-18    |
64+------------------------+----------------+---------------+
65| `Zephyr 3.7.0 (LTS3)`_ | 2024-07-26     | 2027-01-26    |
66+------------------------+----------------+---------------+
67
68Previous LTS
69************
70
71+-------------------------+---------------+
72| Release                 | EOL           |
73+=========================+===============+
74| `Zephyr 2.7.6 (LTS2)`_  | 2025-01-26    |
75+-------------------------+---------------+
76| `Zephyr 1.14.1 (LTS1)`_ | 2022-01-01    |
77+-------------------------+---------------+
78
79Release Notes
80*************
81
82Release notes contain a list of changes that have been made to the different
83areas of the project during the development cycle of the release.
84Changes that require the user to modify their own application to support the new
85release may be mentioned in the release notes, but the details regarding *what*
86needs to be changed are to be detailed in the release's migration guide.
87
88Updates to the release notes post release cycle is permitted but limited to
89style, typographical fixes and to upmerge the notes from maintenance release
90branches with the sole purpose of keeping the latest documentation consistent
91with the changes in the project.
92
93.. toctree::
94   :maxdepth: 1
95   :glob:
96   :reversed:
97
98   release-notes-3.7
99   release-notes-4.[0-2]
100
101Migration Guides
102****************
103
104Zephyr provides migration guides for all major releases, in order to assist
105users transition from the previous release.
106
107As mentioned in the previous section, changes in the code that require an action
108(i.e. a modification of the source code or configuration files) on the part of
109the user in order to keep the existing behavior of their application belong in
110in the migration guide. This includes:
111
112- Breaking API changes
113- Deprecations
114- Devicetree or Kconfig changes that affect the user (changes to defaults,
115  renames, etc)
116- Treewide changes that have an effect (e.g. changing the include path or
117  defaulting to a different C standard library)
118- Anything else that can affect the compilation or runtime behavior of an
119  existing application
120
121Each entry in the migration guide must include a brief explanation of the change
122as well as refer to the Pull Request that introduced it, in order for the user
123to be able to understand the context of the change.
124
125.. toctree::
126   :maxdepth: 1
127   :glob:
128   :reversed:
129
130   migration-guide-3.[6-7]
131   migration-guide-4.[0-2]
132
133End-of-life Releases
134********************
135
136.. toctree::
137   :hidden:
138   :maxdepth: 1
139
140   eol_releases
141
142Release notes and migration guides for end-of-life releases of Zephyr RTOS can be accessed
143:ref:`here <eol_releases>`.
144
145.. _`GitHub repository`: https://github.com/zephyrproject-rtos/zephyr
146.. _`GitHub tagged releases`: https://github.com/zephyrproject-rtos/zephyr/tags
147.. _`Zephyr 1.14.1 (LTS1)`: https://docs.zephyrproject.org/1.14.1/
148.. _`Zephyr 2.7.6 (LTS2)`: https://docs.zephyrproject.org/2.7.6/
149.. _`Zephyr 3.7.0 (LTS3)`: https://docs.zephyrproject.org/3.7.0/
150.. _`Zephyr 4.0.0`: https://docs.zephyrproject.org/4.0.0/
151.. _`Zephyr 4.1.0`: https://docs.zephyrproject.org/4.1.0/
152