Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
37
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 7 in progress · Last activity 3mo ago
See all on GitHub →
https://github.com/cataclysmbn/Cataclysm-BN/actions/runs/28531733148/job/84587179488?pr=9762 occurred right after https://github.com/denoland/deno/releases/tag/v2.9.1
I have a use case where I want to manage my Deno installation through another tool, mise specifically in this case, but I'd like to still use the action to manage the cache. I find it easier to let Deno manage the cache than manually with the action. Can we add a configuration to disable Deno installation, or is the stance to just manage the cache manually?
Problem supports reading via (added in #32), but it expects a bare version number like . However, dvm (https://github.com/justjavac/dvm) writes in format: This causes to fail with: Expected behavior should parse the prefix when reading , since that's the format dvm produces (via ). Workaround Extract the version manually before calling :
Recent fixes
Describe the bug denoland/setup-deno fails to resolve and install the most recent versions when they are missing from https://deno.com/versions.json, even if the release exists on denoland/deno. While works fine (because it fetches the tag directly from the GitHub API), specifying a fixed version or a semver range fails if the version isn't yet listed in the JSON. Example Case Released version: (Released 2 days ago) : Does not yet contain . Link to the failing Action https://github.com/bee-browser/bee/actions/runs/25147734427/job/73719002137 Error Message Technical Context fetches and resolves a specified semver to a particular version. When there is a lag in updating the JSON file, setup-deno becomes unusable for the newly released version. Suggested Solution Immediate fix: Please update https://deno.com/versions.json to include v2.7.14. Long-term fix: Is it possible to automate the JSON update immediately upon release, or implement a fallback in setup-deno to check GitHub Releases API when a version is not found in the JSON? Thank you for maintaining this project and for all your hard work on the Deno ecosystem!
@crowlKats It looks like you forgot to move the v2 branch ref to the v2.0.4's commit.
Structured data for AI agents
Repository: denoland/setup-deno. Description: Set up your GitHub Actions workflow with a specific version of Deno Stars: 328, Forks: 56. Primary language: TypeScript. Languages: TypeScript (100%). License: MIT. Latest release: v2.0.4 (2mo ago). Open PRs: 7, open issues: 10. Last activity: 3mo ago. Community health: 37%. Top contributors: lucacasonato, crowlKats, csvn, dsherret, satyarohith, kt3k, katayama8000, ctdeakin, sebdanielsson, r7kamura and others.