Skip to content

chore(deps): bump astro, @astrojs/starlight, astro-mermaid and starlight-llms-txt in /docs#825

Open
dependabot[bot] wants to merge 3 commits intomainfrom
dependabot/npm_and_yarn/docs/multi-7e56a0d552
Open

chore(deps): bump astro, @astrojs/starlight, astro-mermaid and starlight-llms-txt in /docs#825
dependabot[bot] wants to merge 3 commits intomainfrom
dependabot/npm_and_yarn/docs/multi-7e56a0d552

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Apr 21, 2026

Bumps astro, @astrojs/starlight, astro-mermaid and starlight-llms-txt. These dependencies needed to be updated together.
Updates astro from 5.18.1 to 6.1.8

Release notes

Sourced from astro's releases.

astro@6.1.8

Patch Changes

  • #16367 a6866a7 Thanks @​ematipico! - Fixes an issue where build output files could contain special characters (!, ~, {, }) in their names, causing deploy failures on platforms like Netlify.

  • #16381 217c5b3 Thanks @​ematipico! - Slightly improved the performance of the dev server by caching the internal crawling of the dependencies of a project.

  • #16348 7d26cd7 Thanks @​ocavue! - Fixes a bug where emitted assets during a client build would contain always fresh, new hashes in their name. Now the build should be more stable.

  • #16317 d012bfe Thanks @​das-peter! - Fixes a bug where allowedDomains weren't correctly propagated when using the development server.

  • #16379 5a84551 Thanks @​martrapp! - Improves Vue scoped style handling in DEV mode during client router navigation.

  • #16317 d012bfe Thanks @​das-peter! - Adds tests to verify settings are properly propagated when using the development server.

  • #16282 5b0fdaa Thanks @​jmurty! - Fixes build errors on platforms with skew protection enabled (e.g. Vercel, Netlify) for inter-chunk Javascript using dynamic imports

  • Updated dependencies [e0b240e]:

    • @​astrojs/telemetry@​3.3.1

astro@6.1.7

Patch Changes

  • #16027 c62516b Thanks @​fkatsuhiro! - Fixes a bug where remote image dimensions were not validated during static builds on Netlify.

  • #16311 94048f2 Thanks @​Arecsu! - Fixes --port flag being ignored after a Vite-triggered server restart (e.g. when a .env file changes)

  • #16316 0fcd04c Thanks @​ematipico! - Fixes the /_image endpoint accepting an arbitrary f=svg query parameter and serving non-SVG content as image/svg+xml. The endpoint now validates that the source is actually SVG before honoring f=svg, matching the same guard already enforced on the <Image> component path.

astro@6.1.6

Patch Changes

  • #16202 b5c2fba Thanks @​matthewp! - Fixes Actions failing with ActionsWithoutServerOutputError when using output: 'static' with an adapter

  • #16303 b06eabf Thanks @​matthewp! - Improves handling of special characters in inline <script> content

  • #14924 bb4586a Thanks @​aralroca! - Fixes SCSS and CSS module file changes triggering a full page reload instead of hot-updating styles in place during development

astro@6.1.5

Patch Changes

  • #16171 5bcd03c Thanks @​Desel72! - Fixes a build error that occurred when a pre-rendered page used the <Picture> component and another page called render() on content collection entries.

  • #16239 7c65c04 Thanks @​dataCenter430! - Fixes sync content inside <Fragment> not streaming to the browser until all async sibling expressions have resolved.

  • #16242 686c312 Thanks @​martrapp! - Revives UnoCSS in dev mode when used with the client router.

    This change partly reverts #16089, which in hindsight turned out to be too general. Instead of automatically persisting all style sheets, we now do this only for styles from Vue components.

  • #16192 79d86b8 Thanks @​alexanderniebuhr! - Uses today’s date for Cloudflare compatibility_date in astro add cloudflare

... (truncated)

Changelog

Sourced from astro's changelog.

6.1.8

