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

Update actions versions #2260

Merged
merged 13 commits into from
May 20, 2024
Merged

Update actions versions #2260

merged 13 commits into from
May 20, 2024

Conversation

tinyboxvk
Copy link
Contributor

Fix GitHub Actions Node.js deprecation warnings

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2.

This PR bumps actions/checkout to v4, and actions/setup-python to v5.

Fix GitHub Actions Node.js deprecation warnings
@aandergr
Copy link
Member

Pretty nice that you addressed the deprecation warnings in the actions. I think one should also take the opportunity to adjust the versions in the other actions, not only in the Windows EXE build action.

I have also seen that setup-python provides a cache for the dependencies, which could save a few seconds for the build. Would you perhaps like to take the opportunity to implement this as well?

@tinyboxvk
Copy link
Contributor Author

I have updated the PR per your suggestion.

with:
python-version: 3.12
cache: 'pip'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
cache: 'pip'
cache: 'pipenv'

We actually use Pipenv for dependency management, Pip is only used in the Workflows to install Pipenv.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I wasn't quite sure which one to use. Does that apply to "packages.yml" as well?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Good point, "packages.yml" does acutally not install the Instaloader dependencies, it just installs the dependencies required for the packaging, and does so with Pip. However, the pip cache mechanism seems to be using the requirements.txt file which we do not have, so for packages.yml the cache should better be disabled.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good. I removed the cache entry from the "packages.yml" file.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thank you very much!

@aandergr aandergr merged commit 3b705fe into instaloader:master May 20, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants