-
Notifications
You must be signed in to change notification settings - Fork 236
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
feat(action): use composite action for semantic release #692
feat(action): use composite action for semantic release #692
Conversation
Maybe problem arise when used in docker container or on windows runner. Was this supported before ? |
Looks good just from reading through, couple of questions but I'll review in more depth when I can run this on a project too. |
I don't understand how I expect Build relying on More important than that, I identified a bug in my version for GITHUB_OUTPUT variable. Look at the env in Master: https://github.com/zckv/semantic-versioning-example/actions/runs/6233057268/job/16917466927 Branch: https://github.com/zckv/semantic-versioning-example/actions/runs/6222835609/job/16887537001 I will work on correcting that. |
This correct the outputs set to none problem.
I forgot to add the Now this seems to work fine. |
Should no longer be needed once python-semantic-release/python-semantic-release#692 is merged. Signed-off-by: Felix Kaechele <felix@kaechele.ca>
…a_composite_action
4648d87
into
python-semantic-release:master
I appreciate the updates hoping to make this action more efficient and not break backwards compatibility, but unfortunately this update still broke our workflows. For anyone else potentially running into an error that looks like this:
You need to add the
This is on a self-hosted actions runner, on Ubuntu 20.04, with python 3.10 installed. |
Hello @venachescu 👋 I'm sorry that it broke your workflows, I didn't consider the self-hosted runners option. Python is a dependency of this action. Before, the problem didn't happen because python was installed within the Dockerfile. As GitHub Hosted runners have python3.10 per default, I thought python3 interpreter would be available at all time. Should I make a new branch to enhance the behavior of this error? |
Hey @venachescu - I should add my apologies too, I'd also glossed straight over the question "what if there's no Python entirely?" If you don't manage to get to it today @zckv I'll modify the |
I don't think there is a better way of handling this than to display a better error. And adding documentation. Another method is to install a python3 (>=3.7) interpreter on the machine, but that is too risky from my point of view. According to GitHub documentation, self-hosted runners can run on many different platforms. I'm not sure if the new version can run on RHEL7, as the default interpreter is python3.6. I would document that this action does not officially support self-hosted runners. |
Or maybe reverting the changes and do a separate action, like python-semantic-release/upload-to-gh-release ? |
This reverts commit 4648d87.
I reverted the changes for now - let's make a new PR. Good point about self-hosted runners. There's a lot of different OSs. I'd be more inclined to take the stance that we support self-hosted with some prerequisites, that's fairly normal when taking on the overhead of self-hosting, but it needs to be documented & released as breaking. We shouldn't be installing an interpreter as part of the action, and Windows is going to be problematic (I just tested). Should be doable though 🤞 |
Co-authored-by: Bernard Cooke <bernard-cooke@hotmail.com>
Hi @zckv and @bernardcooke53 - no worries about the broken workflows, and thanks for jumping on this so quickly! We have a slightly unusual setup where python (version 3.10) is installed on the self-hosted runners, but it's managed by pyenv and not installed using the using Either way, having the |
Later versions reverted python-semantic-release/python-semantic-release#692 which breaks builds on Python projects requiring a newer interpreter than 3.10, which their container uses. Should be fine to update after python-semantic-release/python-semantic-release#741 is merged again. Signed-off-by: Felix Kaechele <felix@kaechele.ca>
Co-authored-by: Bernard Cooke <bernard-cooke@hotmail.com>
Resolves: #692 Co-authored-by: Bernard Cooke <bernard-cooke@hotmail.com>
The fork simply reintroduces python-semantic-release/python-semantic-release#692 Signed-off-by: Felix Kaechele <felix@kaechele.ca>
For issue #685
Make a venv environment in ~/semantic-release folder, install python-semantic-release with pip.
Dependencies are used in github
env
keyword.Changed default git user mail from
"github-actions@github.com"
to"actions@github.com"
to reflect the docs.Removed
--global
git option to avoid breaking user environment.This will probably break
tool.semantic-release.build_command
. This should not break standard usage.I tested this on a personal project, it worked fine.