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

chore: dump gha for node deprecation #1146

Merged
merged 1 commit into from
Oct 9, 2024
Merged

Conversation

dimaqq
Copy link
Contributor

@dimaqq dimaqq commented Oct 8, 2024

Bump the versions of 1st party github actions in CI.

Fixes #1115

Fixes warnings like this: Linter (3.10) The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

And this: Warning actions/upload-artifact@v3 is scheduled for deprecation on November 30, 2024. Learn more. Similarly, v1/v2 are scheduled for deprecation on June 30, 2024. Please update your workflow to use v4 of the artifact actions. This deprecation will not impact any existing versions of GitHub Enterprise Server being used by customers.

Not touching download-artifact as that's sourced from someone's private repo; would have to actually check what changed there.

Copy link
Contributor

@james-garner-canonical james-garner-canonical left a comment

Choose a reason for hiding this comment

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

Sounds good to me.

I noticed that we still get a similar warning on cla-check

The following actions use a deprecated Node.js version and will be forced to run on node20: canonical/[email protected].

The version 1.2.3 specified here is kind of odd, since apparently the latest version is 1.1.4

@dimaqq
Copy link
Contributor Author

dimaqq commented Oct 9, 2024

I think you're confusing the github actions marketplace with repo tags.
See https://github.com/canonical/has-signed-canonical-cla/tags

@james-garner-canonical
Copy link
Contributor

You're right! Looks like 1.2.3 is the latest so nothing to do there.

@dimaqq
Copy link
Contributor Author

dimaqq commented Oct 9, 2024

Ugh why is GitHub unhappy about signed commits now?

commit b4e7f56f54d33d9a775973b67317d5d54a9d9bf1 (HEAD -> chore-bump-gha, origin/chore-bump-gha)
gpg: Signature made Tue  8 Oct 16:21:42 2024 JST
gpg:                using EDDSA key 2CACAC142A47D695069F998989906BA8E1A63051
gpg: Good signature from "Dima Tisnek <[email protected]>" [ultimate]
gpg:                 aka "Dima Tisnek <[email protected]>" [ultimate]
Author: Dima Tisnek <[email protected]>
Date:   Tue Oct 8 16:21:42 2024 +0900

    chore: dump gha for node deprecation

Looks a-ok to me!

@dimaqq
Copy link
Contributor Author

dimaqq commented Oct 9, 2024

Solved by reuploading the same key to github.

@dimaqq
Copy link
Contributor Author

dimaqq commented Oct 9, 2024

/merge

@jujubot jujubot merged commit 29ee682 into juju:main Oct 9, 2024
10 of 12 checks passed
@dimaqq dimaqq deleted the chore-bump-gha branch October 9, 2024 06:58
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.

Clean up CI warnings
3 participants