Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cannot execute multiple times in same job #57

Closed
McManning opened this issue Apr 8, 2021 · 3 comments · Fixed by #63
Closed

Cannot execute multiple times in same job #57

McManning opened this issue Apr 8, 2021 · 3 comments · Fixed by #63
Labels
released

Comments

@McManning
Copy link

Describe the bug

Hi all - I have an action that runs semantic-release-action in two steps, first one does a dry run to grab release version information needed for my build steps and the second performs the actual release once all the build steps have completed.

The first run happens as expected, but the second will never execute. This is all that I get as an output:

Run cycjimmy/semantic-release-action@v2
  with:
  env:
    DOTNET_ROOT: C:\Users\runneradmin\AppData\Local\Microsoft\dotnet
    GITHUB_TOKEN: ***
added 323 packages in 10.813s

npm WARN prepare removing existing node_modules/ before installation

Workflow

This is the workflow for the project I'm testing with that fails to perform any action at the "Publish to GitHub" step - https://github.com/McManning/tmp-release-ci/blob/master/.github/workflows/publish.yml#L34-L38

Expected behavior

Deploys release to Github on the second run
@McManning
Copy link
Author

McManning commented Apr 8, 2021 •
edited

I tested this with a workflow that runs semantic-release-action twice (dry run first) and nothing else - got the same error.

Workflow file here: https://github.com/McManning/tmp-release-ci/actions/runs/729625406/workflow

@denouche
Copy link
Contributor

Hello,
Same thing for me here.
I want to run a dry-run step before my build, build my artifact, and then execute the release without the dry-run option. The second release step does not work.
I guess the warning npm WARN prepare removing existing node_modules/ before installation displayed the second time make the process stopping here: https://github.com/cycjimmy/semantic-release-action/blob/master/index.js#L11

denouche added a commit to denouche/semantic-release-action that referenced this issue Apr 29, 2021
@denouche
fix: use error loglevel for installing dependencies
ed6729b 
Because warnings during dependencies installation are not meants to make crash the release
Closes cycjimmy#57
@denouche denouche mentioned this issue Apr 29, 2021
Merged
5 tasks
github-actions bot pushed a commit that referenced this issue Apr 30, 2021
@semantic-release-bot
chore(release): 2.5.4 [skip ci]
1166472 
## [2.5.4](v2.5.3...v2.5.4) (2021-04-30)

### Bug Fixes

* use error loglevel for installing dependencies ([ed6729b](ed6729b)), closes [#57](#57)
@github-actions
Copy link

🎉 This issue has been resolved in version 2.5.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

gsmlg pushed a commit to gsmlg/semantic-release-action that referenced this issue Sep 10, 2021
@denouche @gsmlg
fix: use error loglevel for installing dependencies
404e484 
Because warnings during dependencies installation are not meants to make crash the release
Closes cycjimmy#57
gsmlg pushed a commit to gsmlg/semantic-release-action that referenced this issue Sep 10, 2021
@semantic-release-bot @gsmlg
chore(release): 2.5.4 [skip ci]
5549864 
## [2.5.4](cycjimmy/semantic-release-action@v2.5.3...v2.5.4) (2021-04-30)

### Bug Fixes

* use error loglevel for installing dependencies ([ed6729b](cycjimmy@ed6729b)), closes [cycjimmy#57](cycjimmy#57)
gsmlg pushed a commit to gsmlg/semantic-release-action that referenced this issue Sep 10, 2021
@denouche @gsmlg
fix: use error loglevel for installing dependencies
887368a 
Because warnings during dependencies installation are not meants to make crash the release
Closes cycjimmy#57
gsmlg pushed a commit to gsmlg/semantic-release-action that referenced this issue Sep 10, 2021
@semantic-release-bot @gsmlg
chore(release): 2.5.4 [skip ci]
4412739 
## [2.5.4](cycjimmy/semantic-release-action@v2.5.3...v2.5.4) (2021-04-30)

### Bug Fixes

* use error loglevel for installing dependencies ([ed6729b](cycjimmy@ed6729b)), closes [cycjimmy#57](cycjimmy#57)
github-actions bot pushed a commit to gsmlg/semantic-release-action that referenced this issue Sep 13, 2021
@semantic-release-bot
chore(release): 3.0.0 [skip ci]
ff44dd7 
# [3.0.0](v2.5.3...v3.0.0) (2021-09-13)

### Bug Fixes

* Add Workspace dir ([956267b](956267b))
* Always show output ([f642a0a](f642a0a))
* Fix action. ([d27b478](d27b478))
* Fix bug. ([47a9a21](47a9a21))
* Fix chdir. ([bcd53ea](bcd53ea))
* Fix extra_plugins. ([56ca1ae](56ca1ae))
* Fix extra_plugins. ([3cd6ca2](3cd6ca2))
* Fix missing @semantic-release/exec. ([f926412](f926412))
* Fix missing semantic-release-monorepo. ([ed8a67f](ed8a67f))
* Fix NPM_TOKEN. ([2b9be2c](2b9be2c))
* Fix NPM_TOKEN. ([9417d4f](9417d4f))
* Fix token. ([8caf5e5](8caf5e5))
* Update args. ([dcb8a3b](dcb8a3b))
* **deps:** Fix release config. ([ec21719](ec21719))
* use error loglevel for installing dependencies ([887368a](887368a)), closes [cycjimmy#57](https://github.com/gsmlg/semantic-release-action/issues/57)
* Use semantic release api to change cwd. ([293b31c](293b31c))
* Use semantic release api to change cwd. ([3a5638d](3a5638d))
* Using node14 is not support yet, back to node12. ([d587308](d587308))

### Features

* Add name and remove extends. ([c5005bb](c5005bb))
* Add working-directory. ([c5cf3a7](c5cf3a7))
* Add working-directory. ([ed1d114](ed1d114))
* Change to node 14. ([0db5053](0db5053))
* Change to semantic release monorepo. ([23dd334](23dd334))
* Use self hosted release. ([97821e2](97821e2))
* Use v3 release. ([36a0c87](36a0c87))
* **release:** Rebuild. ([2300e41](2300e41))

### BREAKING CHANGES

* The extends option has been removed.
Add name and working-direcotry to monorepo.
Only support monorepo and non javascript repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: use error loglevel for installing dependencies denouche/semantic-release-action
2 participants
@McManning @denouche