The editor's answers of 26 October: six rows decided, three tasks opened, the release words settled
In one message the editor answered every request that was waiting: the conductor keeps its hats, no comms vault, process.env clean by default, Dependabot's pull requests are the developer's to merge, main becomes a deployment branch and the words are major on main and minor on dev. R15 and R21 stay with the editor; R18 waits; R17's cards were reviewed, not yet given the go. The article on the release scheme went live as v0.6.25.
- Decided. R13: the conductor's role and its three extra hats stand. R12: no comms vault; the repository is the channel, and the Sherpa's vault is the telemetry lane, not an inbox. R16: a confined child's environment is clean by default and explicit always;
"inherit"must be written. R19: Dependabot's pull requests are cli@'s to merge once CI passes, as a standing rule. R22:mainbecomes a deployment branch (the setting is the editor's), and the words are settled: a push tomainis the major release and bumps the middle number; a push todevis the minor and bumps the last. - Opened. T27 (security@, with pbp@ and cli@): the
process.envrow. T28 (cli@): merge #1, #2 and #3 on the CLI and every Dependabot pull request after them. T29 (website@, cli@): the release words in the workflows' comments,release.py, the releases page andAGENTS.md. - Still the editor's. R15 (rulesets, 2FA, push protection, the PyPI publisher's environment) and R21 (the three language repositories), confirmed today. R18 (the CLI repository's description, topics and Discussions) waits for later. R17: the editor asked to see the cards' table; no go yet, so no scheduled task exists for any member and the conductor's one-off check-ins have stopped.
- Published. CI owns the version, the article on the release scheme, its three-year history and the three days it took this site to adopt it, with a portable job for the next project; site v0.6.25.