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

Install release-plz to simplify release procedure #880

Open
jdrouet opened this issue Jun 7, 2024 · 2 comments · May be fixed by #884
Open

Install release-plz to simplify release procedure #880

jdrouet opened this issue Jun 7, 2024 · 2 comments · May be fixed by #884
Labels
domain: ci Anything related to Vector's CI environment

Comments

@jdrouet
Copy link
Contributor

jdrouet commented Jun 7, 2024

In order to simplify the release workflow, we should create a github action with release-plz.
This way, it will automagically open a PR to release with the adequate version.

@jdrouet jdrouet added the domain: ci Anything related to Vector's CI environment label Jun 7, 2024
@pront
Copy link
Collaborator

pront commented Jun 7, 2024

I have an untested draft PR to do that:
https://github.com/vectordotdev/vrl/pull/877/files

But feel free to explore other options :)

@jdrouet
Copy link
Contributor Author

jdrouet commented Jun 10, 2024

I don't know if you have tried release-plz. It's fairly simple, you put a github action configuration that will run on the main branch, that will open a PR to bump the version each time you do a change. It can detect breaking changes and knows what kind of version bump to make.
If you merge that PR, then the same github action configuration will create a github release and push the changes to crates.io.

I've been using it on some of my crates like serde-toml-merge and mrml.

I'll open a PR with the change but I'll need a crates.io token with write access to VRL.

@jdrouet jdrouet linked a pull request Jun 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: ci Anything related to Vector's CI environment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants