Priya Gupta

Hello 👋, 
 Apologies for the delayed response. To assist in resolving this issue, could you please provide the following details: * The architecture of your self-hosted runner. * The configuration...

Hello @178inaba👋, Thank you for your keen observation. I'm pleased to inform you that the `Validate setup-go` workflow issue has been addressed in our recently merged pull request ([#479](https://github.com/actions/setup-go/pull/479)). Therefore,...

Hello @silverwind, thank you for your report. I understood your concern. Currently, the problem matcher in the `setup-go` action is designed to capture a single line and column number where...

Thank you for your valuable input, @silverwind. We will take your suggestion into consideration for future enhancement to our problem matcher. In the meantime, here are potential workarounds you may...

Hello @dkirrane 👋, I've attempted to reproduce the issue on my end, but was unable to do so. In my test environment, caching and reuse of dependencies worked as expected....

Hello @dkirrane, Just a gentle reminder about the issue. If you could provide a minimal reproduction of the problem, it would help us in investigating this further. Thank you in...

Hello @dkirrane👋 , A gentle reminder regarding the problem. A minimal reproduction of the problem from your end would be a great help. We look forward to your response. Thank...

Hello @dkirrane👋, Due to inactivity, I'm going to close this issue for now. Please feel free to reopen the issue if necessary, or create a new one. Thank you :)

Hi @marverix , The `setup-python` action prepends the installed Python version directory to the `PATH` environment variable and automatically makes it available to all subsequent actions in the current job....

@marverix 👋 , Thanks for your response! The action uses `core.addPath()` which prepends the installed Python directory to the `PATH` environment variable. For additional `PATH` customization, you can use the...