Skip to content

ci: pin pnpm setup across workflows - #653

Open
ndyugwu wants to merge 1 commit into
accensa:mainfrom
ndyugwu:issue-572-pin-pnpm-workflows
Open

ndyugwu wants to merge 1 commit into
accensa:mainfrom
ndyugwu:issue-572-pin-pnpm-workflows

Conversation

@ndyugwu

@ndyugwu ndyugwu commented Oct 17, 2026 •

Copy link
Copy Markdown

Update all five pnpm-installing jobs in publish.yml, reconcile.yml, and visual-test.yml to use the existing ci.yml pattern: pnpm/action-setup@v4 with pnpm 11.28.5 before setup-node, plus pnpm caching. Add job timeouts: publish build/test 20m, tarball verification 15m, publish 10m, reconciliation 10m; the existing visual job remains 20m. Recent reconciliation runs were 38–57 seconds and visual runs about 90–113 seconds. No tagged publish workflow runs were available to measure, so the release job caps are conservative bounds; the three workflows have triggers that do not run on pull requests, so branch-run links cannot be produced without changing out-of-scope trigger lines.

Checks: targeted Prettier check and git diff --check passed. The full CI workflow runs on this PR.

Closes #572

Summary by CodeRabbit

  • Chores
    • Updated automated build, test, publishing, reconciliation, and visual-test workflows to use a consistent pnpm setup with caching.
    • Added time limits to publishing and reconciliation workflow jobs.

@vercel

vercel Bot commented Oct 17, 2026

Copy link
Copy Markdown

@Cjay-Cyber-2 is attempting to deploy a commit to the ACCENSA Team on Vercel.

A member of the Team first needs to authorize it.

@drips-wave

drips-wave Bot commented Oct 17, 2026

Copy link
Copy Markdown

@ndyugwu Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@mergekeeper

mergekeeper Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

MergeKeeper review

Scope: in scope for linked issue #572.
Verdict: clean

This PR correctly updates the four remaining workflows (publish.yml, reconcile.yml, visual-test.yml) to use pnpm/action-setup@v4 with the pinned version 11.28.5 before actions/setup-node, adds pnpm caching, and introduces necessary timeout-minutes bounds for all affected jobs in accordance with issue #572.

Reviewed commit: aa59468268f037e38539fa98597ebab1c5ed43d8.
CI and merge eligibility are checked separately.

@coderabbitai

coderabbitai Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: ae26b0f3-488a-4767-8b24-0bd6bfea4de8
📥 Commits

Reviewing files that changed from the base of the PR and between e02ecc2 and aa59468.

📒 Files selected for processing: 3
  • .github/workflows/publish.yml
  • .github/workflows/reconcile.yml
  • .github/workflows/visual-test.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The publish, reconcile, and visual-test workflows now set up pnpm 11.28.5 before Node.js and enable pnpm caching. The publish and reconcile jobs also have timeout limits.

Changes: Workflow setup

Layer / File(s) Summary
Standardize package setup and job limits
.github/workflows/publish.yml, .github/workflows/reconcile.yml, .github/workflows/visual-test.yml
The workflows replace global pnpm installation with pnpm/action-setup@v4 before Node.js setup and enable pnpm caching. The publish jobs receive 20-, 15-, and 10-minute timeouts; the reconcile job receives a 10-minute timeout.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Suggested reviewers: seunfunmi-319509

Merge Risk: ⚪ Minimal · up to aa594

Pull-request caches cannot feed the tag-triggered release job, so the alleged release-cache exposure is not introduced. No material merge risk remains beyond routine checks.

Pre-merge checks: Passed 4 · Inconclusive 1

Failed Failed checks: 1 inconclusive

Check name Status Explanation Resolution
Linked Issues check Inconclusive The changed workflows implement the direct coding requirements in #572: all five pnpm installs use pnpm/action-setup@v4 with version: 11.28.5 before actions/setup-node@v4, each setup-node step u… Provide results or a green CI record that covers pnpm lint, pnpm typecheck, pnpm format:check, and pnpm test. No implementation change is indicated by the reviewed workflow diff.
Passed Passed checks: 4 passed
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely summarizes the main change: pinning pnpm setup across the affected CI workflows.
Out of Scope Changes check Passed The diff changes only .github/workflows/publish.yml, .github/workflows/reconcile.yml, and .github/workflows/visual-test.yml. Every change replaces the pnpm installation pattern, adds pnpm cachin…
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Full details: Out of Scope Changes check

Explanation

The diff changes only .github/workflows/publish.yml, .github/workflows/reconcile.yml, and .github/workflows/visual-test.yml. Every change replaces the pnpm installation pattern, adds pnpm caching, or sets the requested timeout. The publish provenance command remains unchanged. The excluded ci.yml, sync.yml, and stale-check.yml files are not modified.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

Full details: Linked Issues check

Explanation

The changed workflows implement the direct coding requirements in #572: all five pnpm installs use pnpm/action-setup@v4 with version: 11.28.5 before actions/setup-node@v4, each setup-node step uses cache: pnpm, and the requested job timeouts are present. The publish command still uses npm publish --provenance. The PR reports Prettier, git diff --check, and a full CI run, but it does not provide results for the issue-requested pnpm lint, pnpm typecheck, pnpm format:check, and pnpm test checks. The available evidence cannot establish completion of those checks. The missing branch-run links are not treated as a coding defect because the workflows lack branch triggers and producing those links would require the out-of-scope trigger changes described in the PR.

Resolution

Provide results or a green CI record that covers pnpm lint, pnpm typecheck, pnpm format:check, and pnpm test. No implementation change is indicated by the reviewed workflow diff.

✨ Finishing Touches: 💡 1
🛠️ Fix failing CI checks: 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@mergekeeper mergekeeper Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Approved

This PR correctly updates the four remaining workflows (publish.yml, reconcile.yml, visual-test.yml) to use pnpm/action-setup@v4 with the pinned version 11.28.5 before actions/setup-node, adds pnpm caching, and introduces necessary timeout-minutes bounds for all affected jobs in accordance with issue #572.

@mergekeeper

mergekeeper Bot commented Oct 17, 2026

Copy link
Copy Markdown

MergeKeeper merge status

Status: blocked
PR state: open
Mergeability: mergeable
Checked commit: aa59468268f037e38539fa98597ebab1c5ed43d8.

Reason:
GitHub pull request merge request failed with 403: Resource not accessible by integration

Next steps:
GitHub rejected this as a permissions/ruleset problem, not a review problem — a maintainer merge override cannot force this through.

  1. Confirm the MergeKeeper GitHub App has Contents: Read & write and Pull requests: Read & write permissions for this repository.
  2. If this repository uses a ruleset, add the MergeKeeper GitHub App as a Bypass actor on it (Settings → Rules → Rulesets → the ruleset → Bypass list) — this is what the "bypass rules" checkbox on GitHub's merge button represents, and MergeKeeper can only do the same once it's listed there.
  3. Retry the merge once either is fixed.

This branch has not been deployed

No deployments
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.

chore: install pnpm the documented way in four workflows

2 participants