How do I use the latest upstream version?

[iainelder]

I would like to use this wrapper to simplify the installation of dependencies in my GitHub workflows. In one of my projects, actionlint is the only dependency that isn't a Python package.

The latest version of your wrapper is 1.6.24.

The latest version of the upstream project is 1.6.25.

It seems a trivial difference now, but that gap will grow. Without a clear way for me to get the latest upstream version I'm hesitant to depend on this wrapper.

[Mateusz-Grzelinski]

Well, if you are doing something production, then it is not a great idea to depend on this repo.
This is my first time releasing the package, and the forked code is not obvious, although I managed to develop nice automation for it.
I just updated it to newest version.
I just updated readme and documented a bit more.
The best way would be to probably automate it fully...
What would you like to see in this repo? I simply made it to make my life a bit easier.

[Mateusz-Grzelinski]

I would love to move away from setup.py but learning how to extend build system in pyproject.toml is quite involving.

[iainelder]

Thanks! I will try it now to replace the "Install actionlint" step of my workflow with your pre-commit hook.

My own pre-commit hook looks like this:

      - id: actionlint
        name: actionlint
        entry: actionlint
        types: [yaml]
        files: .github/workflows
        language: system

And I install actionlint like this:

      - name: Install actionlint
        uses: giantswarm/install-binary-action@v1.1.0
        with:
          binary: actionlint
          version: 1.6.25
          download_url: "https://github.com/rhysd/actionlint/releases/download/v${version}/actionlint_${version}_linux_amd64.tar.gz"
          tarball_binary_path: "${binary}"
          smoke_test: "${binary} --version"

      - name: Install Python dependencies
        run: poetry install --no-interaction

      - name: Run pre-commit checks
        run: poetry run pre-commit run --all-files --verbose

The best way would be to probably automate it fully...

You could run your auto-update script on a schedule and run the rest of the steps if it makes changes.

would love to move away from setup.py but learning how to extend build system in pyproject.toml is quite involving.

Have you tried Poetry? It generates a pyproject.toml file and can manage the dependencies parts automatically.

[Mateusz-Grzelinski]

using pre-commit you should be able to skip the giantswarm/install-binary-action, but I am too tired to to test it today, I've done this scrpt a while back.
The auto update script is only partial automation of process, i would still need to write and action to reelase a package, we will see.
I know the pyproject. But the hard part is customizing build system: see #2 (just created). This entire project customizes build steps from setuptools

[iainelder]

Yes, that's exactly what I've just done: iainelder/aws-org-tree@8ce7b50

Good luck with the release automation! My own workflow automates a GitHub release and a publication to PyPI. You might be able to to reuse part of it.

Thank you for your help.