cicd(versioning): Automate proper version tagging in the bouncer.go that is reported to Crowdsec LAPI#314
Conversation
…hat is reported to Crowdsec LAPI
|
Maybe create a version.go at the root project and import/in the same package and update this file instead of sed bouncer.go |
|
kinda meh, but here You go. |
|
Hey - will this be merged for next release? :) |
|
Should work now. Still get an error in my repo ci, but it's referencing this repo's cache for the package. |
Removed the verification step after updating the version and modified the commit message to include an emoji.
|
I just try to publish a new version and the repo policy block the update. |
|
Just tested on my fork - worked flawlessly. |
|
I tested too but repo policy prevent push directly on main branch... |
|
Yeah - You need to add "github-actions[bot]" user as an exception to this if You haven't done that already. Docs: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule Maybne this isn't an enterprise solution, but a fully automatic one :) |
…plugin to v1.5.1 ##### [\`v1.5.1\`](https://github.com/maxlerebourg/crowdsec-bouncer-traefik-plugin/releases/tag/v1.5.1) #### What's Changed - ✨ cicd: Automate proper version tagging in the bouncer.go that is reported to Crowdsec LAPI by [@Shadoweee77](https://github.com/Shadoweee77) in [#314](maxlerebourg/crowdsec-bouncer-traefik-plugin#314) #### New Contributors - [@Shadoweee77](https://github.com/Shadoweee77) made their first contribution in [#314](maxlerebourg/crowdsec-bouncer-traefik-plugin#314) **Full Changelog**: <maxlerebourg/crowdsec-bouncer-traefik-plugin@v1.5.0...v1.5.1>
…plugin to v1.5.1 ##### [\`v1.5.1\`](https://github.com/maxlerebourg/crowdsec-bouncer-traefik-plugin/releases/tag/v1.5.1) #### What's Changed - ✨ cicd: Automate proper version tagging in the bouncer.go that is reported to Crowdsec LAPI by [@Shadoweee77](https://github.com/Shadoweee77) in [#314](maxlerebourg/crowdsec-bouncer-traefik-plugin#314) #### New Contributors - [@Shadoweee77](https://github.com/Shadoweee77) made their first contribution in [#314](maxlerebourg/crowdsec-bouncer-traefik-plugin#314) **Full Changelog**: <maxlerebourg/crowdsec-bouncer-traefik-plugin@v1.5.0...v1.5.1>
|
Hey @maxlerebourg - did You get it working? :) |
|
Not really, and you ? |
|
Oh - I can't :) It's done in the repository settings. You need to be an owner or maintainer. |
|
Yes, but if you have the same setup as this repo, you can try to reproduce it on your side. I don't find the option to whitelist the github-action[bot] |
|
Sadly I don't have the same setup - it doesn't fork over. I've linked the docs, and the GitHub's own copilot does really well with their official docs. Regarding this rule the only downside I can see is someone could push a bad command for the CI worker to execute, but than again it would have to be accepted manually and merged to take effect on the main branch. The only other way around this that I know of is to bump the version manually in the file. |
2 participants
In reference to #287 - this is an automatic way. Works fine on my forked repo. I hope it will finally report a correct version so I can know which machines to update at a glance :)