Commit 9989be5
committed
docs: mark the 0.12.0 entry as a breaking release
The generated 0.12.0 section listed the work only under Features and Bug
Fixes, with no breaking-changes block, so a reader upgrading from 0.11.x
had nothing telling them a public parameter disappeared.
Add the `⚠ BREAKING CHANGES` section, matching the style the 0.11.0 entry
already uses, and record the migration: `extra_let_bindings` is gone from
`Session.enter_environment`, `Session.exit_environment` and
`Session.run_task`, and step-scope EXPR `let` values now travel through
`resolved_symtab`.
Also annotate the "deliver step-scope let bindings to run_task" feature
entry. Read on its own it advertises `extra_let_bindings` on `run_task`, a
parameter that does not exist in 0.12.0: it was added and removed inside
this same release. The note points at the breaking section instead.
The template does render a breaking section from
`release["elements"]["breaking"]`, but the `BREAKING CHANGE:` footer for
this release sits on a `chore:` commit (f05bf28) and no `chore` entries
reached the rendered output, so nothing was emitted. Worth a follow-up if
we want this to generate on its own next time.
Signed-off-by: David Leong <116610336+leongdl@users.noreply.github.com>1 parent adfb0c2 commit 9989be5
1 file changed
Lines changed: 5 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
4 | 8 | | |
5 | 9 | | |
6 | | - | |
| 10 | + | |
7 | 11 | | |
8 | 12 | | |
9 | 13 | | |
| |||
0 commit comments