Feature: Get last n releases || releases compatible with semver range

[LongLiveCHIEF]

Often if you're doing something like building a docker image around a product (for me it's the official octoprint/octoprint image), then you need to not only build an image for the latest release of a product, but several of the previous releases.

It would be great to be able to specify the last n releases, or to specify a semver input and get all tags that match.

[LongLiveCHIEF]

I'm willing to help by contributing this feature if you like the idea. I was actually going to create this "get release" action, and figured I'd search the marketplace first. Ironically, @foosel is a contributor to this action, and she's the maintainer of the product I'm supporting docker images for!

I also recently released the HackerHappyHour/tagging-strategy action, which would pair with this nicely using the output. It's possible we could even create a compound action to get matching releases and create a matrix of tags.

[LongLiveCHIEF]

Here's what I'm thinking this could look like: (see example of creating a matrix in one job and passing it to another from github actions docs

jobs:
  releases:
    outputs:
      matrix: ${{ steps.releases.outputs.matrix }}
    steps:
      # produces a matrix with a key of `matrix`
      - name: Get Releases
         id: releases
         uses: pozetroninc/github-action-get-latest-release
          with: 
            repository: some/repository
            semver: '^1.0.0'
  build:
    needs: releases
    strategy: 
      matrix: ${{ needs.releases.outputs.matrix }}

[LongLiveCHIEF]

related #5

[neil-pozetroninc]

Hey @LongLiveCHIEF, that sounds like a super useful idea!

If I understand correctly though, it would mean that get-latest-release would no longer only be returning the one and only latest release. If we go ahead with this idea I would like to propose that we fork this action and create another sibling action which would get "releases".

I'll then port the semver functionality to this action so that this action gets the latest single release that matches the semver and point people in the README to the sibling action for getting a list of releases if that's their use case.

Does that sound like a good idea?

[LongLiveCHIEF]

I had the same thought, just didn't want to preempt you.

[dannysauer]

Did the fork happen, or did everyone fall down a well? :)

[LongLiveCHIEF]

Moved it here: HackerHappyHour/tagging-strategy#37 ...then came the well.

…

On Thu, Jun 10, 2021, 5:17 PM Danny Sauer ***@***.***> wrote: Did the fork happen, or did everyone fall down a well? :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZBLAOJM3D3KJQPUOMU52TTSE2WBANCNFSM4P7VZMSA> .