Idea regarding Tiger Github Action

[IsaBeau-Dev]

The idea is to automate the work of @kaiser-chris to manually replace the bundled tiger versions each time you update tiger aka create an release.

So I'd like to propose a change to your release workflow or a new workflow that listens for the release.published event and sends a repository_dispatch to https://github.com/kaiser-chris/tiger-action-public using https://github.com/peter-evans/repository-dispatch (your free to choose something else)

The only other requirement is that @kaiser-chris gives you an access token to the tiger-action repo. Thats for him to decide.

The tiger-action repo would then only need a workflow that listens for repository_dispatch and downloads the latest Linux builds of Vic3 Tiger and CK3 Tiger. (Maybe extract them too.)

[IsaBeau-Dev]

Heres a fancier to look at version if you prefer that:

To streamline the process of updating bundled Tiger versions, I’d like to suggest automating the manual work currently done by @kaiser-chris whenever a new Tiger release is published.

🔁 Workflow Overview

The idea is to modify the release workflow in tiger (or add a new one) that listens for the release.published event and sends a repository_dispatch to kaiser-chris/tiger-action-public. This can be done using peter-evans/repository-dispatch, or any alternative you prefer.

🔐 Access Token Requirement

The only prerequisite is that @kaiser-chris provides a GitHub access token with write permissions to the tiger-action-public repo. This token would be stored as a secret in the amtep/tiger repo to authorize the dispatch.

📦 What Happens in tiger-action-public

The target repo (tiger-action-public) would contain a workflow that:

• Listens for the repository_dispatch event
• Downloads the latest Linux builds of Vic3 Tiger and CK3 Tiger
• Optionally extracts or processes them as needed

✅ Benefits

• Eliminates manual syncing of Tiger builds
• Ensures downstream repos stay up to date automatically
• Reduces maintenance overhead for contributors