marvinpinto / actions Goto Github PK

View Code? Open in Web Editor NEW

128.0 3.0 70.0 1.58 MB

A Collection of GitHub Actions

License: MIT License

JavaScript 10.59% TypeScript 84.15% Shell 5.26%

github-actions ci keybase release-automation ssm secrets

actions's People

Contributors

Stargazers

Watchers

Forkers

thielepaul welldsagl seramade 6paklata jhhughes asbjornu arjunan4 hwoarang etra0 technovangelist uly6 folex arrowplum vasyau1960 eyal0 mingjun97 cedriking turleypol grengojbo techno-sam sorenisanerd pandademic dolalla tkrishnanand fatash89 okias alexkb0009 onpon4 moloch-- pzhlkj6612 qudini tony-fr evermind-zz mgm87 navarr lauravuo ziflin dwkns rafalohaki asinkxcoswt necoarcdotcom geolaz labithiotis maggie44 balena-io-experimental coffee2bits jjliggett unl0ck shannah diillson sede-open aarondarwish soonlai814 crowbarmaster timcosgrove happypoo35 moontai0724 hjemmel vnprogramming enase itsusinn pegler asml-actions-validation mathieucarbou gutpuncher

actions's Issues

automatic_release_tag appears to be required

I honestly just want to bump my version from the previous release, however every time I use this action, I keep getting the same error message:

##[error]The parameter "automatic_release_tag" was not set and this does not appear to be a GitHub tag event. (Event: refs/heads/master)
  (node:3970) UnhandledPromiseRejectionWarning: Error: The parameter "automatic_release_tag" was not set and this does not appear to be a GitHub tag event. (Event: refs/heads/master)
      at /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:224244
      at Generator.next (<anonymous>)
      at /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:221786
      at new Promise (<anonymous>)
      at n (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:221531)
      at Object.t.main (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:223199)
      at Object.<anonymous> (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:221441)
      at r (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:124)
      at /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:923
      at Object.<anonymous> (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:933)
  (node:3970) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
  (node:3970) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit

The README shows that I don't need automatic_release_tag, but when I omit it or set it to null, I get that error.

Here is my full build file: https://pastebin.com/yaA3iFWj

Error uploading to https://github-production-release-asset-2e65be.s3.amazonaws.com: 403

I get an error while trying to upload artifacts to a release. Not sure what other info will help but let me know I would be happy to provide it. The project I'm working on is here.

including title of GitHub issue in changelog

We just started using this for automatic version, and it's great!

However, I was hoping that it would do one more thing to make the auto-generated changelog more easily skimmable by users. Whenever a commit closes an issue (via a phase such as "closes #303"), it would be great if the changelog could include the title of that issue.

Here's a release where I've manually added the title of three issues that were closed (issues 327, 328, 329):

https://github.com/UC-Davis-molecular-computing/scadnano/releases/tag/v0.9.3-1

But the draft that was generated did not have the Issue titles for issues 327, 328, 329:

Of course, the link to the issue is there for the user to go read if they want. But if the title were included, that would help them figure out whether it's relevant to them and whether they ought to go read it.

Generate changelog even when specifying a semver compatible automatic_release_tag

First, I'd like to thank you for the great work and functionality provided by this action.

I'd like to use this action within a workflow where I first generate the semver tag using other means, then use this action to create the release and upload the assets.

With that in mind, I was wondering if it would be possible to pass the newly generated tag name in the automatic_release_tag arg and still have your action generate the changelog with all commits since the previous semver compatible tag.

Currently, if the automatic_release_tag is provided, the action does not search for the previous semver compatible tag, therefore no commits are found and no changelog is generated.

Thanks!

changelog for same branch

Hi,
I got a changelog always for differences compared to default branch. Is there any way to get changelog for changes in same branch till last release?

I have a kernel repo where i build each LTS version (4.14, 4.19, 5.4, 5.10) on push

https://www.github.com/frank-w/BPI-R2-4.14

If this is not possible,can i disable the changelog feature?

Prevent update release if files didn't change

It would be a nice-to-have feature if this action had an option to prevent a release update if none of the attached assets were changed compared to a previous release.

When 'automatic_release_tag:' is not latest, commit formatting errors occur

Thanks for this action, making my life much easier.

