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
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.
Summary
This PR updates
README.mdandCONTRIBUTING.mdto bring both documents into alignment with the three develop cycles that have landed sincev2.1.0-25.7.0: the Node.js bump to25.8.0, thetzdatapin bump to2026a-r0, and the addition of theTZ=UTCintegrity test to the PR test suite. Both files also receive a<div align="center">wrapper around their opening title and icon block to center the heading in GitHub's rendered Markdown view.Files Changed
Added:
Modified:
CONTRIBUTING.mdREADME.mdDeleted:
Key Changes
README.mdKey Features table from25.7.0to25.8.0, and updated the builder stage reference in both the Usage section Dockerfile snippet and the Pinning to a Specific Version example fromnode:25.7.0-alpine3.22tonode:25.8.0-alpine3.22.Timezone Databaserow in theREADME.mdKey Features table to specify the explicit package version, changingIANA tzdata includedtoIANA tzdata 2026a-r0 included.README.md(Usage Dockerfile snippet, Pinning section, and Versioning section) fromv2.1.0-25.7.0tov2.2.0-25.8.0.Integrity Test: TZ, to the CI/CD & Quality Guarantees numbered list inREADME.md, documenting thatTZis tested to equalUTCon every pull request.<div align="center">/</div>wrappers around the opening title, tagline, and icon block in bothREADME.mdandCONTRIBUTING.md, centering the header block in GitHub's Markdown renderer.CONTRIBUTING.mdfrom25.7.0to25.8.0.Integrity Test — TZ is UTCdescription to the PR Tests section inCONTRIBUTING.mdimmediately after the existingNODE_ENVdescription, and updated the merge-readiness statement from "All four integrity tests" to "All five integrity tests".Timezone Databaserow in theCONTRIBUTING.mdimage components table to specify the package version asIANA timezone data 2026a-r0rather than the unversioned description.CONTRIBUTING.mdfromv2.1.0-25.7.0/v2.2.0-25.8.0tov2.2.0-25.8.0/v2.3.0-25.9.0, and the step 4 tag example fromv2.1.0-25.7.0tov2.2.0-25.8.0.CONTRIBUTING.mdfromnode:25.7.0-alpine3.22tonode:25.8.0-alpine3.22, and tightened the rejection criteria wording to referenceENV NODE_ENV=productionandENV TZ=UTCwith their fullENVprefix rather than just the variable names.