build(deps): bump juspay/yama from 2.6.0 to 3.0.2 - #45
Conversation
Bumps [juspay/yama](https://github.com/juspay/yama) from 2.6.0 to 3.0.2. - [Release notes](https://github.com/juspay/yama/releases) - [Changelog](https://github.com/juspay/yama/blob/main/CHANGELOG.md) - [Commits](juspay/yama@v2.6.0...v3.0.2) --- updated-dependencies: - dependency-name: juspay/yama dependency-version: 3.0.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
Single Commit Policy — COMPLIANTStatus: 1 commit | Valid format | No merge commits | Ready for merge Commit details
Automated validation — dopamine single-commit enforcement |
|
Follow-up on the This PR's diff (verified at current head - uses: juspay/yama@v2.6.0
+ uses: juspay/yama@v3.0.2But mcpServers:
github:
enabled: true
jira:
enabled: falseThe v3.0.0 release notes (surfaced in this very PR's dependabot description) call this out explicitly under BREAKING CHANGES:
Since this PR bumps the action tag but doesn't migrate the config, the very next PR's "Yama PR Review" run would hit this at config-load time. Looking at how That message reads like a transient infra hiccup — re-running won't fix it, because the actual cause is the config shape, and "Yama PR Review" is a required status check, so this would block merges on every subsequent PR until fixed. Suggest migrating |
|
Chase on the above — reconfirmed live at current head |
|
Superseded by #57. |
1 participant
Bumps juspay/yama from 2.6.0 to 3.0.2.
Release notes
Sourced from juspay/yama's releases.
... (truncated)
Changelog
Sourced from juspay/yama's changelog.
Commits
087e7c6chore(release): 3.0.2 [skip ci]b842f24fix(review): gate-anchored verdicts, posting finalization, no default wall clock7fdacfachore(release): 3.0.1 [skip ci]10116a8fix(config): make ai temperature optional, omit when unsetbb6c205chore(release): 3.0.0 [skip ci]705efe9fix(release): repair GitHub Packages publish and refresh v3 docs53b4a55refactor(v2): config-driven MCP, agentic review harness, and v3 pipelineb89b3aachore(release): 2.7.2 [skip ci]9fa4e96fix(release): run release.yml on Node 24 so npm@latest OIDC install succeedsfe1de54fix(deps): bump@juspay/neurolinkto 10.1.2 for litellm timeout defaultsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)