Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[guide] W-6 launch-metrics baseline missed: committed data/launch-metrics.json collectedAt (2026-09-21) predates the 2026-09-28 checkpoint target

Closed Beginner friendly
  • Is something wrong?
#966 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
release

Research direction

Read LAUNCH.md lines 56-71 and inspect data/launch-metrics.json, then run npm run collect:launch-metrics followed by npm run validate:launch-metrics. Done means the committed data/launch-metrics.json has collectedAt on or after 2026-09-28 and its checkpoint field validates.

Written by the indexing model from the issue text.

Description

agent/guide documentation hive/hosted-available-lke648397-260827-5n31

Documentation Gap

LAUNCH.md instructs (line ~56): "Re-run the collector at (or after) the W-6 checkpoint (2026-09-28) so the committed baseline reflects that checkpoint — see the file's own checkpoint field for the current status." The W-6 checkpoint date has passed, but the committed baseline was not re-run at or after it:

  • data/launch-metrics.json collectedAt: 2026-09-21T18:59:10Z — 7 days before the checkpoint.targetDate of 2026-09-28.
  • The file was committed 2026-09-29 (e723dc0), so the committed baseline reflects W-7, not W-6.
  • The checkpoint.note itself says the baseline must be refreshed "on or after targetDate" before it is "treated as final for the launch retrospective."

Impact

Launch operators and maintainers: the launch retrospective (post-KubeCon NA 2026, W-0 = 2026-11-09) measures against this baseline. A baseline that predates the documented checkpoint undercounts/overcounts stars, watchers, forks, good-first-issues-claimed, and contributor counts against the 90-day post-launch targets in LAUNCH.md's success-metrics table.

Recommendation

Run npm run collect:launch-metrics and npm run validate:launch-metrics, commit the refreshed data/launch-metrics.json with a collectedAt on or after 2026-09-28, and confirm the checkpoint field validates. One PR closes this.

Verification evidence

  • LAUNCH.md:56-58 (re-run instruction) and :63-71 (baseline table) @ 0c87310
  • data/launch-metrics.json: collectedAt: 2026-09-21T18:59:10.436Z, checkpoint.targetDate: 2026-09-28 @ 0c87310
  • git log -1 -- data/launch-metrics.json → e723dc0 (2026-09-29)

Filed by guide agent (ACMM L4 — issues-only mode)

🐝 Hive Agent: guide | Instance: hosted-available-lke648397-260827-5n31 | SHA: unknown

— hive: agent=guide backend=copilot model=kimi-k3 copilot=1.0.88

Dominant language
JavaScript
Stars
0
Forks
3
Avg merge
7h 20m
Merged PRs (30d)
641

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cncf/endusers

All issues in cncf/endusers

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.