Ran across a slight issue. When running the below with automatic_release_tag: "develop" on a pre-release the formatting of the Commit details is lost. Here is an example: https://github.com/LearnersBlock/learners-block/releases

        name: Test process
        uses: "marvinpinto/[email protected]"
        with:
          repo_token: "${{ secrets.GITHUB_TOKEN }}"
          automatic_release_tag: "develop"
          prerelease: true
          title: "Development Build"
          files: |
            *.zip

When I run this with automatic_release_tag: "latest" it works fine.

        name: Test process
        uses: "marvinpinto/[email protected]"
        with:
          repo_token: "${{ secrets.GITHUB_TOKEN }}"
          automatic_release_tag: "latest"
          prerelease: true
          title: "Development Build"
          files: |
            *.zip

Using marvinpinto/[email protected]

action-automatic-releases export urls?

Could let action-automatic-releases export releases's urls? I just want action send me a email contains these urls. So I don't need sign in github to get this urls.

Error: Cannot read property 'trim' of undefined

Surprisingly, this action which used to work started to fail today, using v1.1.0 (using sha).

Generating changelog
  Found 1 pull request(s) associated with commit 234cefd9e510cd6db5ef9d1d9bed6f882d8b2363
  Error: Cannot read property 'trim' of undefined
  (node:2477) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'trim' of undefined
      at e.exports (/home/runner/work/_actions/marvinpinto/action-automatic-releases/10bdce64abdb4558a2ee6983192242be40d631d8/dist/index.js:1:562792)
      at Function.e.exports.sync (/home/runner/work/_actions/marvinpinto/action-automatic-releases/10bdce64abdb4558a2ee6983192242be40d631d8/dist/index.js:1:561270)
      at /home/runner/work/_actions/marvinpinto/action-automatic-releases/10bdce64abdb4558a2ee6983192242be40d631d8/dist/index.js:1:211488
      at Generator.next (<anonymous>)
      at s (/home/runner/work/_actions/marvinpinto/action-automatic-releases/10bdce64abdb4558a2ee6983192242be40d631d8/dist/index.js:1:210383)
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
  (node:2477) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
  (node:2477) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Alternative to hashed asset names

Hey, I'm using your automatic-releases action. I'm using it with the tag set to latest so it replaces the release and I notice that uploads quite often fail with:

(Validation Failed: {"resource":"ReleaseAsset","code":"already_exists","field":"name"})

This seems quite common (it happens with this https://github.com/actions/upload-release-asset too).

Your current solution is to add a hash to the filename which works however I want to be able to access the release assets at a known url so it would be better if they uploaded with their original name.

Do you know why this error happens and if there is a way to upload with the same name?

Thanks for any response and thanks for making the action.

Error: Unable to process command ::set-env with [email protected]

I haven't had any issue using this action previously, though I recently switched from @latest to @1.1 of the action. This morning, I made unrelated changes to the workflow and it gave me the error below.

https://github.com/ngdenterprise/neo-blockchaintoolkit-library/runs/2168092633?check_suite_focus=true

Error: Unable to process command '::set-env name=AUTOMATIC_RELEASES_TAG,::1.0.30-preview' successfully.
Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

Creating release with this does not trigger my other workflow which is dependent on release published event.

I have two workflow,

One is for building and deploying the application, and it is triggered by Github release feature, I check if the release is pre-release or not, if pre-release then I build beta version of my app and deploy otherwise stable version.

Another is with this action which is triggered by Tag Push, I create tag from my IDE using name like v5.5.1-beta or v5.5.2, in this workflow, I decide whether to create pre-release or stable release.

That's how workflows are installed.
but the Tag push workflow with this action creates a release in Github but my Build and Deploy workflow doesn't run on the create release event triggered by this action.

Thanks.

Action: marvinpinto/action-automatic-releases

Possible to omit the changelog or supply and alternate description?

Hello - this is a really useful action. We have some cases where we do not want the automatic changelog to be created. Is it possible to provide a parameter to disable this, and/or provide a custom value that would be used as description? Thanks.

Set-env is being deprecated

Just a heads up that github is deprecating set-env and this action may break as a result:

Allow duplicate releases

In some projects I manage, releases and tags are created on GitHub.com, but I would still want to upload release assets automatically when on: tags is triggered.

It would, therefore, be great if action-automatic-releases had an allow_duplicates (or similar) field that could be set to true to allow a release to already exist, while still performing all the other tasks it currently does, such as uploading assets to the release.

Load error: Unexpected value 'description'

In job setup...

Download action repository 'marvinpinto/[email protected]'
##[error]marvinpinto/action-automatic-releases/v1.0.0/action.yml (Line: 27, Col: 5): Unexpected value 'decription'
##[error]marvinpinto/action-automatic-releases/v1.0.0/action.yml (Line: 27, Col: 5): Unexpected value 'decription'
##[error]Fail to load marvinpinto/action-automatic-releases/v1.0.0/action.yml

avoid security issue

The https://github.com/marvinpinto/action-automatic-releases action fails with:

Unable to process command '::set-env name=AUTOMATIC_RELEASES_TAG,::v2.2.5-1' successfully.

due to the enforcement of the security mech due to GHSA-mfwh-5m23-j46w
can you update the actions/code lib?

TIA

Allow regexp for release tags

Hello,

First let me say that I find this action super useful :) saves me a lot of time writing changelogs myself. Thank you for that

