Default to `v1.x`?
Instead of writing:
- uses: denoland/setup-deno@v1
with:
deno-version: v1.x
It would be nice to write:
- uses: denoland/setup-deno@v1
Then when deno v2 is released we can bump the version of this action:
- uses: denoland/setup-deno@v2
The one risk for this is if we would want to make any breaking changes to the action, but I feel we could just do that when a new major deno version release occurs.
~~This would not be a breaking change because not providing a deno-version currently errors.~~
It looks like we do have a default, but I didn't test that it works. https://github.com/denoland/setup-deno/blob/d4873ceeec10de6275fecd1f94b6985369d40231/action.yml#L10
@satyarohith oh, I didn't realize a default was able to be set there. Do you think this would be a good versioning strategy going forward? Maybe we could add it to the readme?
Do you think this would be a good versioning strategy going forward? Maybe we could add it to the readme?
I'm in favor. In addition to mentioning it in the readme, it would be nice to have a test that exercises this condition in test.yml.
just to add my 2¢, I'd expect the default to be the latest stable version of deno (of any major) and the version of the action to not effect the version of deno. But perhaps I'm too experienced with actions…