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
package.json,deno.json, andjsr.json(three-file bump as required by the dual-publish model).format-datetime→khmer-datetimeinpackage.json(repository.url,homepage,bugs.url). The npm/JSR package name is unchanged (@pphatdev/format-datetime).docs/set (10 files) covering getting started, tokens, API reference, TypeScript, lunar calendar, algorithms, architecture, runtimes, examples, and FAQ.llms.txtat the repo root following the llmstxt.org spec, pointing LLM tools at every doc and source file viaraw.githubusercontent.com/pphatdev/khmer-datetime/...URLs.README.mdlinking toCLAUDE.mdandllms.txt, plus a list of load-bearing invariants (longest-token-first regex,.tsimport extensions, no Node built-ins insrc/, UTC-noon normalization in the lunar solver, three-file version bumps, dual-runtime test parity,globalThisattachment,defualtPatternstypo,KhmerDateplaceholder methods)..github/workflows/npm-publish.yml).postcss8.5.18 → 8.5.26 (Dependabot, transitive dev-only).Commits (non-merge)
a30bc09docs: add documentation structure and AI agent guidelines for contributors4528b2fdocs: add comprehensive documentation for format-datetime library tokens and usage3777b80chore: update repository URL, homepage, and bug tracker links to reflect project rename5d7841b/1cba8cefeat: add GitHub Actions workflow to automate NPM and GitHub package publishingbadb530chore: bump version to 0.3.518cb4d5build(deps): bump postcss from 8.5.18 to 8.5.26Files changed
No
src/ortest/files change in this PR — this is a docs, infra, and version-bump release only.Verification
npm run buildsucceeds (dist artifacts produced for cjs, esm, iife +.d.ts).npm run testpasses on Node (Vitest) and Deno (@std/testing+@std/expect).package.json,deno.json,jsr.jsonall show0.3.5.package.jsonrepository.url,homepage, andbugs.urlall point tokhmer-datetime.llms.txtlinks resolve (spot-check a fewraw.githubusercontent.com/pphatdev/khmer-datetime/...URLs).npm-publish.ymlworkflow completes green.Risk
Low. No runtime source changes, no API surface changes, no test changes. The repository URL rename is metadata-only — the published package name stays
@pphatdev/format-datetimeon both npm and JSR.