chore: update tend workflows - #6265
Merged
Merged
Conversation
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
2 participants
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.
Nightly regeneration of tend's workflow files (
uvx tend@latest init). No version bump — this run stayed on tend 0.1.24.The regen normalizes the
sandbox_setupblock scalar from|to|2in all eighttend-*.yamlfiles, matching the explicit-indentation form the generator already emits for the neighboringprompt: |2. The committed files were lagging because #6251 addedsandbox_setup:to.config/tend.yamland hand-wrote the resulting block into the workflows rather than regenerating them.No behavior change: the block contents are byte-identical, and parsing every changed file before and after with
yaml.safe_loadgives equal documents in all eight cases. This just stops the same diff resurfacing on every future nightly.