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/Flowseal/zapret-discord-youtube/pull/9962
**Author:** [@salmanmkc](https://github.com/salmanmkc)
**Created:** 2/7/2026
**Status:** ✅ Merged
**Merged:** 2/7/2026
**Merged by:** [@Flowseal](https://github.com/Flowseal)
**Base:** `main` ← **Head:** `upgrade-github-actions-node24-general`
---
### 📝 Commits (1)
- [`e004b75`](https://github.com/Flowseal/zapret-discord-youtube/commit/e004b7599f75486f772e68868a77615f2d2838b1) Upgrade GitHub Actions to latest versions
### 📊 Changes
**1 file changed** (+1 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `.github/workflows/comment.yml` (+1 -1)
</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 |
|--------|---------------|-------------|---------|-------|
| `peter-evans/create-or-update-comment` | [`v4`](https://github.com/peter-evans/create-or-update-comment/releases/tag/v4) | [`v5`](https://github.com/peter-evans/create-or-update-comment/releases/tag/v5) | [Release](https://github.com/peter-evans/create-or-update-comment/releases/tag/v5) | comment.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>
mirror-bot
changed title from [PR #9962] [MERGED] Upgrade GitHub Actions to latest versions to [PR #9962] Upgrade GitHub Actions to latest versions2026-07-20 04:23:44 +03:00
mirror-bot
changed title from [PR #9962] Upgrade GitHub Actions to latest versions to [PR #9962] [MERGED] Upgrade GitHub Actions to latest versions2026-07-20 23:19:44 +03:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Flowseal/zapret-discord-youtube/pull/9962
Author: @salmanmkc
Created: 2/7/2026
Status: ✅ Merged
Merged: 2/7/2026
Merged by: @Flowseal
Base:
main← Head:upgrade-github-actions-node24-general📝 Commits (1)
e004b75Upgrade GitHub Actions to latest versions📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
.github/workflows/comment.yml(+1 -1)📄 Description
Summary
Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates.
Changes
peter-evans/create-or-update-commentv4v5Why upgrade?
Keeping GitHub Actions up to date ensures:
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.
[PR #9962] [MERGED] Upgrade GitHub Actions to latest versionsto [PR #9962] Upgrade GitHub Actions to latest versions[PR #9962] Upgrade GitHub Actions to latest versionsto [PR #9962] [MERGED] Upgrade GitHub Actions to latest versions