You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we are using cycjimmy/[email protected] in our release workflow https://github.com/geostyler/geostyler/blob/main/.github/workflows/release.yml#L23, which uses it's own version of semantic-release. Additionally, we have semantic-release listed as one of our devDependencies. When using the github action, the version listed in our devDependencies is not being used. So in order to avoid confusion, I would suggest we replace the actually not necessary github action with just a simple command (something alike npm run semantic-release). The benefit of this is that it is also possible to test semantic-release locally.
Example
No response
Alternatives
The alternative would be to remove semantic-release from the devDependencies, but then we would also lose the capability of testing our config locally.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
This issue was closed because it has been inactive for 14 days since being marked as stale. Feel free to reopen it at any time, if this issue is still relevant.
Description
Currently, we are using
cycjimmy/[email protected]
in our release workflowhttps://github.com/geostyler/geostyler/blob/main/.github/workflows/release.yml#L23, which uses it's own version of semantic-release. Additionally, we have semantic-release listed as one of our devDependencies. When using the github action, the version listed in our devDependencies is not being used. So in order to avoid confusion, I would suggest we replace the actually not necessary github action with just a simple command (something alike
npm run semantic-release
). The benefit of this is that it is also possible to test semantic-release locally.Example
No response
Alternatives
The alternative would be to remove semantic-release from the devDependencies, but then we would also lose the capability of testing our config locally.
Additional Context
No response
The text was updated successfully, but these errors were encountered: