8000 AGENTS.md: the checker rejects SOURCE_DATE_EPOCH=0 re-sets, not every re-set by bryan-minimal · Pull Request #867 · gominimal/pkgs · GitHub
[go: up one dir, main page]

Skip to content

AGENTS.md: the checker rejects SOURCE_DATE_EPOCH=0 re-sets, not every re-set - #867

Merged
bryan-minimal merged 1 commit into
mainfrom
docs/source-date-epoch-rule
Oct 20, 2026
Merged

bryan-minimal merged 1 commit into
mainfrom
docs/source-date-epoch-rule

Conversation

@bryan-minimal
@bryan-minimal bryan-minimal commented Oct 13, 2026 •
Copy link
Copy Markdown
Member

AGENTS.md (CLAUDE.md is a symlink to it) says the checker rejects setting SOURCE_DATE_EPOCH or PYTHONHASHSEED again. The rule in minimal/crates/check/src/lib.rs only matches setting either to 0. A non-zero override passes, which is how all 17 openjdk rungs in #775 carried export SOURCE_DATE_EPOCH=315532802 through minimal-check (found by @norrietaylor's review).

This states the rule as it is, and adds the guidance #775 now follows: give a tool that can't use epoch 0 its date through its own option (--with-source-date for JDK 15+, SH_DATE for nspr) rather than re-exporting the variable.

Docs only.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Clarified reproducibility guidance: the sandbox sets SOURCE_DATE_EPOCH and PYTHONHASHSEED to 0, and the checker rejects setting them to 0 again.
    • Added guidance to use a tool-specific date option when epoch 0 is unsupported, rather than overriding the shared build setting.

It rejects re-setting it to 0, not any re-set; a non-zero override passes,
which is how the openjdk rungs (#775) carried one. Point at the per-tool
option instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bryan-minimal
bryan-minimal requested a review from a team as a code owner October 13, 2026 16:34
@coderabbitai
coderabbitai Bot commented Oct 13, 2026 •
Copy link
Copy Markdown
Contributor

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Repository: gominimal/pkgs/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: 6cc9d11e-3667-4d62-b43c-19542f9c2b4b
📥 Commits

Reviewing files that changed from the base of the PR and between 673744d and 03bd5d5.

📒 Files selected for processing (1)
  • AGENTS.md

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

📝 Walkthrough

The reproducibility guidance now documents sandbox-provided environment variables, checker behavior, and date options for tools that cannot use epoch 0.

Changes: Reproducibility guidance

Layer / File(s) Summary
Document reproducibility variables and date options
AGENTS.md
The instructions state that the checker rejects resetting either sandbox-provided variable to 0. They direct tools that cannot use epoch 0 to use their own date option and note that a non-zero SOURCE_DATE_EPOCH override affects every tool in the build.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Suggested reviewers: norrietaylor

Merge Risk: ⚪ Minimal · up to 03bd5

The guidance directs maintainers toward tool-specific date options. No actionable issue is established that should block merging.

Pre-merge checks · Passed 5
Passed Passed checks (5 passed)
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly describes the primary documentation change: the checker rejects re-s 8000 etting SOURCE_DATE_EPOCH to 0, not every re-set. It is specific and related to the pull request, although it does …
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@norrietaylor norrietaylor left a comment
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. It's consistent with practice on main: microvm-rootfs's ${SOURCE_DATE_EPOCH:-0} passes the check, and openjdk uses --with-source-date instead of re-exporting.

Optional nits:

  • "rejects setting either to 0 again" slightly overstates it, since only a literal =0 is caught.
  • The caveat about non-zero overrides should cover PYTHONHASHSEED too.

Generated by Claude Code

@bryan-minimal
bryan-minimal added this pull request to the merge queue Oct 20, 2026
@bryan-minimal
bryan-minimal removed this pull request from the merge queue due to a manual request Oct 20, 2026
@bryan-minimal
bryan-minimal added this pull request to the merge queue Oct 20, 2026
Merged via the queue into main with commit 0ced567 Oct 20, 2026 8000
12 checks passed
@bryan-minimal
bryan-minimal deleted the docs/source-date-epoch-rule branch October 20, 2026 18:35
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

0