Unverified Commit a4374459 authored by Hong Minhee's avatar Hong Minhee
Browse files

Include deno.lock in version control 

Previously, deno.lock was excluded from version control while
pnpm-lock.yaml was committed. This created an inconsistent lockfile
policy where Node.js dependencies were pinned but Deno dependencies
could vary across environments.

This commit:

- Removes deno.lock from .gitignore
- Adds deno.lock to version control for reproducible builds
- Documents lockfile policy in CONTRIBUTING.md and AGENTS.md

Resolves https://github.com/fedify-dev/fedify/issues/371



Co-Authored-By: default avatarClaude <noreply@anthropic.com>
parent 9731dc91

.gitignore

+0 −1
Original line number Diff line number Diff line 
.claude/settings.local.json

.DS_Store

dist/

deno.lock

node_modules/

repomix-output.xml

t.ts

AGENTS.md

+2 −0
Original line number Diff line number Diff line
@@ -37,6 +37,8 @@ Development Environment 
 -  Recommended editor: [Visual Studio Code] with [Deno extension]

 -  Important: Run `deno task codegen` before working with the codebase (for

    code generation)

 -  Lockfiles: Both *deno.lock* and *pnpm-lock.yaml* are committed to the

    repository for reproducible builds.  Update them when changing dependencies.



[Deno]: https://deno.com/

[Node.js]: https://nodejs.org/

CONTRIBUTING.md

+27 −0
Original line number Diff line number Diff line
@@ -197,6 +197,33 @@ When adding a new package to the monorepo, the following files must be updated: 
 -  If using pnpm catalog for dependency management: Add to `catalog` in

    *pnpm-workspace.yaml*.



### Dependency management



Fedify uses two package managers:



 -  **Deno**: For Deno-based packages.  The lockfile is *deno.lock*.

 -  **pnpm**: For Node.js-based packages.  The lockfile is *pnpm-lock.yaml*.



Both lockfiles are committed to the repository to ensure reproducible builds and

consistent dependency resolution across all environments.  When you add, update,

or remove dependencies, you must commit the updated lockfile(s) along with your

changes.



To update the Deno lockfile, run:



~~~~ bash

deno task install

~~~~



To update the pnpm lockfile, run:



~~~~ bash

pnpm install

~~~~



When reviewing pull requests, please check that lockfile changes are included

for any dependency-related changes.



### Pull request builds



Each pull request is automatically built and published to the JSR and npm

deno.lock

0 → 100644
+4624 −0

File added.

Preview size limit exceeded, changes collapsed.