Skip to content

issues Search Results · repo:apache/infrastructure-actions language:Python

Filter by

55 results
 (104 ms)

55 results

inapache/infrastructure-actions (press backspace or delete to remove)

When authoring GH workflows, people may add new or change action references (uses:). Also dependabot and Renovate change action references. If the workflows/jobs/steps are not run when such an action ...
  • snazy
  • Opened 
    7 days ago
  • #482

In the pelican action: + cmake --version cmake version 3.31.6 CMake suite maintained and supported by Kitware (kitware.com/cmake). + cmake -DCMARK_TESTS=OFF -DCMARK_STATIC=OFF .. CMake Deprecation Warning ...
  • dave2wave
  • Opened 
    on Nov 30, 2025
  • #400

While working on a website build using apache/infrastructure-actions/pelican - I noticed that there is a conflict on the versions of pygments between pelican and rich. See debug run here: https://github.com/apache/tooling-docs/actions/runs/19802923980/job/56732834987 ...
  • dave2wave
  • Opened 
    on Nov 30, 2025
  • #399

Hi, I noticed that actions-cool/maintain-one-comment@* is in the approved_patterns.yml with a wildcard while the README states: Always pin actions to exact commit SHAs, never use tags or branch references. ...
  • ongdisheng
  • 2
  • Opened 
    on Nov 24, 2025
  • #385

This is blocked on https://github.com/apache/pekko-sbt-paradox being updated to a version of https://github.com/sbt/sbt-github-actions/ that has https://github.com/sbt/sbt-github-actions/pull/207
gateway
  • raboof
  • 2
  • Opened 
    on Nov 18, 2025
  • #376

Replace gaurav-nelson/github-action-markdown-link-check with the actively maintained fork, tcort/github-action-markdown-link-check Requires tcort/github-action-markdown-link-check to be allowlisted first ...
  • kevinjqliu
  • 2
  • Opened 
    on Nov 14, 2025
  • #371

From actions.yml: gradle/wrapper-validation-action: * : expires_at: 2050-01-01 keep: true f9c9c575b8b21b6485636a91ffecd10e558c62f6: tag: v3.5.0 expires_at: 2050-01-01 Not sure this ...
  • snazy
  • 7
  • Opened 
    on Nov 7, 2025
  • #355

It would be great if we had a way to define more fine-grained trust levels for GitHub actions: for example, it might be fine to allow many questionable actions in pull_request workflows, since those don ...
gateway
  • raboof
  • Opened 
    on Oct 6, 2025
  • #324

Since #279, the dummy workflow is ran for PRs and pushes. If I understand correctly, the intent was to have a CI job that checks the latest allowed versions of actions don t introduce dependencies on ...
gateway
  • raboof
  • Opened 
    on Sep 22, 2025
  • #305

As I noticed in #251 the current format leads to failed pulls: /usr/bin/docker pull pandoc/core@sha256-48e15e83db0df6fb39b24adb0210ecbde85003a3a8139d526e29c98f95ac0a93 invalid reference format Warning: ...
  • assignUser
  • 1
  • Opened 
    on Aug 2, 2025
  • #253
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.