-
Notifications
You must be signed in to change notification settings - Fork 68
Patch 1 #942
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
Open
AndresMaqueo
wants to merge
3
commits into
github:main
Choose a base branch
from
AndresMaqueo:patch-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Patch 1 #942
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 4 to 5. - [Release notes](https://github.com/actions/download-artifact/releases) - [Commits](actions/download-artifact@v4...v5) --- updated-dependencies: - dependency-name: actions/download-artifact dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contexto y descripción del problema En tu pipeline de GitHub Actions para pruebas unitarias de CodeQL, tenías un paso crítico encargado de descargar artefactos (los resultados de pruebas) para luego validar esos resultados. Este paso se ejecuta en el job validate-test-results y usa la acción oficial de GitHub actions/download-artifact. El problema fue que en ese paso habías declarado dos veces la acción, así: yaml Copiar Editar uses: actions/download-artifact@v4 uses: actions/download-artifact@v5 Esto es inválido en YAML y GitHub Actions porque un paso solo puede tener un único uses o run. Declarar dos veces el mismo campo provoca que la ejecución falle inmediatamente con error de sintaxis o comportamiento inesperado. Además, tenías la versión 4 y la versión 5 juntas, lo que podría generar conflictos de versión o comportamientos inconsistentes. Impacto real El job de validación de resultados no pudo ejecutar correctamente, y por ende las pruebas unitarias no pudieron confirmarse. Esto bloquea el merge del Pull Request porque la política de protección de ramas exige que todas las verificaciones pasen. Si no se corrige, el pipeline no puede garantizar la calidad del código ni validar la integridad de los tests. Esto afecta tu flujo de trabajo DevOps, automatización de calidad y la confianza en el control de calidad automatizado. Cómo lo solucionamos Elegimos usar la versión más reciente y estable de la acción: actions/download-artifact@v5. Eliminamos la duplicidad para que el paso sea válido y funcional. Esto garantiza que la acción se ejecute correctamente, descargue los artefactos, y el siguiente paso pueda validar los resultados. Ahora el flujo puede continuar, detectar fallos reales de tests, y evitar falsos negativos o bloqueos. Por qué esto importa para ti y para tu ecosistema Mantener la coherencia y limpieza en tu pipeline es clave para la automatización fiable y la escalabilidad. Usar versiones actualizadas reduce riesgos de incompatibilidades y mejora la seguridad. El pipeline completo es tu “oráculo” para la calidad del código: arreglar este paso hace que tu control de calidad funcione a nivel profesional. Esto te permite avanzar en la certificación y monetización de tus servicios como experto en CodeQL y seguridad DevOps. Además, te da una base sólida para seguir integrando nuevas funcionalidades y automatizaciones sin frenos. Resumen rápido El error fue un conflicto de configuración al declarar dos versiones de la acción download-artifact en un mismo paso, lo que provocaba fallo de ejecución y bloqueo en la validación de tests. Se corrigió eliminando la duplicidad y quedando solo con la versión 5, asegurando la correcta descarga y validación de resultados, lo que habilita un pipeline de calidad robusto, confiable y profesional.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates GitHub Actions dependencies and performs code cleanup by upgrading the actions/download-artifact
action from v4 to v5 and removing unnecessary comments.
- Updates
actions/download-artifact
from v4 to v5 in two workflow files - Removes redundant comments that explain basic functionality
- Fixes a minor syntax error in a
jq
command
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
.github/workflows/standard_library_upgrade_tests.yml |
Updates download-artifact action to v5 |
.github/workflows/codeql_unit_tests.yml |
Updates download-artifact action to v5, removes comments, and fixes jq syntax |
El comando jq tiene un escape incorrecto. La barra invertida adicional antes de la comilla de cierre causará un error de sintaxis. Debería ser:jq --raw-output '"PASS \(map(select(.pass == true)) | length)/\(length)"' "$json_report" Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
please enter the description of your change here
Change request type
.ql
,.qll
,.qls
or unit tests)Rules with added or modified queries
Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:
If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?
🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.
Reviewer: Confirm that either a change note is not required or the change note is required and has been added.
Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
Reviewer
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.