Patch Changes

  • #16367 a6866a7 Thanks @​ematipico! - Fixes an issue where build output files could contain special characters (!, ~, {, }) in their names, causing deploy failures on platforms like Netlify.

  • #16381 217c5b3 Thanks @​ematipico! - Slightly improved the performance of the dev server by caching the internal crawling of the dependencies of a project.

  • #16348 7d26cd7 Thanks @​ocavue! - Fixes a bug where emitted assets during a client build would contain always fresh, new hashes in their name. Now the build should be more stable.

  • #16317 d012bfe Thanks @​das-peter! - Fixes a bug where allowedDomains weren't correctly propagated when using the development server.

  • #16379 5a84551 Thanks @​martrapp! - Improves Vue scoped style handling in DEV mode during client router navigation.

  • #16317 d012bfe Thanks @​das-peter! - Adds tests to verify settings are properly propagated when using the development server.

  • #16282 5b0fdaa Thanks @​jmurty! - Fixes build errors on platforms with skew protection enabled (e.g. Vercel, Netlify) for inter-chunk Javascript using dynamic imports

  • Updated dependencies [e0b240e]:

    • @​astrojs/telemetry@​3.3.1

6.1.7

Patch Changes

  • #16027 c62516b Thanks @​fkatsuhiro! - Fixes a bug where remote image dimensions were not validated during static builds on Netlify.

  • #16311 94048f2 Thanks @​Arecsu! - Fixes --port flag being ignored after a Vite-triggered server restart (e.g. when a .env file changes)

  • #16316 0fcd04c Thanks @​ematipico! - Fixes the /_image endpoint accepting an arbitrary f=svg query parameter and serving non-SVG content as image/svg+xml. The endpoint now validates that the source is actually SVG before honoring f=svg, matching the same guard already enforced on the <Image> component path.

6.1.6

Patch Changes

  • #16202 b5c2fba Thanks @​matthewp! - Fixes Actions failing with ActionsWithoutServerOutputError when using output: 'static' with an adapter

  • #16303 b06eabf Thanks @​matthewp! - Improves handling of special characters in inline <script> content

  • #14924 bb4586a Thanks @​aralroca! - Fixes SCSS and CSS module file changes triggering a full page reload instead of hot-updating styles in place during development

6.1.5

Patch Changes

  • #16171 5bcd03c Thanks @​Desel72! - Fixes a build error that occurred when a pre-rendered page used the <Picture> component and another page called render() on content collection entries.

  • #16239 7c65c04 Thanks @​dataCenter430! - Fixes sync content inside <Fragment> not streaming to the browser until all async sibling expressions have resolved.

  • #16242 686c312 Thanks @​martrapp! - Revives UnoCSS in dev mode when used with the client router.

... (truncated)

Commits

Updates @astrojs/starlight from 0.37.6 to 0.38.3

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.38.3

Patch Changes

@​astrojs/starlight@​0.38.2

Patch Changes

  • #3759 f24ce99 Thanks @​MilesChou! - Fixes an issue where monolingual sites using a region-specific locale (e.g., zh-TW) as the default would incorrectly display base language translations (e.g., zh Simplified Chinese) instead of the region-specific ones (e.g., zh-TW Traditional Chinese).

  • #3768 a4c6c20 Thanks @​delucis! - Improves performance of sidebar generation for sites with very large sidebars

@​astrojs/starlight@​0.38.1

Patch Changes

@​astrojs/starlight@​0.38.0

