Make gettext outputs deterministic #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… msgcat options and header normalization
…gcatOptions with example
…narratives Why: Improve commit quality and make history a resumable work log. What: Simplified rules, removed duplicates, clarified validation and consistency, added "Conversation-Driven Commit Narratives" with template. Progress: 1/1 complete — Next: adopt template in future commits.
Why: ensure correct metadata for npm and linkbacks to project. What: add repository, bugs, homepage fields to root and both plugin packages. Progress: 1/1 complete — Next: publish when ready.
Why: provide direct package landing pages for users. What: update homepage URLs in blueprint/gettext package.json to tree/main package paths. Progress: 1/1 complete — Next: push branch.
Why: Reduce noisy diffs and stabilize headers by keeping existing POT Creation-Date when available, while supporting deterministic builds. What: Add preserveCreationDate option; read previous POT to capture existing Creation-Date; normalize header with precedence: fixedCreationDate > preserveCreationDate > deterministic epoch. Progress: 1/1 complete — Next: document option and usage in README.
JumpLink
changed the title
… to 0.2.4; update dependencies for @types/node and vite
…-read value Why: Previously re-reading the freshly generated POT could override the preserved value; use pre-read date to ensure stability. What: Use prevPotCreationDate captured before extraction when preserveCreationDate is enabled. Progress: 1/1 complete — Next: verify on downstream project.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make gettext outputs deterministic; add commit rules doc; bump packages to 0.2.5
Improve reproducibility of POT/PO generation to reduce noisy diffs and make CI stable. Add concise commit best practices doc leveraging conversation context. Bump package versions.
Changes
/.cursor/rules/git-commit-best-practices.mdcwith high‑density rules and a conversation‑driven commit template.@gjsify/vite-plugin-gettext)noLocation,deterministic,sourceDateEpoch,fixedCreationDate,sortOutput,msgcatOptions,preserveCreationDate.xgettextOptionsand propagate new flags toxgettext,msgcat,msgmerge.SOURCE_DATE_EPOCHfor reproducible timestamps whendeterministicis true.POT-Creation-DateviafixedCreationDate, preserved previous value when available, or formatted epoch.updatePoFilesto accept options and respectnoLocation/deterministic.formatSourceDateEpoch.README.mdexamples and option docs to reflect new flags.packages/vite-plugin-gettext/package.json: 0.2.2 → 0.2.5packages/vite-plugin-blueprint/package.json: 0.2.2 → 0.2.5Why
Impact
deterministic(and related flags) are set.preserveCreationDateis enabled and a prior POT exists, header date remains stable.Notes
noLocation,deterministic,sourceDateEpoch: 0,sortOutput, andpreserveCreationDatein CI configs for stable archives and diffs.