snorkel/root-repository-maintenance-4a9d6ef2d06f43
2
0
Fork 0
Code Issues Pull requests 5 Projects Releases Packages Wiki Activity

guard-pinned-zod-import: Guard pinned Zod import map #3

Open
std-bot wants to merge 1 commit from task/guard-pinned-zod-import into main
pull from: task/guard-pinned-zod-import
merge into: snorkel:main
Conversation 0 Commits 1 Files changed 10 +329 -53
std-bot commented 2026-06-07 17:44:12 +00:00
First-time contributor
Copy link

Assigned idea

Add a small deterministic check that ensures import_map.json continues to map "zod" to the pinned "npm:zod@3.25.64" specifier currently used by the project.

Approach: Create a repository script or test that reads import_map.json as JSON, verifies the top-level imports object exists, and asserts imports.zod is exactly "npm:zod@3.25.64". Keep the check focused on this dependency so future dependency changes must be intentional.

Verification: Run the new validation command, for example deno test or the added script command, and also run deno fmt --check import_map.json to confirm the import map remains valid and formatted.

Risk: Low risk; the change only adds validation around an existing import-map entry. The main risk is choosing a command style that does not match the repository's existing tooling, so the implementation should reuse any existing Deno/test convention if present.

Agent context

Task slug: guard-pinned-zod-import
Branch: task/guard-pinned-zod-import

## Assigned idea Add a small deterministic check that ensures import_map.json continues to map "zod" to the pinned "npm:zod@3.25.64" specifier currently used by the project. Approach: Create a repository script or test that reads import_map.json as JSON, verifies the top-level imports object exists, and asserts imports.zod is exactly "npm:zod@3.25.64". Keep the check focused on this dependency so future dependency changes must be intentional. Verification: Run the new validation command, for example `deno test` or the added script command, and also run `deno fmt --check import_map.json` to confirm the import map remains valid and formatted. Risk: Low risk; the change only adds validation around an existing import-map entry. The main risk is choosing a command style that does not match the repository's existing tooling, so the implementation should reuse any existing Deno/test convention if present. ## Agent context Task slug: guard-pinned-zod-import Branch: task/guard-pinned-zod-import <!-- std-ts:idea-pr-body -->
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin task/guard-pinned-zod-import:task/guard-pinned-zod-import
git switch task/guard-pinned-zod-import

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff task/guard-pinned-zod-import
git switch task/guard-pinned-zod-import
git rebase main
git switch main
git merge --ff-only task/guard-pinned-zod-import
git switch task/guard-pinned-zod-import
git rebase main
git switch main
git merge --no-ff task/guard-pinned-zod-import
git switch main
git merge --squash task/guard-pinned-zod-import
git switch main
git merge --ff-only task/guard-pinned-zod-import
git switch main
git merge task/guard-pinned-zod-import
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
snorkel/root-repository-maintenance-4a9d6ef2d06f43!3
No description provided.