Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check for CLI component updates #18

Open
SanjulaGanepola opened this issue Oct 1, 2024 · 3 comments
Open

Check for CLI component updates #18

SanjulaGanepola opened this issue Oct 1, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@SanjulaGanepola
Copy link
Owner

No description provided.

@SanjulaGanepola SanjulaGanepola added the enhancement New feature or request label Oct 1, 2024
@SanjulaGanepola
Copy link
Owner Author

@SanjulaGanepola
Copy link
Owner Author

For act, can use: https://api.github.com/repos/nektos/act/releases/latest

@ChristopherHX Any ideas for an easy way to implement this. I was thinking we could detect a new version by checking the installed version against https://api.github.com/repos/nektos/act/releases/latest. As for then updating act, does act have a mechanism to update or can the installation command just be re-run?

@ChristopherHX
Copy link
Contributor

does act have a mechanism to update

No

can the installation command just be re-run?

I have never used most of them, but not all pkg manager I know update on repeating the install command.

How would your extension even know, which package manager is responsible?

Or if none, if replacing the binary would be ok?

e.g. if act is just in PATH and some pkg managers distribute a copy of the gh release page.

Any ideas for an easy way to implement this

As long it is allowed to install act yourself and use that one directly, I would say the user is responsible

IMHO updating act if installed to extension global storage is most straight forward, extract the update to the previous folder and done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants