Last 12 weeks ยท 1 commit
2 of 6 standards met
Given what's mentioned by @crowlKats in https://github.com/denoland/setup-deno/pull/101#issuecomment-2884016815, I thought perhaps it's better to combine + into only once more. Given that all metadata for the action comes from . The field in can instead be used if it's preferable to have PR's (e.g. #102) when new versions are released. The only field that has no equivalent in is the field, though I don't think there's any purpose to it when this field exists in .
Repository: denoland/setup-deno. Description: Set up your GitHub Actions workflow with a specific version of Deno Stars: 323, Forks: 53. Primary language: TypeScript. Languages: TypeScript (100%). License: MIT. Latest release: v2.0.3 (9mo ago). Open PRs: 7, open issues: 7. Last activity: 2w ago. Community health: 37%. Top contributors: lucacasonato, crowlKats, csvn, dsherret, satyarohith, kt3k, katayama8000, ctdeakin, sebdanielsson, r7kamura and others.
It would be great to have this action and https://github.com/denoland/deno_install/pull/338 both verifying the digests. After is installed, using the script from https://github.com/denoland/deno/pull/31804#issuecomment-3769542292 should let us safely downgrade to older versions as well. ๐ As an example, safely retrieving the LTS version: Output from : Output from :
Hi, it might be convenient to document in the Readme how to test multiple versions using matrix builds, e.g.: I have this working at https://github.com/seriousme/durable-data/blob/master/.github/workflows/deno-ci.yml Kind regards, Hans