Skip to content

change: Add GitHub Actions to Dependabot configuration - #13283

Closed
sd416 wants to merge 0 commit into
linode:developfrom
sd416:develop
Closed

change: Add GitHub Actions to Dependabot configuration#13283
sd416 wants to merge 0 commit into
linode:developfrom
sd416:develop

Conversation

@sd416

@sd416 sd416 commented Jan 16, 2026

Copy link
Copy Markdown

Description 📝

Add GitHub Actions to Dependabot configuration

Changes 🔄

This will auto-update all the github action dependencies as soon as those are released.

  • ...
  • ...

Scope 🚢

Upon production release, changes in this PR will be visible to:

  • All customers
  • Some customers (e.g. in Beta or Limited Availability)
  • [ x] No customers / Not applicable

Target release date 🗓️

Please specify a release date (and environment, if applicable) to guarantee timely review of this PR. If exact date is not known, please approximate and update it as needed.

Preview 📷

Include a screenshot <img src="" /> or video <video src="" /> of the change.

🔒 Use the Mask Sensitive Data setting for security.

💡 For changes requiring multiple steps to validate, prefer a video for clarity.

Before After
📷 📷

How to test 🧪

Prerequisites

(How to setup test environment)

  • ...
  • ...

Reproduction steps

(How to reproduce the issue, if applicable)

  • ...
  • ...

Verification steps

(How to verify changes)

  • ...
  • ...
Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support


  • [ X] I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

  • All tests and CI checks are passing
  • TypeScript compilation succeeded without errors
  • Code passes all linting rules

@sd416
sd416 requested a review from a team as a code owner January 16, 2026 06:59
@bnussman-akamai

bnussman-akamai commented Jan 20, 2026

Copy link
Copy Markdown
Member

Can you add some more context/commentary about your changes? (Specifically around the .github/dependabot.yml addition)

Right now, we primarily use Dependabot to notify us of vulnerable packages. What does this PR enable? Automatic package updates?

@sd416

sd416 commented Jan 21, 2026

Copy link
Copy Markdown
Author

@bnussman-akamai Dependabot has now ability to update actions to the latest available version. This configuration runs once in a week and will create a pull request to update actions to latest available versions in a single PR.

Some other Linode projects are also using it

Ref 1 - https://github.com/linode/linode-cli/blob/dev/.github/dependabot.yml#L12
Ref 2 - https://github.com/linode/terraform-provider-linode/blob/dev/.github/dependabot.yml#L19

@abailly-akamai

Copy link
Copy Markdown
Contributor

@sd416 Pinning guaranties we're working with a secure version of a package (well, until it's not I guess). While getting the latest version has benefits, can't it also introduce security problems on its own? Not arguing the approach, just wanted to confirm this is a desirable outcome.

@sd416

sd416 commented Jan 21, 2026

Copy link
Copy Markdown
Author

You are 100% right about both the problems and benefits of this approach. Luckily for us, all it does is generate a pull request. Whether to merge it or not, it's still in your hands.

Also FYI, it only updates the github action packages such as upload-artifact@v4, actions/checkout@v4 and does not update any actual dependency inside the code.

@abailly-akamai

Copy link
Copy Markdown
Contributor

@sd416 this makes thanks, thx for clarifying. Good to go my end

- run: pnpm run --filter @linode/api-v4 build
- name: Run tests
uses: cypress-io/github-action@b8ba51a856ba5f4c15cf39007636d4ab04f23e3c # v6.10.2
uses: cypress-io/github-action@2ad32e649e4db26c07674ebae31a297601dbcbaf # v6.10.8

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@jdamore-linode for extra 👁️

@github-actions

Copy link
Copy Markdown

This PR is stale because it has been open 15 days with no activity. Please attend to this PR or it will be closed in 5 days

@github-actions github-actions Bot added Stale and removed Stale labels Feb 20, 2026
@github-actions

github-actions Bot commented Mar 8, 2026

Copy link
Copy Markdown

This PR is stale because it has been open 15 days with no activity. Please attend to this PR or it will be closed in 5 days

@github-actions github-actions Bot added the Stale label Mar 8, 2026
@sd416

sd416 commented Mar 8, 2026

Copy link
Copy Markdown
Author

@bnussman-akamai @jdamore-linode Can you please review?

@github-actions

github-actions Bot commented Apr 8, 2026

Copy link
Copy Markdown

This PR is stale because it has been open 15 days with no activity. Please attend to this PR or it will be closed in 5 days

@github-actions github-actions Bot added Stale and removed Stale labels Apr 8, 2026
@github-project-automation github-project-automation Bot moved this from Review to Approved in Cloud Manager Apr 15, 2026
@grevanak-akamai
grevanak-akamai force-pushed the develop branch 2 times, most recently from c31f130 to 6503a87 Compare April 23, 2026 12:06
@github-actions

github-actions Bot commented May 9, 2026

Copy link
Copy Markdown

This PR is stale because it has been open 15 days with no activity. Please attend to this PR or it will be closed in 5 days

@github-actions github-actions Bot added the Stale label May 9, 2026
@sd416 sd416 closed this Aug 20, 2026
@github-project-automation github-project-automation Bot moved this from Approved to Merged in Cloud Manager Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Merged

Development

Successfully merging this pull request may close these issues.

4 participants