Skip to content

chore(deps): lock file maintenance - #1306

Merged
joryirving merged 1 commit into
mainfrom
renovate/lock-file-maintenance
Oct 19, 2026
Merged

joryirving merged 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@its-miso

@its-miso its-miso Bot commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (in timezone America/Edmonton)

  • Branch creation
    • "before 5am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@its-miso
its-miso Bot requested a review from joryirving as a code owner October 19, 2026 06:21
@its-miso

its-miso Bot commented Oct 19, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code EALLOWREMOTE
npm error Fetching packages of type "remote" have been disabled
npm error Refusing to fetch "https://registry.npmjs.org/@tailwindcss/oxide-wasm32-wasi/-/oxide-wasm32-wasi-4.3.3.tgz"
npm error A complete log of this run can be found in: /tmp/cache/others/npm/_logs/2026-10-19T06_21_40_043Z-debug-0.log

@its-saffron its-saffron Bot 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.

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M3.1-Flash-Preview (anthropic) — primary route · pr-reviewer-action v3.6.0

Partial coverage: required-check coverage is incomplete — this review did not resolve every required check and must not be read as a complete pass.

Findings (1 major)

Severity Location Finding
⚠️ Major Renovate reports that updating `package-lock.json` failed, so this PR does not yet satisfy its stated goal of refreshing all affected lock artifacts.

Request changes: Renovate reports an artifact-update failure for the root package-lock.json, while this PR claims that all lock files were refreshed; retry the artifact update and verify the complete lockfile set before merging.

Claims: violated: 1 of 4. The “all locks refreshed” claim is not satisfied by the one-file diff and is contradicted by the reported artifact failure; latest-version selection (3 items), effective automerge disabling, and immortal-PR behavior remain unverified.

Required checks: Breaking API changes — unresolved because this lockfile-only update has no upstream API-change evidence. Full test suite — unresolved; the site workflow includes npm ci and a production build, but the corpus shows the full checks as pending.

Tool Harness Findings: The harness verified that the changed lockfile retains Astro's zod dependency range, moves duplicate entities/zod entries to the top-level resolution, and updates PostCSS to 8.5.31. The Pages workflow installs this lockfile with Node 24 and runs the site production build. The configured Renovate file contains no automerge setting, but inherited/local effective configuration and closure behavior could not be fully verified.

Unaddressed required checks

The classifier marked these checks as required for this PR's risk profile, but the review does not resolve or disposition them:

  • check for breaking API changes in updated dependencies
  • run full test suite after upgrade

@joryirving
joryirving merged commit f9a381b into main Oct 19, 2026
17 of 18 checks passed
@joryirving
joryirving deleted the renovate/lock-file-maintenance branch October 19, 2026 16:11
@its-miso its-miso Bot mentioned this pull request Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant