| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
For the record, this landed in actions/setup-java@v1.4.3 (I was mystified as to why I was getting set-env warnings when I didn't use set-env…directly.) |
Sorry, something went wrong.
- Background: https://github.community/t/version-numbering-for-actions/16307/4 - Specific issue: actions/setup-java#104 (comment) actions/setup-java@v1.4.2 was creating warning messages about set-env, needed to switch to v1.4.3. Instead, all actions now use @v1 or @v2, which points to a branch.
- Background: https://github.community/t/version-numbering-for-actions/16307/4 - Specific issue: actions/setup-java#104 (comment) actions/setup-java@v1.4.2 was creating warning messages about set-env, needed to switch to v1.4.3. Instead, all actions now use @v1 or @v2, which points to a branch.
- Background: https://github.community/t/version-numbering-for-actions/16307/4 - Specific issue: actions/setup-java#104 (comment) actions/setup-java@v1.4.2 was creating warning messages about set-env, needed to switch to v1.4.3. Instead, all actions now use @v1 or @v2, which points to a branch.
* Add Licensed workflow and config files * Manually validate dependencies * Swap to Environment Files
| Back | FazBrowse Home | New Git URL |
The newest toolkit version uses Environment files to communicate with the Runner. This pr moves towards the new way of communicating with the runner and updates the toolkit version if appropriate.