If I understand the action correctly, the generated changelog will always been between the current semver compatible tag and the previous one. So in the following scenario

1.0.0 <-- previous release tag
1.0.1-beta
1.0.1-rc
1.0.1 <-- latest release tag

The changelog for 1.0.1 will only show the commits since 1.0.1-rc. Would it be possible to allow some kind of regexp so I can configure the action to generate changelogs between tags that match, say, [0-9]+.[0-9]+.[0-9]+ for example?

Thank you

Error: Resource not accessible by integration

I got an error from the release action.

Generating release tag
  Attempting to create or update release tag "latest"
  Could not create new tag "refs/tags/latest" (Resource not accessible by integration) therefore updating existing tag "tags/latest"
  Error: Resource not accessible by integration
  (node:2449) UnhandledPromiseRejectionWarning: HttpError: Resource not accessible by integration
      at /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:357542
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
  (node:2449) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
  (node:2449) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Assets are uploaded as 34 byte

Hello, @marvinpinto
Why are assets uploaded as 34 bytes since v0.2.1?

Option to disable changelog

I would like to see an option to disable the output of the changelog to the release notes.
I have another action, which generates a changelog, which fits our requirements.

automatic-releases not writing breaking changes properly

It is the text after "BREAKING CHANGE" that should be listed in Breaking Changes section, not the commit message.

Message:

feat: Allow custom separator

BREAKING CHANGE: some breaking change.

Expected:

## Breaking Changes

- some breaking change.

## Features

- Allow custom separator

Got:

## Breaking Changes

- Allow custom separator

## Features

- Allow custom separator

Note: above example is not accurate, but can demonstrate the issue

Additional info

How about using notes field returned by conventional-commits-parser?

{ type: 'feat',
  scope: 'ng-list',
  subject: 'Allow custom separator',
  merge: null,
  header: 'feat(ng-list): Allow custom separator',
  body: 'bla bla bla',
  footer: 'BREAKING CHANGE: some breaking change.\nThanks @stevemao',
  notes:
   [ { title: 'BREAKING CHANGE',
       text: 'some breaking change.\nThanks @stevemao' } ],
  references: [],
  mentions: [ 'stevemao' ],
  revert: null }

Error due to github changes

I started to get this error today

Download action repository 'marvinpinto/[email protected]'
##[error]marvinpinto\action-automatic-releases\v1.0.0\action.yml (Line: 27, Col: 5): Unexpected value 'decription'
##[error]marvinpinto\action-automatic-releases\v1.0.0\action.yml (Line: 27, Col: 5): Unexpected value 'decription'
##[error]Fail to load marvinpinto\action-automatic-releases\v1.0.0\action.yml

How to automate release from multiple GitHub CI jobs?

I have a GitHub CI workflow that runs multiple VMs on multiple environments. Each one creates an executable artifact, for Windows, Linux, and Mac. I would like a single release to include files from all the different jobs. Is that possible?

run semverClean in searchForPreviousReleaseTag

Could be first run semverClean before find previous release tag? Usually the tag might be in the format like v1.0.0 and semverClean is tool to get the correct semver 1.0.0.

Syntax error in action.yml

There is a small typo in packages/automatic-releases/action.yml.

