SOURCE_DATE_EPOCH not working as expected
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 245
- Forks
- 80
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 2
Description
In https://github.com/tc39/proposal-pattern-matching, locally npm run build is now deterministic. It won't update the date until spec.emu is modified. However, PRs that do not update spec.emu - and builds on main that do not update it - still generate a date diff.
I suspect there's timezone issues here, and it's something about the value i'm passing to the env var, or, something about the modification dates locally vs in github actions, but I'm hoping the ultimate goal of a stable spec date can be achieved somehow :-)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing npm run build locally with builds on main, focusing on how SOURCE_DATE_EPOCH and modification dates affect generated dates. Use spec.emu as the reference input and verify the fix by confirming that builds without changes to it produce no date diff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100