Skip to content

chore: regenerate package-lock.json - #18

Merged
allocsys merged 1 commit into
mainfrom
chore/regenerate-lockfile
Jul 26, 2026
Merged

chore: regenerate package-lock.json#18
allocsys merged 1 commit into
mainfrom
chore/regenerate-lockfile

Conversation

@allocsys

Copy link
Copy Markdown
Owner

Regenerated by the "Generate lockfile" workflow (run #5) on commit ba41aa8, syncing package-lock.json with the current package.json (fixes the @upstash/redis/uncrypto drift that's been forcing CI to fall back from npm ci to npm install).

Opened manually rather than by the workflow itself -- its own PR-creation step failed with GitHub Actions is not permitted to create or approve pull requests, a repo/org-level Actions setting (Settings → Actions → General → "Allow GitHub Actions to create and approve pull requests") that overrides the workflow's own permissions: pull-requests: write. Worth enabling that setting if you want future runs of this workflow to open PRs on their own without manual follow-up.

@vercel

vercel Bot commented Jul 26, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
madmcp Ready Ready Preview, Comment Jul 26, 2026 7:41am

@allocsys
allocsys merged commit 135543f into main Jul 26, 2026
3 checks passed
@allocsys
allocsys deleted the chore/regenerate-lockfile branch July 26, 2026 07:43
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.

1 participant