Skip to content

fix(plugins): bump capabilities plugins off orphaned libs revision#22711

Closed
nadahalli wants to merge 1 commit into
developfrom
tejaswi/bump-capabilities-plugins-fix
Closed

fix(plugins): bump capabilities plugins off orphaned libs revision#22711
nadahalli wants to merge 1 commit into
developfrom
tejaswi/bump-capabilities-plugins-fix

Conversation

@nadahalli

Copy link
Copy Markdown
Contributor

The capabilities plugins were pinned at 9dd7b288 (#22686). Its
chain_capabilities/* (and cron/consensus/http_*/readcontract/
workflowevent) modules require
github.com/smartcontractkit/capabilities/libs@...c4b42d8c0edf, a revision
that was force-pushed out of the capabilities repo and no longer exists.
So make install-plugins-* fails on every fresh chainlink image build
with "unknown revision c4b42d8c0edf".

Builds that ran before the force-push are stale-green (e.g. #22687's
image build completed 2026-05-29, merged June 1), so develop currently
has no passing image build despite the recent merges.

Bump all nine capabilities module gitRefs from 9dd7b288 to 3fad562d
(current capabilities main), whose transitive libs/common references
resolve to existing commits (verified for evm/solana/consensus/http_trigger/cron).

Unblocks the chainlink image build (and the ETH Smoke / Integration /
CCIP smoke jobs that gate on it) for all PRs.

The capabilities plugins were pinned at 9dd7b288 (#22686), whose
chain_capabilities/* and other modules require
github.com/smartcontractkit/capabilities/libs@...c4b42d8c0edf. That
libs revision was force-pushed out of the capabilities repo and no
longer exists, so `make install-plugins-*` fails for every fresh
chainlink image build with "unknown revision c4b42d8c0edf". Builds
that ran before the force-push are stale-green.

Bump all capabilities module gitRefs to 3fad562d (current capabilities
main), whose transitive libs/common references resolve to existing
commits.
@nadahalli nadahalli requested review from a team as code owners June 2, 2026 12:29
Copilot AI review requested due to automatic review settings June 2, 2026 12:29

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Bumps all nine capability plugin gitRefs from the orphaned 9dd7b288 commit to 3fad562d (current capabilities main) so that make install-plugins-* can resolve the transitive capabilities/libs dependency and unblock chainlink image builds.

Changes:

  • Update gitRef across all nine capability plugin entries (cron, readcontract, consensus, workflowevent, httpaction, httptrigger, evm, solana, aptos) to 3fad562d65996bf447372023b5123c0c6e8850c7.

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

@cl-sonarqube-production

Copy link
Copy Markdown

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@trunk-io

trunk-io Bot commented Jun 2, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

@nadahalli

Copy link
Copy Markdown
Contributor Author

Closing as superseded. develop has since bumped the capabilities plugins off the orphaned 9dd7b288 / libs@c4b42d8c0edf pin (plugins.private.yaml now references 3fad562d and other current capabilities commits, and 9dd7b288 is gone), so this one-commit fix is no longer needed. The broader prevention (a check that intra-repo capabilities pins are reachable from the default branch) is proposed separately in smartcontractkit/capabilities#630.

@nadahalli nadahalli closed this Jun 8, 2026
@nadahalli nadahalli deleted the tejaswi/bump-capabilities-plugins-fix branch June 8, 2026 13:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants