question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The `set-env` command is deprecated and will be disabled on November 16th

See original GitHub issue

Description

index.js uses set-env and add-path. Both will be disabled soon. As a result I’m seeing these warnings in my log:

The `set-env` command is deprecated and will be disabled on November 16th. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
The `add-path` command is deprecated and will be disabled on November 16th. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

Details

YAML

name: Build on push

on:
  push:
    branches: [master]

jobs:

  Box:
    runs-on: <runner name>
    steps:
    - uses: actions/checkout@v2
      with:
        fetch-depth: 0 
    - uses: actions/setup-dotnet@v1
      with:
        dotnet-version: '3.1.100'
    - uses: nuget/setup-nuget@v1
      with:
        nuget-version: 'latest'
    - name: <build name>
      run: |
        cd <Project name>
        nuget restore <Solution name>.sln
        msbuild  <Solution name>.sln /verbosity:normal /t:Rebuild /p:Configuration=Debug
        dotnet test  <Solution name>.sln

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:2
  • Comments:5

github_iconTop GitHub Comments

4reactions
kyle-radercommented, Nov 17, 2020

set-env is now disabled, and I am seeing Errors now using

- name: Setup .NET Core
      uses: actions/setup-dotnet@v1
      with:
        dotnet-version: 3.1.302

Edit: Okay, Nevermind this task is working! There are just many other things hitting this same error 😉

1reaction
ericsampsoncommented, Nov 13, 2020

According to the releases/tags for this repo, V1 should have been updated already?

Read more comments on GitHub >

github_iconTop Results From Across the Web

The `set-env` command is deprecated and will be disabled on ...
The `set-env ` command is deprecated and will be disabled on November 16th. Please upgrade to using Environment Files.
Read more >
Github Actions set-env deprecation | [“Kirø~$”]
We get the following deprecation message in our github actions workflow. The `set-env` command is deprecated and will be disabled on November 16th....
Read more >
How do I set an env var with a bash expression in GitHub ...
Due to a security vulnerability set-env is being deprecated and should no longer be used. This is the new way to set environment...
Read more >
NixOS 23.05 manual
extraConfig will be deprecated when NixOS 22.11 reaches end of life. To reduce closure size in nixos/modules/profiles/minimal.nix profile disabled ...
Read more >
Changelog - curl
docs: remove mentions of deprecated '--without-openssl' parameter; docs: tag curl options better in man pages; docs: tell about disabled protocols in CURLOPT_* ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found