Automate your GitHub Actions Releases (with Semantic Release)!
Вставка
- Опубліковано 7 жов 2024
- In this final Episode, I show you how you can use semantic-release to easily automate your GitHub Action releases!
This is part of my series on how to create and release GitHub Actions.
The first episode on how to create GitHub Actions is found here: • Create your first GitH...
The second episode on how to (manually) release GitHub Actions is here:
• Release your first Git...
This is the repository used:
github.com/dav...
Here you can find semantic-release:
semantic-relea...
thanks for the slow and calmly explaining everything, I really like this video.
Thank you very much for the feedback, glad you enjoyed it!
Thank you! Not much people are commenting here but I found it helpful and well explained. Hoping to see more videos in the future that I could learn from!
Thank you very much for the feedback! Happy that my content was helpful for you - and I am already working on more! :)
awesome video.
i didnt know semantic release was a thing. I just integrated it into my project and versioning is so seamless now
Great work Dave! Keep making videos man! Your teaching style is really good and easy to follow. I'd even go as far as creating a full course. This information is really valuable and I appreciate you taking the time to put this together and publish it to UA-cam! Subbed!
Thank you very much for that feedback, really appreciate you took the time to let me know!! I will release more videos, soon!
Quite nice video Dave :)
Very well explained! Keep up with Github Action videos that really resembles real life scenarios! We need more of that :)
Thank you so much for the kind feedback! I'm already working on more! :)
Thanks Dave for the amazing post. I was setting up the semantic-release for the repo for work and got a lot of help from your video. 🎉 Subscribed!
Hey Brandon, super glad this was helpful to you! Thanks for the subscription, I will release some more videos pretty soon. :)
holy shit, this is good stuff.. been looking for a good semantic workflow. thanks dave
Glad I could be of help! :)
This is very well explained, I am going to try to use this amazing tool with a java-maven project, I hope it is not too different to make it work, thanks :)
Thank you very much, well explained
really learnt alot from this
Thanks Dave
Really good video! Thanks!
Hello great work! Can you share your vscode config/plugins? It looks amazing for a dev environment.
The best, thank you for this
thank you very much! How to push to a protected Branch, e.g. main. I get all the time "can't push tags to protected branch". I don't even know where to start
Hey there,
if the main branch is protected, you most likely will have to go through a pull request to make the changes. Or remove the branch protection from the repository settings, if this is a repository you own. Though I'd not recommend this for repositories which are used 'in production'.
thanks for video. I'm trying to do the same with release-it. It has 3 different plugins to bump a version, based on your preferences how you want to change it.
Thank you, keep it up.
Nice video. All the best for YouTubing👋
Thank you very much - glad you liked it!
Yes I am working on a react hook npm package. Have a look at it. Its in its basic version stage. Lot of stuffs to do.
Package name: zop-hooks
Just as a disclaimer, in the test.yml file, where you're defining the action steps, we don't have to include the npm run build step as seen on line 11 as it will slow down the release making process by quite a lot.
I wonder why it's there in the first place @Dave?
Thinking out loud I would imagine it's there to make sure the project build succeeds before making a release. If that's the case its fair as we all have different setups but I would argue that project building and build validation isn't the responsibility of semantic-release package.
Hi,
First of all: Thank you for the feedback!
Actually, the `npm run build` step is required in this case, as our action.yml references the dist/index.js, and thus, the test `./uses`-step in the test will execute that file.
If we'd leave it out, the test would potentially be conducted for an 'old' version of the repository as it would reference the `dist/index.js` from a previous build (e.g. in pull-requests, but also on main before the actual new dist/index.js is pushed). :)
Great video
Nice video, can I refer that version number while pushing Docker image in artifactory
Hi Dave thank you! But, how to sign a commit with semantic-release github actions?
How to update new version to package.json? it seams only change the dist files
You mean update the version field in the package.json?
If so, you probably need the npm plugin (is included in semantic-release, docs can be found here: docs.github.com/en/enterprise-server@3.7/admin/configuration/configuring-github-connect/about-github-connect#data-transmitted-by-individual-features-of-github-connect).
You would just need to make sure to set the option 'npmPublish' to false, as you most likely don't want to publish a GitHub Action to npm.
Not working for me. I make a fork your project and not work too. Nothing error but dont created a release version. Ah, i am using docker build to exec this command, this possible ? I am a test with steps 100% in cicd github actions and work.
toooooooooooo looooooonnnnngggggggg
Really helpful
can you prepare a complete lifecycle video of trunk based development using semantic-release
nice! and what about publishing to npm? and version in package.json? is it updated automatically?
Hi,
this video is specifically about releasing GitHub Actions, which don't require publishing to NPM.
However, with Semantic Release, what you are asking for is easily doable with the npm plugin: github.com/semantic-release/npm
@@davelosert thank you!
@@davelosert great library I was looking for something like that