Minor Changes

  • #3644 0d2e7ed Thanks @​HiDeoo! - Adds support for Astro v6, drops support for Astro v5.

    Upgrade Astro and dependencies

    ⚠️ BREAKING CHANGE: Astro v5 is no longer supported. Make sure you update Astro and any other official integrations at the same time as updating Starlight:

    npx @astrojs/upgrade

    Community Starlight plugins and Astro integrations may also need to be manually updated to work with Astro v6. If you encounter any issues, please reach out to the plugin or integration author to see if it is a known issue or if an updated version is being worked on.

    Update your collections

    ⚠️ BREAKING CHANGE: Drops support for content collections backwards compatibility.

    In Astro 5.x, projects could delay upgrading to the new Content Layer API introduced for content collections because of some existing automatic backwards compatibility that was not previously behind a flag. This meant that it was possible to upgrade from Astro 4 to Astro 5 without updating your content collections, even if you had not enabled the legacy.collections flag. Projects would continue to build, and no errors or warnings would be displayed.

    Astro v6.0 now removes this automatic legacy content collections support, along with the legacy.collections flag.

    If you experience content collections errors after updating to v6, check your project for any removed legacy features that may need updating to the Content Layer API. See the Starlight v0.30.0 upgrade guide for detailed instructions on upgrading legacy collections to the new Content Layer API.

    If you are unable to make any changes to your collections at this time, including Starlight's default docs and i18n collections, you can enable the legacy.collectionsBackwardsCompat flag to upgrade to v6 without updating your collections. This temporary flag preserves some legacy v4 content collections features, and will allow you to keep your collections in their current state until the legacy flag is no longer supported.

  • #3704 375edcc Thanks @​florian-lefebvre! - Fixes autocomplete for components exported from @astrojs/starlight/components/*

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.38.3

Patch Changes

0.38.2

Patch Changes

  • #3759 f24ce99 Thanks @​MilesChou! - Fixes an issue where monolingual sites using a region-specific locale (e.g., zh-TW) as the default would incorrectly display base language translations (e.g., zh Simplified Chinese) instead of the region-specific ones (e.g., zh-TW Traditional Chinese).

  • #3768 a4c6c20 Thanks @​delucis! - Improves performance of sidebar generation for sites with very large sidebars

0.38.1

Patch Changes

0.38.0

Minor Changes

  • #3644 0d2e7ed Thanks @​HiDeoo! - Adds support for Astro v6, drops support for Astro v5.

    Upgrade Astro and dependencies

    ⚠️ BREAKING CHANGE: Astro v5 is no longer supported. Make sure you update Astro and any other official integrations at the same time as updating Starlight:

    npx @astrojs/upgrade

    Community Starlight plugins and Astro integrations may also need to be manually updated to work with Astro v6. If you encounter any issues, please reach out to the plugin or integration author to see if it is a known issue or if an updated version is being worked on.

    Update your collections

    ⚠️ BREAKING CHANGE: Drops support for content collections backwards compatibility.

    In Astro 5.x, projects could delay upgrading to the new Content Layer API introduced for content collections because of some existing automatic backwards compatibility that was not previously behind a flag. This meant that it was possible to upgrade from Astro 4 to Astro 5 without updating your content collections, even if you had not enabled the legacy.collections flag. Projects would continue to build, and no errors or warnings would be displayed.

    Astro v6.0 now removes this automatic legacy content collections support, along with the legacy.collections flag.

    If you experience content collections errors after updating to v6, check your project for any removed legacy features that may need updating to the Content Layer API. See the Starlight v0.30.0 upgrade guide for detailed instructions on upgrading legacy collections to the new Content Layer API.

... (truncated)

Commits

Updates astro-mermaid from 1.3.1 to 1.4.0

Release notes

Sourced from astro-mermaid's releases.

v1.4.0

