Skip to content

taiki-e/install-action blocked at v1.6.0 #435

@MusicalNinjaDad

Description

@MusicalNinjaDad

Hi,
After some searching I found jaq, which does exactly what I need in a way I can trust.

Thanks!

Background

I'm using jaq in github actions to allow me to store reusable yaml elements (mainly matrix definitions) in a separate file and use them in multiple workflows & jobs

Issue

  • Installing jaq via taiki-e/install-action installs v1.6.0
  • I can force this by specifically requesting tool: jaq@3.0.0 but that slows the installation from 1-2s to 13-15s and removes dependabot support
  • I've done a little digging and found the underlying issue. I opened a codespace on install-action and manually ran their manifest update script which output:
    loading pre-existing manifest /workspaces/install-action/manifests/jaq.json
    no asset '["jaq-v3.0.0-x86_64-unknown-linux-musl"]' for host platform 'x86_64_linux_musl'
    no asset '["jaq-v3.0.0-x86_64-apple-darwin"]' for host platform 'x86_64_macos'
    no asset '["jaq-v3.0.0-x86_64-pc-windows-msvc.exe"]' for host platform 'x86_64_windows'
    no asset '["jaq-v3.0.0-aarch64-unknown-linux-gnu"]' for host platform 'aarch64_linux_gnu'
    no asset '["jaq-v3.0.0-aarch64-apple-darwin"]' for host platform 'aarch64_macos'
    no release asset for jaq 3.0.0
    ...
    ... etc for all releases >v1.6.0
    

Suggestion / Offer

  • I guess the easiest "fix" would be to request removal from the supported tools list, at which point users will at least get the latest version via automatic fallback to cargo binstall if they install jaq via install-action
  • I'd be happy to support with an efficient cross-compilation workflow if you prefer to publish a full suite of release binaries and have install-action support (example here: https://github.com/MusicalNinjaDad/rust/blob/main/.github/workflows/rust-publish.yml#L84)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions