Skip to content

build(deps): apply 1ES-compatible Dependabot updates - #70845

Merged
pelikhan merged 1 commit into
mainfrom
pelikhan-cuddly-broccoli
Oct 21, 2026
Merged

pelikhan merged 1 commit into
mainfrom
pelikhan-cuddly-broccoli

Conversation

@pelikhan

Copy link
Copy Markdown
Collaborator

Summary

Apply the two open Dependabot npm updates whose new exact versions and tarballs are available through the Microsoft 1ES public npm feed:

Preserve existing npm registry URLs, overrides, and other dependency versions.

Compatibility evidence

make check-npm-1es passed for all 1,151 exact npm registry versions across five tracked lockfiles. Both affected projects also installed successfully using npm ci through the 1ES feed. The separate Git dependency @actions/github-script is not an npm registry dependency.

Updates left unapplied because their proposed lockfiles require versions unavailable from 1ES (ETARGET):

Dependabot PR Example unavailable dependency
#70608 postcss@8.5.31
#70496 @vitest/mocker@5.0.5
#70495 @astrojs/prism@4.1.0
#70494 @vitest/pretty-format@5.0.5
#70493 @playwright/test@1.64.1
#70492 @astrojs/markdown-satteri@0.4.4
#70489 starlight-changelogs@0.7.1

The Python update #70485 is not covered by the 1ES npm compatibility check and is left unchanged.

Validation

  • Passed: full make check-npm-1es.
  • Passed: make agent-report-progress.
  • Passed: documentation production build and internal-link validation.
  • Passed: setup JavaScript typecheck and session-schema freshness.
  • In progress: broad setup JavaScript suite, excluding integration and live frontmatter API tests.

No original Dependabot PRs have been merged or closed.

Apply Vite 8.3.4 from #70607 and follow-redirects 1.16.1 from #70606. Verify all 1,151 locked npm registry versions through the 1ES public feed; leave updates requiring unavailable feed versions unchanged.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@pelikhan
pelikhan marked this pull request as ready for review October 21, 2026 11:11
Copilot AI max review requested due to automatic review settings October 21, 2026 11:11
@pelikhan
pelikhan merged commit 4ef0301 into main Oct 21, 2026
51 of 55 checks passed
@pelikhan
pelikhan deleted the pelikhan-cuddly-broccoli branch October 21, 2026 11:12
@github-actions

Copy link
Copy Markdown
Contributor

🔬 Test Quality Sentinel is analyzing test quality on this pull request...

@github-actions

Copy link
Copy Markdown
Contributor

🔍 Design Decision Gate 🏗️ is checking for design decision records on this pull request...

@github-actions

Copy link
Copy Markdown
Contributor

✂️ Ponytail Reviewer has started processing this pull request

@github-actions

Copy link
Copy Markdown
Contributor

🧠 Matt Pocock Skills Reviewer is reviewing this pull request using Matt Pocock's engineering skills...

@github-actions

Copy link
Copy Markdown
Contributor

🔎 PR Code Quality Reviewer is reviewing code quality for this pull request...

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.

🟡 Changes recommended

The Vite update leaves its PostCSS override below the newly declared dependency minimum without explicit compatibility validation.

1 open issue
2 files not reviewed
  • actions/setup/js/package-lock.json: Generated file
  • docs/package-lock.json: Generated file
What changed in this PR

Updates gh-aw’s setup JavaScript tooling and documentation dependencies using versions available through the 1ES npm feed.

Changes:

  • Bumps setup Vite from 8.3.1 to 8.3.4.
  • Bumps docs follow-redirects from 1.16.0 to 1.16.1.
File Description
docs/​package-lock.json Locks follow-redirects 1.16.1 and its integrity metadata.
actions/​setup/​js/​package.json Pins Vite to 8.3.4.
actions/​setup/​js/​package-lock.json Updates Vite’s locked version and dependency requirements.

Review effort: Max

"picomatch": "^4.0.7",
"postcss": "^8.5.28",
"rolldown": "~1.2.9",
"postcss": "^8.5.29",
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.

2 participants