##[error]marvinpinto/action-automatic-releases/latest/action.yml (Line: 27, Col: 5): Unexpected value 'decription'
See: https://github.com/libretro/mame/runs/942138167?check_suite_focus=true

Strange is that I got no error in my repo: https://github.com/tcamargo/mame/runs/941527950?check_suite_focus=true

Anyway, should be an easy fix.

Generating changelog: Cannot read property 'trim' of undefined

Hi,

I was trying out this action on this workflow and got an error during the generation of the changelog. This was the first time running this action. Prior to running it, I tagged 0f47f15ad738972fe7104645639aceb3da94aa21 as latest to reduce the number of commits taken into account for the changelog.

Generating changelog
  Adding commit "Bump MSTest.TestFramework from 2.0.0 to 2.1.0" to the changelog
  Adding commit "Bump Microsoft.NET.Test.Sdk from 16.4.0 to 16.5.0" to the changelog
  ##[error]Cannot read property 'trim' of undefined
  (node:3432) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'trim' of undefined
      at e.exports (D:\a\_actions\marvinpinto\action-automatic-releases\latest\dist\index.js:1:572296)
      at Function.e.exports.sync (D:\a\_actions\marvinpinto\action-automatic-releases\latest\dist\index.js:1:570888)
      at D:\a\_actions\marvinpinto\action-automatic-releases\latest\dist\index.js:1:222656
      at Generator.next (<anonymous>)
      at s (D:\a\_actions\marvinpinto\action-automatic-releases\latest\dist\index.js:1:221551)
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
  (node:3432) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
  (node:3432) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

tagged-release assets

Hi,
your action is super simple and works well, but unfortunately the upload of files as release assets doesn't seem to work anymore.

Add a body argument?

First of all thank you again for this GitHub Action. It is easy to use and works well.

This a feature request :)

Would it be possible to add a body argument to the automatic-release action? For example, if the body argument is defined then it's content would be used as body for the release instead of the changelog (e.g. here). While it is convenient to have a changelog generated automatically, for my use case it would make more sense to to have a custom message as the body of the release.

[automatic-releases] Error: Unexpected token y in JSON at position 0

From the automatic-releases action https://github.com/marvinpinto/action-automatic-releases

I'm giving a try to the action with the following parameters:

    - name: Create the snapshot release
      uses: marvinpinto/action-automatic-releases@latest
      with:
        repo_token: ${{ secrets.GITHUB_TOKEN  }}
        title: Snapshot ${{ env.SNAPSHOT_TAG }} build
        prerelease: yes
        automatic_release_tag: ${{ env.SNAPSHOT_TAG }}

But it ends with error:

2021-04-20T10:26:38.7214793Z ##[group]Run marvinpinto/action-automatic-releases@latest
2021-04-20T10:26:38.7215489Z with:
2021-04-20T10:26:38.7216971Z   repo_token: ***
2021-04-20T10:26:38.7217437Z   title: Snapshot 21w16a build 
2021-04-20T10:26:38.7217926Z   prerelease: yes
2021-04-20T10:26:38.7218409Z   automatic_release_tag: 21w16a
2021-04-20T10:26:38.7218870Z   draft: false
2021-04-20T10:26:38.7219228Z env:
2021-04-20T10:26:38.7219829Z   BUILD_TYPE: Release
2021-04-20T10:26:38.7220408Z   SNAPSHOT_TAG: 21w16a
2021-04-20T10:26:38.7220837Z ##[endgroup]
2021-04-20T10:26:38.8259101Z ##[error]Unexpected token y in JSON at position 0
2021-04-20T10:26:38.8284275Z (node:6279) UnhandledPromiseRejectionWarning: SyntaxError: Unexpected token y in JSON at position 0
2021-04-20T10:26:38.8285297Z     at JSON.parse (<anonymous>)
2021-04-20T10:26:38.8286812Z     at /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:213282
2021-04-20T10:26:38.8288225Z     at /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:213461
2021-04-20T10:26:38.8289509Z     at Generator.next (<anonymous>)
2021-04-20T10:26:38.8290635Z     at /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:211750
2021-04-20T10:26:38.8291442Z     at new Promise (<anonymous>)
2021-04-20T10:26:38.8292527Z     at s (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:211495)
2021-04-20T10:26:38.8293972Z     at Object.t.main (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:213025)
2021-04-20T10:26:38.8295504Z     at Object.<anonymous> (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:210868)
2021-04-20T10:26:38.8296933Z     at r (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:1:124)
2021-04-20T10:26:38.8300892Z (node:6279) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
2021-04-20T10:26:38.8303749Z (node:6279) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
2021-04-20T10:26:38.8386579Z Post job cleanup.

