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
summary: fix remaining scheduler race conditions and add warning when tasks are not ran in time
3
+
4
+
The mechanism for checking if tasks are not ran in time is very simple but that also means the scheduler can only know if a task has not been called when the waiting time runs out for the second time.
5
+
This means you will know if you're too slow to execute the task in less than 2x its period but not if you're between 1 and 2x its period.
Treat [`docs/releases.md`](docs/releases.md) as the source of truth for the release flow.
6
+
7
+
- For a normal PR into `development` that changes ST-LIB, add exactly one new file under [`.changesets`](.changesets).
8
+
- Use [`.changesets/README.md`](.changesets/README.md) and [`.changesets/TEMPLATE.md`](.changesets/TEMPLATE.md) for the exact format.
9
+
- Changesets must follow this shape:
10
+
11
+
```text
12
+
release: patch
13
+
summary: Short user-visible summary in one line
14
+
15
+
Optional extra context in markdown.
16
+
```
17
+
18
+
- Choose `release:` like this:
19
+
-`major` for breaking API or contract changes.
20
+
-`minor` for backwards-compatible features.
21
+
-`patch` for backwards-compatible fixes.
22
+
-`none` only for internal, docs, or CI changes that should appear in release notes without bumping the version by themselves.
23
+
- If the change affects public behavior, API, contracts, or shipped functionality, do not use `none`.
24
+
- Do not manually bump [`VERSION`](VERSION) or edit [`CHANGELOG.md`](CHANGELOG.md) for normal feature or fix work. Release automation updates them on `release/next`.
25
+
- Expect CI to validate the changeset, roll pending changesets into `release/next`, archive processed files, tag `vX.Y.Z`, and publish the GitHub Release after the `release/next` PR merges.
0 commit comments