[PR #1] Fix CI: Update deprecated GitHub Actions commands and dependencies #1

Open
opened 2026-08-01 22:46:35 +00:00 by katia · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/iakat/aikta/pull/1
Author: @Copilot
Created: 7/8/2025
Status: 🔄 Open

Base: mainHead: copilot/fix-3d6bd5d9-f2e2-4c8c-a0f8-ab6c4fde1486


📝 Commits (3)

  • 91b13d9 Initial plan
  • b85f614 Fix deprecated set-output commands and update GitHub Actions versions
  • 59e5e04 Add .gitignore and fix Docker tag conditions

📊 Changes

2 files changed (+58 additions, -7 deletions)

View changed files

📝 .github/workflows/docker.yaml (+7 -7)
.gitignore (+51 -0)

📄 Description

Problem

The CI workflow was failing due to deprecated GitHub Actions commands that were disabled by GitHub in 2023, along with outdated action versions that posed security risks.

Root Cause

The workflow was using the deprecated ::set-output command syntax:

echo "::set-output name=timestamp::$(date +%s)"
echo "::set-output name=short_sha::${GITHUB_SHA::8}"

GitHub disabled these commands and now requires the modern $GITHUB_OUTPUT environment file approach.

Changes Made

1. Fixed Deprecated Commands

Before:

run: |-
  echo "::set-output name=timestamp::$(date +%s)"
  echo "::set-output name=short_sha::${GITHUB_SHA::8}"

After:

run: |-
  echo "timestamp=$(date +%s)" >> $GITHUB_OUTPUT
  echo "short_sha=${GITHUB_SHA::8}" >> $GITHUB_OUTPUT

2. Updated GitHub Actions Versions

  • actions/checkout@v3actions/checkout@v4
  • docker/login-action@v2docker/login-action@v3
  • actions/cache@v3actions/cache@v4

3. Fixed Docker Tag Conditions

Before:

type=raw,value=latest,enable=${{ endsWith(github.ref, github.event.repository.default_branch) }}

After:

type=raw,value=latest,enable={{is_default_branch}}

This ensures Docker tags are only applied to the actual default branch, not branches that happen to end with the same name.

4. Added .gitignore

Added comprehensive .gitignore to prevent Python cache files, virtual environments, and build artifacts from being accidentally committed.

Validation

  • YAML syntax validated successfully
  • All Python source files compile without errors
  • Dockerfile builds correctly
  • All deprecated patterns removed from workflow
  • Follows current GitHub Actions best practices

Expected Impact

  • CI workflows will run successfully without deprecation warnings
  • Docker builds will have correct tagging behavior for releases
  • Improved security with updated action versions
  • No more accidental commits of build artifacts

Fixes the CI pipeline and brings the workflow up to current GitHub Actions standards.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

  • astral.sh
    • Triggering command: curl -LsSf REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.


🔄 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/iakat/aikta/pull/1 **Author:** [@Copilot](https://github.com/apps/copilot-swe-agent) **Created:** 7/8/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `copilot/fix-3d6bd5d9-f2e2-4c8c-a0f8-ab6c4fde1486` --- ### 📝 Commits (3) - [`91b13d9`](https://github.com/iakat/aikta/commit/91b13d9b1bdc1bf9f680892d30f02ff216fe41e7) Initial plan - [`b85f614`](https://github.com/iakat/aikta/commit/b85f61484efe23a074fef25c1546f0c6a11dee06) Fix deprecated set-output commands and update GitHub Actions versions - [`59e5e04`](https://github.com/iakat/aikta/commit/59e5e047a99285c91249f43ac6b897ac2082618c) Add .gitignore and fix Docker tag conditions ### 📊 Changes **2 files changed** (+58 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/docker.yaml` (+7 -7) ➕ `.gitignore` (+51 -0) </details> ### 📄 Description ## Problem The CI workflow was failing due to deprecated GitHub Actions commands that were disabled by GitHub in 2023, along with outdated action versions that posed security risks. ## Root Cause The workflow was using the deprecated `::set-output` command syntax: ```yaml echo "::set-output name=timestamp::$(date +%s)" echo "::set-output name=short_sha::${GITHUB_SHA::8}" ``` GitHub disabled these commands and now requires the modern `$GITHUB_OUTPUT` environment file approach. ## Changes Made ### 1. Fixed Deprecated Commands **Before:** ```yaml run: |- echo "::set-output name=timestamp::$(date +%s)" echo "::set-output name=short_sha::${GITHUB_SHA::8}" ``` **After:** ```yaml run: |- echo "timestamp=$(date +%s)" >> $GITHUB_OUTPUT echo "short_sha=${GITHUB_SHA::8}" >> $GITHUB_OUTPUT ``` ### 2. Updated GitHub Actions Versions - `actions/checkout@v3` → `actions/checkout@v4` - `docker/login-action@v2` → `docker/login-action@v3` - `actions/cache@v3` → `actions/cache@v4` ### 3. Fixed Docker Tag Conditions **Before:** ```yaml type=raw,value=latest,enable=${{ endsWith(github.ref, github.event.repository.default_branch) }} ``` **After:** ```yaml type=raw,value=latest,enable={{is_default_branch}} ``` This ensures Docker tags are only applied to the actual default branch, not branches that happen to end with the same name. ### 4. Added .gitignore Added comprehensive `.gitignore` to prevent Python cache files, virtual environments, and build artifacts from being accidentally committed. ## Validation - ✅ YAML syntax validated successfully - ✅ All Python source files compile without errors - ✅ Dockerfile builds correctly - ✅ All deprecated patterns removed from workflow - ✅ Follows current GitHub Actions best practices ## Expected Impact - CI workflows will run successfully without deprecation warnings - Docker builds will have correct tagging behavior for releases - Improved security with updated action versions - No more accidental commits of build artifacts Fixes the CI pipeline and brings the workflow up to current GitHub Actions standards. > [!WARNING] > > <details> > <summary>Firewall rules blocked me from connecting to one or more addresses</summary> > > #### I tried to connect to the following addresses, but was blocked by firewall rules: > > - `astral.sh` > - Triggering command: `curl -LsSf REDACTED` (dns block) > > If you need me to access, download, or install something from one of these locations, you can either: > > - Configure [Actions setup steps](https://gh.io/copilot/actions-setup-steps) to set up my environment, which run before the firewall is enabled > - Add the appropriate URLs or hosts to my [firewall allow list](https://gh.io/copilot/firewall-config) > > </details> <!-- START COPILOT CODING AGENT TIPS --> --- 💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs. --- <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
katia/aikta#1
No description provided.