Commit activity
Last 12 weeks · 1 commit
Community health
2 of 6 standards met
37
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Active · Last activity 1mo ago
See all on GitHub →
Follow-up to the read-only work (#348). Now that the registry rejects all publish webhooks, nothing feeds the async build pipeline — so this removes it. The read-only webhook gate and the entire serving path (S3 storage, replication, and the cdn.deno.land CloudFront distribution) are left untouched. What will do on merge Destroy: the Lambda, its SQS event-source mapping, and its permission the and SQS queues the two SQS CloudWatch alarms (, ) and the instance of the lambda-errors alarm Update (in place): the lambda execution IAM policy (drops the now-unused SQS statement) the Lambda (drops the env var) No stateful data is touched — no S3 buckets, no CloudFront, no datastore. Source / tooling cleanup delete and its test drop the unused / exports from and the test helper from remove the SQS setup from and the elasticmq service from refresh the webhook handler docstring to describe the read-only behavior Note I couldn't run locally (no terraform on this machine), but I grepped the config and there are no remaining references to any removed resource. CI's Validate step is the gate — if anything dangles, the PR goes red before any apply runs. Left as an explicit follow-up: removing the webhook Lambda + its API Gateway route + the datastore/SSM surface entirely. Kept here to stay off the networked/stateful path in this PR.
The content type returned right now is , which causes the deno cli to not load these files.
Redis isn't found: It exists, though: !-2147483648_-211826 This behaviour can be observed for any package.
Recent fixes
deno.land/x is being deprecated in favor of JSR. This gates the GitHub publish webhook handler so no new modules or versions can be published, while existing content continues to be served unchanged. now checks a env flag, defaulting to read-only**. When enabled, the handler returns a 403 pointing to JSR before forwarding anything to apiland, so no build is ever queued. Set to temporarily re-enable publishing for a controlled rollback. The webhook endpoint and its Terraform are intentionally left in place — the Lambda simply rejects new publishes. Deploying the updated Lambda image makes the registry read-only immediately; no env var needs to be set.
When I am browsing the documentation of a module, I can no longer view the documentation of a specific symbol. This still worked about a week ago. Clicking on any of the links to the classes does no longer load the page which documents the class. Instead the same documentation of the module is loaded again, only the URL changes to e.g. https://deno.land/x/oak@14.2.0/application.ts?s=Application (without any effect).
Structured data for AI agents
Repository: denoland/deno_registry2. Description: The backend for the deno.land/x service Stars: 93, Forks: 13. Primary language: TypeScript. Languages: TypeScript (63.1%), HCL (33.7%), Shell (2.6%), Dockerfile (0.5%), Makefile (0.2%). License: MIT. Homepage: https://deno.land/x Topics: deno. Open PRs: 1, open issues: 27. Last activity: 1mo ago. Community health: 37%. Top contributors: lucacasonato, wperron, crowlKats, piscisaureus, bartlomieju, christophgysin, UltiRequiem, kitsonk, ry.