Skip to content

release-notes.txt: add 2026.01 release notes#22044

Merged
miri64 merged 1 commit intoRIOT-OS:masterfrom
leandrolanzieri:pr/add_release_notes_2026_01
Feb 9, 2026
Merged

release-notes.txt: add 2026.01 release notes#22044
miri64 merged 1 commit intoRIOT-OS:masterfrom
leandrolanzieri:pr/add_release_notes_2026_01

Conversation

@leandrolanzieri
Copy link
Contributor

@leandrolanzieri leandrolanzieri commented Feb 4, 2026

It's release time again 🦫!

We're currently on RC3 of the 2026.01 release (RIOT-OS/Release-Specs#332), with just a few tests left, which means we need to start discussing the release notes. Please let me know if you want to highlight something else that I missed from this cycle, or otherwise adapt the notes.

Thanks!


Depends on #22041

@leandrolanzieri leandrolanzieri added this to the Release 2026.01 milestone Feb 4, 2026
@leandrolanzieri leandrolanzieri added Process: needs backport Integration Process: The PR is required to be backported to a release or feature branch Process: release cycle Integration Process: The PR is connected to the release cycle (e.g. release notes) labels Feb 4, 2026
@github-actions github-actions bot added the Area: doc Area: Documentation label Feb 4, 2026
@crasbe
Copy link
Contributor

crasbe commented Feb 4, 2026

Do you want to wait for #22041?

@crasbe crasbe added CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR CI: skip compile test If set, CI server will run only non-compile jobs, but no compile jobs or their dependent jobs labels Feb 4, 2026
@riot-ci
Copy link

riot-ci commented Feb 4, 2026

Murdock results

✔️ PASSED

0d52939 release-notes.txt: add 2026.01 release notes

Success Failures Total Runtime
1 0 1 01m:12s

Artifacts

@leandrolanzieri
Copy link
Contributor Author

Do you want to wait for #22041?

I wasn't pinged, so I wasn't aware of that PR. Given the associated security issue, it makes sense to have that merged.

Copy link
Member

@AnnsAnns AnnsAnns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Read through it, looked good to me, ty for the release :D (Also added the fix PR to the description for tracking)

@leandrolanzieri leandrolanzieri added the State: waiting for other PR State: The PR requires another PR to be merged first label Feb 5, 2026
Copy link
Contributor

@mguetschow mguetschow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for doing this!

@crasbe crasbe removed the State: waiting for other PR State: The PR requires another PR to be merged first label Feb 7, 2026
@leandrolanzieri
Copy link
Contributor Author

leandrolanzieri commented Feb 9, 2026

I think I've addressed the comments. I also updated the PR list to include #22041

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: doc Area: Documentation CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR CI: skip compile test If set, CI server will run only non-compile jobs, but no compile jobs or their dependent jobs Process: needs backport Integration Process: The PR is required to be backported to a release or feature branch Process: release cycle Integration Process: The PR is connected to the release cycle (e.g. release notes)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants