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

chore: update release steps to keep crossplane-runtime renovate config up to date #34

Merged
merged 1 commit into from
Dec 19, 2024

Conversation

jbw976
Copy link
Member

@jbw976 jbw976 commented Dec 19, 2024

This PR adds some new instructions to avoid the scenario we just manually fixed in crossplane-runtime with crossplane/crossplane-runtime#797. The Renovate config had fallen behind a couple releases, so we should be able to stay on top of it in future releases with these extra steps.

@@ -28,7 +28,7 @@ examples of each step, assuming release vX.Y.0 is being cut.
- [ ] Confirm that all security/critical dependency update PRs from Renovate are merged into `main`
- https://github.com/crossplane/crossplane-runtime/pulls?q=is%3Apr+is%3Aopen+label%3Aautomated
- [ ] Created the release branch using the [GitHub UI][create-branch].
- [ ] (On the **Main** Branch) Created and merged an empty commit with `git commit --allow-empty -s -m "Empty commit after release-X.Y"`
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no more need for an empty commit to crossplane-runtime main because the renovate config PR will serve the same purpose (to move main along ahead of the tag that's in the release branch)

@jbw976 jbw976 merged commit 1b1a404 into crossplane:main Dec 19, 2024
1 check passed
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