chore(deps): align Pack dev dependency updates#72
Merged
Conversation
Signed-off-by: Tapish Khandelwal <tapishkhandelwal13@gmail.com>
This was referenced Jul 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Batch the safe Pack dev-dependency updates that were open as separate Dependabot PRs:
@types/chrome0.0.320->0.2.2@typescript-eslint/eslint-plugin,@typescript-eslint/parser, andtypescript-eslint->8.63.0prettier->3.9.4This intentionally does not update
@types/node; Pack remains on Node 22.Root Cause / Decision Record
@types/node@26PR is not included because Pack runtime and CI are still Node 22.Scope
Pack Workflow Preflight
pnpm workflow:preflightwas run before editing/push, or the skip reason is documented.Sanchika Adoption Gate
@sanchika/*packages or copied Sanchika guidance, I readsanchika/docs/adoption-pack.mdin the coordinated parent worktree.../sanchika,sanchika/packages/*/src, or parent source paths.Not applicable: this PR does not consume Sanchika.
Privacy And Data-Flow Impact
No public behavior changed.
Sensitive Surface Review
Only dev dependencies, lockfile entries, and formatter output changed.
Chrome Web Store Impact
docs/PUBLICATION_READINESS.mdis checked.No Chrome Web Store behavior changed.
Verification
pnpm install --frozen-lockfilepnpm audit --audit-level highpnpm exec wxt preparepnpm exec prettier --check .pnpm exec eslint . --max-warnings 0pnpm exec tsc --noEmitpnpm exec vitest runpnpm exec wxt buildnode scripts/verify-extension-package.mjs .output/chrome-mv3pnpm exec wxt zipnode scripts/verify-extension-zip.mjsnode scripts/write-release-provenance.mjsnode scripts/verify-github-release-assets.mjs --tag <tag> --zip <zip> --checksum <sha256> --provenance <json>when release assets existnode scripts/publish-chrome-web-store.mjs --zip .output/<zip> --provenance .output/pack-release-provenance.v1.json --publisher-id <id> --dry-run truegit diff --checkpnpm review:gate -- --strict-head-review --required-review-author chatgpt-codex-connector --wait-head-review-ms 180000 --allow-missing-head-reviewbefore merge/readiness claim, with missing Codex review recorded as an audit gap if reported:Install was done through
pnpm update -D ..., which refreshedpnpm-lock.yaml. Release-provenance and Chrome Web Store dry-run checks are not applicable because this PR does not publish a release.Review gate result:
review-gate:allowed-missing-head-review; no current-head Codex review was found forc087f05, and the gate passed because missing-head review is explicitly allowed for this lane.Artifact Evidence
.output/complyeazepack-0.3.3-chrome.zip1451c688e0861ad448b1382e96e16b6b0cf3111d9c5fbf2b0d0bca37da8d699ac087f05PR Review Follow-Up
c087f05c087f05c087f05.nvmrc,package.json, CI Node setupc087f05Screenshots
Use synthetic data only.
Not applicable: no UI behavior changed.
DCO
Signed-off-by:trailers.