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
Copy file name to clipboardExpand all lines: RELEASE_NOTES.md
+17-4
Original file line number
Diff line number
Diff line change
@@ -10,15 +10,18 @@
10
10
11
11
### Cookiecutter template
12
12
13
-
All upgrading should be done via the migration script or regenerating the templates.
13
+
* Branch protection rule **Protect version branches** was updated, please re-import it following the [instructions](https://frequenz-floss.github.io/frequenz-repo-config-python/v0.13/user-guide/start-a-new-project/configure-github/#rulesets).
14
+
15
+
> [!IMPORTANT]
16
+
> For **api** projects make sure to require the **Check proto files with protolint** status check too, which is not included by the provided ruleset by default.
17
+
18
+
All other upgrading should be done via the migration script or regenerating the templates.
<!-- Here upgrade steps for cookiecutter specifically -->
24
+
But you might still need to adapt your code.
22
25
23
26
## New Features
24
27
@@ -33,6 +36,16 @@ But you might still need to adapt your code:
33
36
* Major updates and dependencies excluded by the above groups are still managed, but they'll create one PR per dependency, as breakage is expected, so it might need manual intervention.
34
37
* Finally, we group some dependencies that are related to each other, and usually needs to be updated together.
35
38
39
+
- The GitHub workflows is now split into PRs and CI workflows.
40
+
41
+
These new workflows also start using a new reusable `gh-action-nox`, native arm runners and Ubuntu 24.04, as [Ubuntu 20.04 will be removed from GitHub runners by April's 1st][ubuntu-20.04]. Python 3.12 is also added to the test matrix.
42
+
43
+
The PR action is more lightweight, and only tests with one matrix (the most widely used), so PRs can be tested more quickly.
44
+
45
+
The push workflow does a more intense testing with all matrix combinations. This also runs for the merge queue, so before PRs are actually merged the tests will run for the complete matrix.
0 commit comments