[PR #363] Upgrade GitHub Actions to latest versions #390

Open
opened 2026-10-26 09:49:42 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/deepseek-ai/3FS/pull/363
Author: @salmanmkc
Created: 12/20/2025
Status: 🔄 Open

Base: main ← Head: upgrade-github-actions-node24-general


📝 Commits (1)

  • 3b4b428 Upgrade GitHub Actions to latest versions

📊 Changes

1 file changed (+3 additions, -3 deletions)

View changed files

📝 .github/workflows/build-dev-docker-image.yml (+3 -3)

📄 Description

Summary

Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates.

Changes

Action Old Version(s) New Version Release Files
docker/build-push-action 3b5e802 2634353 Release build-dev-docker-image.yml
docker/login-action 65b78e6 5e57cd1 Release build-dev-docker-image.yml
docker/metadata-action 9ec57ed c299e40 Release build-dev-docker-image.yml

Why upgrade?

Keeping GitHub Actions up to date ensures:

  • Security: Latest security patches and fixes
  • Features: Access to new functionality and improvements
  • Compatibility: Better support for current GitHub features
  • Performance: Optimizations and efficiency improvements

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/deepseek-ai/3FS/pull/363 **Author:** [@salmanmkc](https://github.com/salmanmkc) **Created:** 12/20/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `upgrade-github-actions-node24-general` --- ### 📝 Commits (1) - [`3b4b428`](https://github.com/deepseek-ai/3FS/commit/3b4b4283682164f40539d283877a5719501c087e) Upgrade GitHub Actions to latest versions ### 📊 Changes **1 file changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/build-dev-docker-image.yml` (+3 -3) </details> ### 📄 Description ## Summary Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates. ## Changes | Action | Old Version(s) | New Version | Release | Files | |--------|---------------|-------------|---------|-------| | `docker/build-push-action` | [`3b5e802`](https://github.com/docker/build-push-action/commit/3b5e8027fcad23fda98b2e3ac259d8d67585f671) | [`2634353`](https://github.com/docker/build-push-action/commit/263435318d21b8e681c14492fe198d362a7d2c83) | [Release](https://github.com/docker/build-push-action/releases/tag/v6) | build-dev-docker-image.yml | | `docker/login-action` | [`65b78e6`](https://github.com/docker/login-action/commit/65b78e6e13532edd9afa3aa52ac7964289d1a9c1) | [`5e57cd1`](https://github.com/docker/login-action/commit/5e57cd118135c172c3672efd75eb46360885c0ef) | [Release](https://github.com/docker/login-action/releases/tag/v3) | build-dev-docker-image.yml | | `docker/metadata-action` | [`9ec57ed`](https://github.com/docker/metadata-action/commit/9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7) | [`c299e40`](https://github.com/docker/metadata-action/commit/c299e40c65443455700f0fdfc63efafe5b349051) | [Release](https://github.com/docker/metadata-action/releases/tag/v5) | build-dev-docker-image.yml | ## Why upgrade? Keeping GitHub Actions up to date ensures: - **Security**: Latest security patches and fixes - **Features**: Access to new functionality and improvements - **Compatibility**: Better support for current GitHub features - **Performance**: Optimizations and efficiency improvements ### Security Note Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references. ### Testing These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/3FS#390
No description provided.