What's Changed

  • chore: bump version to 1.4.0 (#44)
  • Chore: support Astro 6.x and above in peerDependencies (#42)
  • feat: add enableLog option to control client-side logging (#38)
  • Update README.md
  • Update demo dependency to 1.3.1

Full Changelog: joesaby/astro-mermaid@v1.3.1...v1.4.0

Commits
  • ebe84bc chore: bump version to 1.4.0 (#44)
  • 1623261 Chore: support Astro 6.x and above in peerDependencies (#42)
  • 50bb768 feat: add enableLog option to control client-side logging (#38)
  • d3b1b07 Update README.md
  • 88e6ea9 Update demo dependency to 1.3.1
  • See full diff in compare view

Updates starlight-llms-txt from 0.7.0 to 0.8.1

Release notes

Sourced from starlight-llms-txt's releases.

starlight-llms-txt@0.8.1

Patch Changes

  • 29e5efb Thanks @​mvanhorn! - Strips HTML comments from llms.txt files. <!-- ... --> style comments in .md files are no longer emitted in the generated files.

starlight-llms-txt@0.8.0

Minor Changes

  • #80 dea7b22 Thanks @​nonoakij! - Adds support for Astro v6 and Starlight v0.38, drops support for lower versions.
Changelog

Sourced from starlight-llms-txt's changelog.

0.8.1

Patch Changes

  • 29e5efb Thanks @​mvanhorn! - Strips HTML comments from llms.txt files. <!-- ... --> style comments in .md files are no longer emitted in the generated files.

0.8.0

Minor Changes

  • #80 dea7b22 Thanks @​nonoakij! - Adds support for Astro v6 and Starlight v0.38, drops support for lower versions.
Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
chore(deps): bump astro, @astrojs/starlight, astro-mermaid and starli…
da97499 
…ght-llms-txt

Bumps [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro), [@astrojs/starlight](https://github.com/withastro/starlight/tree/HEAD/packages/starlight), [astro-mermaid](https://github.com/joesaby/astro-mermaid) and [starlight-llms-txt](https://github.com/delucis/starlight-llms-txt/tree/HEAD/packages/starlight-llms-txt). These dependencies needed to be updated together.

Updates `astro` from 5.18.1 to 6.1.8
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/astro@6.1.8/packages/astro)

Updates `@astrojs/starlight` from 0.37.6 to 0.38.3
- [Release notes](https://github.com/withastro/starlight/releases)
- [Changelog](https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md)
- [Commits](https://github.com/withastro/starlight/commits/@astrojs/starlight@0.38.3/packages/starlight)

Updates `astro-mermaid` from 1.3.1 to 1.4.0
- [Release notes](https://github.com/joesaby/astro-mermaid/releases)
- [Commits](joesaby/astro-mermaid@v1.3.1...v1.4.0)

Updates `starlight-llms-txt` from 0.7.0 to 0.8.1
- [Release notes](https://github.com/delucis/starlight-llms-txt/releases)
- [Changelog](https://github.com/delucis/starlight-llms-txt/blob/main/packages/starlight-llms-txt/CHANGELOG.md)
- [Commits](https://github.com/delucis/starlight-llms-txt/commits/starlight-llms-txt@0.8.1/packages/starlight-llms-txt)

---
updated-dependencies:
- dependency-name: astro
  dependency-version: 6.1.8
  dependency-type: direct:production
- dependency-name: "@astrojs/starlight"
  dependency-version: 0.38.3
  dependency-type: direct:production
- dependency-name: astro-mermaid
  dependency-version: 1.4.0
  dependency-type: direct:production
- dependency-name: starlight-llms-txt
  dependency-version: 0.8.1
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Apr 21, 2026
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Apr 21, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 22, 2026

APM Review Panel Verdict

Disposition: REQUEST_CHANGES

PR: chore(deps): bump astro, @astrojs/starlight, astro-mermaid and starlight-llms-txt in /docs
Author: dependabot[bot] | Scope: docs/package.json + docs/package-lock.json only
Key version changes: astro 5.18.1 -> 6.1.8 (MAJOR), @astrojs/starlight 0.37.6 -> 0.38.3, astro-mermaid ^1.3.1 -> ^1.4.0, starlight-llms-txt ^0.7.0 -> ^0.8.1

Per-persona findings

Python Architect: No Python source changes. No APM CLI code, no module structure, no design patterns affected. This PR is entirely within the Node.js docs toolchain (docs/). Not in scope for architectural review. No concerns.

CLI Logging Expert: No changes to CommandLogger, _rich_* helpers, DiagnosticCollector, STATUS_SYMBOLS, or any CLI output path. This PR does not touch APM's output layer. No concerns.

DevX UX Expert: The docs site (Astro + Starlight) is the user-facing documentation funnel -- the primary conversion surface for new contributors and enterprise evaluators. The astro 5 -> 6 jump is a major semver boundary. Astro v6 introduced breaking changes (config API, adapter contracts, server output mode). The Deploy Docs CI workflow is currently failing (conclusion: failure, run 24753879971). Until the docs build passes, the docs site cannot be deployed, which degrades the first-run user experience and the community landing page. The starlight-llms-txt ^0.8.1 bump is a small positive -- it likely improves LLM agent discoverability via the generated LLMs.txt artifact. However, no docs benefit justifies merging a broken build. The astro-mermaid update (^1.4.0) also needs validation since APM's how-it-works.md relies on mermaid diagrams for the system mental model.

Supply Chain Security Expert: Scope is correctly limited to the docs Node.js project. The apm.lock.yaml, uv.lock, and all Python APM supply chain surfaces are completely unaffected. Dependabot is a trusted update source and the package-lock.json churn (-986 / +502 lines) is expected for an astro major version upgrade (new transitive deps, dropped deps, version range resolutions). No path traversal, no credential surface, no token scoping change. Threat model rating: low for the APM tool itself; the docs site carries no secrets or privileged access. The one procedural note: lockfile churn of this magnitude should be validated by a passing build before merge -- which is currently blocked. No security blocker beyond the failed CI.

Auth Expert: No authentication code changes. AuthResolver, token management, credential resolution flows, and remote host auth are entirely unaffected. No concerns.

OSS Growth Hacker: Keeping docs tooling current is a hygiene signal for community trust -- stale dependencies read as an abandoned project. The starlight-llms-txt ^0.8.1 update is directly aligned with APM's AI-native positioning: a better-generated LLMs.txt means AI coding agents (Copilot, Cursor, Claude) are more likely to surface APM correctly. However, all of this growth value is zero if the docs build is broken and the site fails to deploy. The priority is: fix the build, then capture the growth upside. Side-channel to CEO: the starlight-llms-txt improvements may be worth a mention in release notes once it lands cleanly, as an AI-discoverability signal to the community.

CEO arbitration

This is a routine dependabot docs-tooling update that hits a real blocker: the astro 5 -> 6 major version upgrade is breaking the Deploy Docs CI workflow. There is no strategic disagreement among the panel -- all specialists agree the scope is narrow (docs only, no APM Python surface), the intent is correct (stay current on tooling), but the merge must wait for the build to pass. The Node.js 20 deprecation warning surfaced in the annotations is a separate but adjacent concern (actions/checkout@v4, actions/setup-node@v4 will need Node.js 24 variants by June 2026) that maintainers should track but is not a blocker for this PR. The strategic call: hold at REQUEST_CHANGES until CI is green. If the astro v6 migration requires config changes beyond a lockfile bump, dependabot may need manual assist from a maintainer.

Required actions before merge

  1. Fix the docs build: The Deploy Docs workflow is failing (run 24753879971). Astro v6 likely requires config updates (e.g., astro.config.mjs, adapter contracts, or deprecated API usage). Check the Astro v6 migration guide at (docs.astro.build/redacted) and apply any required changes to docs/astro.config.mjs or related config files.
  2. Verify mermaid diagrams render: After fixing the build, confirm that astro-mermaid ^1.4.0 still renders the mermaid diagrams in docs/src/content/docs/introduction/how-it-works.md correctly (the system mental model diagram is a key UX artifact).

Optional follow-ups

  • Track the Node.js 20 deprecation warning: actions/checkout@v4 and actions/setup-node@v4 will need Node.js 24-compatible versions before September 2026. This can be a separate chore PR.
  • Consider noting the starlight-llms-txt improvement in CHANGELOG.md under [Unreleased] once merged, as an AI-discoverability enhancement.

Generated by PR Review Panel for issue #825 · ● 797.3K · ◷

@danielmeppiel danielmeppiel mentioned this pull request Apr 23, 2026
Merged
danielmeppiel added a commit that referenced this pull request Apr 23, 2026
@danielmeppiel
ci: add merge-gate orchestrator to harden against dropped pull_reques…
9d2d0e6 
…t webhooks (#865)

* ci: add merge-gate orchestrator (shadow) + stuck-PR watchdog

PR #856 surfaced a structural CI fragility: required status checks are
satisfied by two independent webhook channels (pull_request emits
'Build & Test (Linux)', pull_request_target emits the four Tier 2
stubs). When the pull_request delivery is dropped, 4/5 stubs go green
and the 5th hangs in 'Expected -- Waiting' forever -- ambiguous yellow
indistinguishable from a slow build. Recovery is folklore.

This PR ships two safety nets in shadow mode:

* .github/workflows/merge-gate.yml + scripts/ci/merge_gate_wait.sh
  Single orchestrator that polls the Checks API for 'Build & Test
  (Linux)' on the PR head SHA and aggregates into one verdict. Triggers
  on BOTH pull_request and pull_request_target so a single dropped
  delivery is recoverable; concurrency dedupes. Times out cleanly with
  a clear error message if Tier 1 never dispatched -- turning the
  invisible failure into a loud red check. NOT YET REQUIRED -- shadow
  observation first, ruleset flip after merge.

* .github/workflows/watchdog-stuck-prs.yml + scripts/ci/watchdog_scan.sh
  Cron every 15 min. For open non-draft PRs with no ci.yml run on the
  head SHA AND non-paths-ignored files, posts one recovery comment.
  Backstop for any required check that stops dispatching.

Tested live (dry-run) against microsoft/apm: watchdog correctly
distinguishes stuck PRs (#853, #409) from docs-only PRs (#864, #461,
#825). Both scripts shellcheck-clean. merge_gate_wait.sh tested
end-to-end against PR #856 head SHA (success path, exit 0) and a
non-existent SHA (timeout path, exit 2 with clear error annotation).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* ci(merge-gate): handle self-bootstrap and use checkout on pull_request

Two fixes for the script-fetch step:

1. On 'pull_request' the runner has no secrets and a read-only token, so
   actions/checkout of PR head is safe -- use it for simplicity. We only
   need API-fetch under 'pull_request_target' where checkout would be a
   security risk.
2. On 'pull_request_target', when the script does not yet exist on base
   (i.e. THIS PR is the one adding it), curl returns 404 and we degrade
   to a self-bootstrap no-op pass instead of failing. Once the script
   lands on main, the gate becomes real.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* ci: address Copilot review feedback on PR #865

- merge_gate_wait.sh: use $EXPECTED_CHECK in failure annotation instead
  of hardcoded 'Build & Test (Linux)' so the orchestrator stays generic.
- merge-gate.yml: add curl --retry/--max-time on the script bootstrap
  fetch so a transient GitHub API blip does not redden the gate.
- watchdog_scan.sh: fail loudly with stderr capture if 'gh pr list'
  errors out, instead of silently treating it as zero PRs (which would
  hide auth regressions or rate limiting).
- watchdog_scan.sh: paginate the changed-files API call so PRs touching
  >100 files cannot be misclassified as docs-only and skipped.
- CHANGELOG: append (#865) to follow the repo convention.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* ci: drop watchdog -- gate's dual-trigger redundancy is sufficient

The watchdog (cron every 15min, posts recovery comments on stuck PRs)
was originally justified for the shadow-mode transition window. Since
we are flipping to required immediately after this PR merges, that
justification disappears.

The merge-gate workflow already triggers on both 'pull_request' and
'pull_request_target' with concurrency dedup, so a single dropped
webhook still fires the gate. The watchdog only added value for the
double-drop case (both webhook channels fail for the same PR), which
is vanishingly rare. We can add it back later if we ever observe one.

Removes:
- .github/workflows/watchdog-stuck-prs.yml
- .github/scripts/ci/watchdog_scan.sh

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@danielmeppiel danielmeppiel Awaiting requested review from danielmeppiel danielmeppiel is a code owner

@sergio-sisternes-epam sergio-sisternes-epam Awaiting requested review from sergio-sisternes-epam sergio-sisternes-epam is a code owner

At least 0 approving reviews are required to merge this pull request.

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@danielmeppiel