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

feat(release-pr): sign release-plz commit #956

Merged
merged 3 commits into from
Sep 11, 2023
Merged

feat(release-pr): sign release-plz commit #956

merged 3 commits into from
Sep 11, 2023

Conversation

marcoieni
Copy link
Member

@marcoieni marcoieni commented Sep 11, 2023

fix #955

@marcoieni marcoieni merged commit 4404a14 into main Sep 11, 2023
@marcoieni marcoieni deleted the sign-commit branch September 11, 2023 13:43
@release-plz release-plz bot mentioned this pull request Sep 11, 2023
@marvin-hansen
Copy link

marvin-hansen commented Sep 11, 2023

Thank you for the fast resolution @marcoieni 🙌

I'm using it here.

https://github.com/deepcausality-rs/deep_causality

I know this sounds really dumb, but when you've issued a new release, do I have to update manually or is the default configuration pulling the latest?

The thing is, after setup I've never touched the configuration again because it just worked and for all other actions DependaBot checks once a week for new versions. Take it as a compliment.

@marcoieni
Copy link
Member Author

By default your ci pulls the latest v0.5.x so you won't need to change anything.
I still have to release the new version. I will do it today probably

@marvin-hansen
Copy link

marvin-hansen commented Sep 11, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants