Names the statifier_blocks moves past 0.35 in the first-workflow guide - #173
Merged
Merged
Conversation
The first-workflow guide's move history stopped at statifier_blocks 0.35.0 while its pin table names 0.41.0. It now names each move from 0.36.0 to 0.41.0 and what it changed for this recipe: nothing. The card-line, Describe and Map changes reach no call the recipe makes; the declared field types that bind from 0.38.0 admit every config value in the hold pickup document, which the suite's pre-flight checks; the block note from 0.39.0 is absent from that document; the note edit and description region from 0.40.0 are the editor's. Docs only: no Elixir code changes, so there is no gate to run. Refs: se-9lmp
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
docs/guides/first-workflow.md, "Moving an existing host to these pins", narrated the statifier_blocks moves only up to 0.35.0 while its pin table names 0.41.0. The section now ends with one more "later move" paragraph and a bullet per statifier_blocks minor from 0.36.0 to 0.41.0, each saying what the move changed for this recipe: nothing, and why. The persistence half of the history already reached 0.21.0 and is untouched.Review (in-turn, docs only)
I re-read the diff against the bead and checked each claim against its source. The release contents come from statifier_blocks'
docs/upgrading.mdand CHANGELOG on its main. The recipe's calls come fromStatifierExamples.FirstWorkflow.run/1and its private decode, publish and register steps, andStatifierExamples.Publish.check/2. The document's blocks and config keys come frompriv/first_workflow/hold_pickup.json(acore.sequenceholding acore.invokeand acore.wait, nocore.send, nonote). The declared field types ofinvoke_type,assign_to,paramsanddurationcome fromconfig_schema/1in statifier_blocks'StatifierBlocks.Core.InvokeandStatifierBlocks.Core.Waitat v0.41.0. The pre-flight claim comes fromtest/statifier_examples/block_schema_test.exs, whose tests "the pre-flight finds nothing in any palette this app mounts" and "the pre-flight finds nothing in any shipped block document" cover this document. The recipe's own files show no change tied to any of these pin moves ingit logsince the 0.36 move, and CI on main at the 0.41.0 pin is green.Gate
Docs only: no Elixir code changes, so under this repo's CLAUDE.md commit row there is no gate to run. CI runs as usual. No changelog entry: this repo takes none.
Refs: se-9lmp