Repository navigation
chore: update tend workflows (0.3.24 → 0.3.25) - #6555
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
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.
Regenerates the Tend workflows for tend 0.3.24 → 0.3.25. The diff only bumps the
max-sixty/tendaction pins and the generated-by header, plus the updated header comment intend-ci-failures.yaml;.config/tend.yamlis unchanged and has no model pins to update.What changes for this repo's bot runs:
main— triage now closes atestsfailure report once it has diagnosed it, andtend-ci-failuresreopens that same report on the lane's next failure instead of filing a new one (Close a CI failure report once diagnosed, and reopen it on the lane's next failure max-sixty/tend#1677). Triage also searches for an existing cause by the full test name and rechecks before filing (fix(triage): search for CI causes by full test name and recheck before filing max-sixty/tend#1673).tend check— a failure a maintainer has reviewed can be accepted with a reason underchecks.acceptedin.config/tend.yaml(Let tend check accept a reviewed failure with a reason from checks.accepted max-sixty/tend#1662). That is one option for the standingimmutable-releasesfailure tracked in tend check: configuration drift on PRQL/prql #6340.setup-runtimeretries the uv download (fix: retry the uv release download in setup-runtime max-sixty/tend#1666).Full upstream diff: max-sixty/tend@0.3.24...0.3.25