Verbose mode to see the exact API calls that are made

I would like to re-implement the following use of action-automatic-releases in Golang as part of a tool that does more than just upload to GitHub Releases.

For this it would be very useful to see the exact API calls action-automatic-releases makes (e..g, in curl syntax or something like that).

Is there a way to see them?

    - name: Release AppImage
      uses: marvinpinto/action-automatic-releases@latest
      with:
        title: AppImage
        automatic_release_tag: continuous
        prerelease: true
        draft: false
        files: |
          Akira*.AppImage*
        repo_token: ${{ secrets.GITHUB_TOKEN }}

Alternatively, can action-automatic-releases be somehow invoked from the command line, so that my Go-based tool can call it?

Add the ability to send customized notification/chat messages

For example:

- uses: "./packages/keybase-notifications/"
  with:
    message: "Hey there, world!"
    keybase_username: "${{ secrets.KeybaseUsername }}"
    keybase_paper_key: "${{ secrets.KeybasePaperKey }}"
    keybase_team_name: "${{ secrets.KeybaseTeamName }}"
    keybase_topic_name: "${{ secrets.KeybaseTopicName }}"

These would theoretically override any GitHub context, and be used to purely send out messages.

automatic release action renames my file.

i'm trying to release a zip file named this way:
FunTuna[$SHA].zip
where $SHA is a variable that holds the first seven characters of the commit-SHA

taking 41e4ebe as an SHA example....

I expected this filename:

FunTuna[41e4ebe].zip

I'm getting this:

FunTuna.41e4ebe.zip

how can i get the filename that i expect?

Possible bundling error in latest release

From a private build I just ran:

