Fix @rev parameter of dtolnay/rust-toolchain

[LingMan]

dtolnay/rust-toolchain parses the desired toolchain version from the @rev parameter. If one wants to use the explicit toolchain input, @master should be specified.

[BurntSushi]

@master should be specified

Where did you get that from? Why is v1 wrong?

[LingMan]

https://github.com/dtolnay/rust-toolchain/blob/master/README.md

toolchain	Rustup toolchain specifier e.g. stable, nightly, 1.42.0, nightly-2022-01-01. Important: the default is to match the @rev as described above. When passing an explicit toolchain as an input instead of @rev, you'll want to use "dtolnay/rust-toolchain@master" as the revision of the action.

[BurntSushi]

Bah. Well that's annoying.

I'll take a closer look at this later. I have this same configuration repeated across a bunch of different repos. I'm sick and tired of having to update and tweak it, and doing it piecemeal is also annoying. So I'll probably figure out what I want to do and then do it everywhere.

Thanks for bringing this to my attention.

[LingMan]

Although the repository does have a v1 tag. That's probably the reason this didn't blow up immediately. Maybe @dtolnay has plans to support the @vN syntax after all?

[dtolnay]

A v﹏ tag is required in order to appear in search on https://github.com/marketplace?type=actions.

I'll update v1 occasionally to point to newer commits from master. I haven't done that in a while because I don't use the tag myself, so currently it doesn't include the most recent 2 PRs (one of which is a build speed improvement, so at least somewhat desirable).

For my own repos master is what I use, but I also don't care if other people refer to v1. They just won't be getting changes from PRs until later than master; TBD how much later. Also the functionality supported by v1 can be out of sync with the documentation which is rendered from master.

My guess is v1 will get bumped close to never, and if someone requests a bump they'd just get told to use master instead.