Infra: pin lycheeverse/lychee-action to v2.9.0 (optional)

オープン
  • 何か問題がありますか？
#618 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
1/5
見積もり時間
1時間未満
初心者へのやさしさ
25/100
issue の種類
リファクタリング
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, yaml
領域
ci-cd

調査の方向性

The workflow call site is .github/workflows/build-docs.yml, in the validate job. Read the lychee step and choose whether to keep the floating @v2 tag or pin it to @v2.9.0; the issue says both currently resolve to the same commit. If you pin it, run the validate job on a PR and confirm the lychee step succeeds and reports the expected version.

索引モデルが issue の本文から書いたものです。

説明

dependencies Infrastructure

Summary

Pin lycheeverse/lychee-action from the floating @v2 to @v2.9.0 (latest release). This is optional. @v2 already resolves to the same commit as @v2.9.0, so this is about making the version explicit, not about picking up a new release.

What changed upstream (v2.8.0 → v2.9.0)

  • Default lychee binary bumped from v0.23.0 to v0.24.2. Upstream lychee 0.24.x changed the archive layout, and the action now detects it automatically.
  • Installs into $RUNNER_TEMP/lychee/bin instead of $HOME.
  • Updated actions/checkout and actions/cache internally.
  • Behavior changes in lychee 0.24.x that affect link checking (per the action's release notes): line and column numbers in reports, text-fragment checking (#:~:text=), sitemap.xml input, JUnit output, and explicit timeout handling.

Impact on this repo

  • Call sites: 1, in .github/workflows/build-docs.yml (the validate job, line 75). It runs on PRs and pushes.
  • The step uses args with --no-progress --scheme https --scheme http --user-agent "...". Those flags are unaffected by the 0.24 changes.
  • Text-fragment checking is new. Any link containing #:~:text= will now be checked against the page content. The earlier search of the repo found none, so this should not cause new failures today.
  • Pinning does not change which lychee version runs. The @v2 tag already resolves to the same commit as v2.9.0.

What to alter when upgrading

Option A (recommended): leave @v2. It already points at v2.9.0 and will track future v2 patches.

Option B: pin to lycheeverse/[email protected] for reproducibility. This means updating the pin manually for each release.

Verification

  1. Run the validate job on a PR.
  2. Confirm the lychee step reports the expected link count and no new failures.
  3. If pinning, confirm the step still resolves lychee v0.24.x in the log.

Risk

Very low. The workflow's behavior is unchanged for existing inputs, and the @v2 tag already resolves to v2.9.0.

主要言語
C#
スター
184
フォーク
48
平均マージ
12分
マージ済み PR（30日）
21

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

CommunityToolkit/Datasync のほかの issue

CommunityToolkit/Datasync の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。