##[group]Determining release tags
(node:5148) UnhandledPromiseRejectionWarning: Error: Cannot find module './functions/valid'
Require stack:
- /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:797:15)
    at Function.Module._load (internal/modules/cjs/loader.js:690:27)
    at Module.require (internal/modules/cjs/loader.js:852:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at lazyRequire (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:20001:52)
    at Object.get [as valid] (/home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:20008:19)
    at /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:15642:42
    at Generator.next (<anonymous>)
    at /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js:15532:71
    at new Promise (<anonymous>)
##[error]Cannot find module './functions/valid'
Require stack:
- /home/runner/work/_actions/marvinpinto/action-automatic-releases/latest/dist/index.js
2019-12-25T19:25:55.0621785Z (node:5148) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
2019-12-25T19:25:55.0623192Z (node:5148) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Question about GITHUB_SUPER_TOKEN

In .github/workflows/pre-release.yml, Line 56, what is secrets.GITHUB_SUPER_TOKEN. When I try to use this in my fork, it doesn't work.

Title not used when set

Custom title is not set when using the title key and not using the automatic_release_tag.

https://github.com/mitm001/jme-ui/blob/0755c4c138613f98c49051a918ecb2f889e35429/.github/workflows/release.yml#L40-L56

https://github.com/mitm001/jme-ui/releases

Am I not using this correctly?

Generate changelog from latest non-pre-release

Hi, your automatic-releases action is great!

I use it to generate automatic master builds. However right now, because it builds every commit on master, the changelog is always just that one commit. I was curious if you had thought about adding an option to generate release notes starting from the most recent non-pre-release commit, or if you would be open to a PR implementing this.

action-automatic-releases@latest doesn't clean the commit list when executed inside a matrix job

This is my workflow
https://github.com/israpps/FreeMcBoot-Installer/blob/c06d4fc4fc54e4b6274c3eb1722f75151f456aeb/.github/workflows/compile-core.yml

Since I've implemented the matrix into my job the commit list isn't erasing the old commits.

Determining release tags step fails

Hello (and thanks for your time in this action):

I have found that release fails when tag doesn't conform with SemVer format x.y.z. I'm using Calver format like YYYY.MM[.PATCH] where Patch is optional. Whenever the tag is like YYYY.MM it fails with the following error:

Run marvinpinto/[email protected]
Initializing the Automatic Releases action
Determining release tags
  Error: The parameter "automatic_release_tag" was not set and the current tag "v2020.11" does not appear to conform to semantic versioning.

Here is my current step config:

...
      - name: Upload Release Assets
        uses: "marvinpinto/[email protected]"
        with:
          title: Release ${{ github.event.release.tag_name }}
          repo_token: ${{ secrets.GITHUB_TOKEN }}
          automatic_release_tag: ${{ github.event.release.tag_name }}
          prerelease: false
          files: |
            ./build_path/*
...

Thanks

Uploading artifacts that don't exist doesn't cause an error

I mistakenly didn't spell an artifact file correctly in the files argument to action-automatic-releases. I expected that there would be an error but instead, nothing happened and no assets were uploaded.

Use with @v1

Many other actions allow us to use syntax like

uses: marvinpinto/action-automatic-releases@v1

This is very useful when we don't want things to be broken by a major v2 upgrade, but still want to track bug fixes.

Possibility of changing author of release

I am not sure if this is possible; But for automatic-release; it would be very nice if I could fake my account as the author of the PR instead of github-actions. I am not sure if its already implemented (did not find any information as such in the documentation)

Allow specifying the previous tag when creating the changelog

As a release manager, I would like to have the changelog include everything for the current major release, not just the changes since the previous tag.

To accomplish this, it would be nice to have a configuration option that names the previous tag to use. If this option is present, then the generator would use that tag instead of the default behavior of finding it.

add files from artifacts as assets

i case of a build strategy matrix multiple files are relevant as assets.
It would be helpful if you are able to define filenames with a pattern from the artifacts who will be upload as assets.

example:
artifactfiles: |
*.bin

[email protected] not detecting the latest commit from git history

Hi,

I have a workflow where the first step is to update a project file (to update the version in the project) and a second step which does the github release.
The results i excepted is to have this new automatic commit tagged with a release from github, but that is not the case, what happens is that the previous commit to the automatic one is the one that gets tagged.

Here's my workflow: https://gist.github.com/rjga94/685bc79c2ca99c8863da5cc62ee887cf

Automatic releases: Allow custom commit sha

I have a workflow that has to commit some changes, as such the commit it builds changes compared to the one it was triggered on. It would be awesome to be able to set the tag on this commit instead of GITHUB_SHA.

option to upload assets to an existing release

I have a workflow that runs a matrix and creates releases for multiple platforms. But when I run it the release gets completely overwritten and I end up with release for only one platform.

I there an existing workaround for this?

Option to keep old releases

Hi.

I'm looking to see if there is a way to keep old releases attached to a tag, for example, we have a tag called "QA", and we want to be able to see the history of the builds that made it to QA and their changelog.

I don't see this option, and I feel like it would be useful for other people too.

Any ideas on how this could be done?

Thanks.

Failed to find artifact file

Hello, The action fails to find the uploaded artifact file to release.
I am attaching part of my .yml file below:

  ...
  Some Python Build and Test Job running on windows-latest which are working fine
  ...

    - name: Save EXE for a release
      uses: actions/upload-artifact@v2
      with:
        name: screenipy.exe
        path: .\dist\screenipy.exe

    - name: Release EXE
      uses: "marvinpinto/action-automatic-releases@latest"
      with:
        repo_token: "${{ secrets.GITHUB_TOKEN }}"
        draft: true
        prerelease: true
        automatic_release_tag: "latest"
        files: |
          screenipy.exe

automatic releases: tag being used instead of defined title

Despite setting the title property under with, the action still seems to prefer simply bumping the pushed tag to a release instead.

Usage:

  release:
    runs-on: ubuntu-latest
    needs: build
    steps:
      - name: Download Build Results
        uses: actions/download-artifact@v2
        with:
          name: libs
          path: buildfiles
        
      - name: Create Release
        uses: "marvinpinto/action-automatic-releases@latest"
        with:
          title: "Release ${{ github.event.release.tag_name }}"
          repo_token: "${{ secrets.GITHUB_TOKEN }}"
          prerelease: false
          files: |
            CHANGELOG.txt
            LICENSE.txt
            buildfiles/*

Example repository:
https://github.com/robotgryphon/mc-mod/blob/1.16.1/.github/workflows/gradle.yml