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

Add workflow to automatically update binary compatibility checks #3242

Merged
merged 1 commit into from
May 5, 2023

Conversation

jackkoenig
Copy link
Contributor

I developed this on a little mini repo, I'm pretty sure it works: https://github.com/jackkoenig/test-on-release

Now whenever a release is created, this action will automatically open PRs to check binary compatibility on any stable branches that include the particular tag. This does include main which can be useful for using main as a major release branch.

Contributor Checklist

  • [NA] Did you add Scaladoc to every public function/method?
  • Did you add at least one test demonstrating the PR?
  • Did you delete any extraneous printlns/debugging code?
  • Did you specify the type of improvement?
  • Did you add appropriate documentation in docs/src?
  • Did you request a desired merge strategy?
  • Did you add text to be included in the Release Notes for this change?

Type of Improvement

  • Internal or build-related (includes code refactoring/cleanup)

Desired Merge Strategy

  • Squash

Release Notes

Reviewer Checklist (only modified by reviewer)

  • Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
  • Did you mark the proper milestone (Bug fix: 3.5.x or 3.6.x depending on impact, API modification or big change: 5.0.0)?
  • Did you review?
  • Did you check whether all relevant Contributor checkboxes have been checked?
  • Did you do one of the following when ready to merge:
    • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
    • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

@jackkoenig jackkoenig added the Internal Internal change, does not affect users, will be included in release notes label May 5, 2023
@jackkoenig jackkoenig merged commit bc4d8f9 into main May 5, 2023
@jackkoenig jackkoenig deleted the automated-mima-updating branch May 5, 2023 03:46
@jackkoenig jackkoenig added this to the 5.x milestone May 5, 2023
@mergify mergify bot added the Backported This PR has been backported label May 5, 2023
mergify bot pushed a commit that referenced this pull request May 5, 2023
mergify bot added a commit that referenced this pull request May 5, 2023
…) (#3246)

(cherry picked from commit bc4d8f9)

Co-authored-by: Jack Koenig <koenig@sifive.com>
@jackkoenig
Copy link
Contributor Author

@Mergifyio backport 3.6.x

@mergify
Copy link
Contributor

mergify bot commented May 5, 2023

backport 3.6.x

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request May 5, 2023
jackkoenig added a commit that referenced this pull request May 5, 2023
…) (#3249)

(cherry picked from commit bc4d8f9)

Co-authored-by: Jack Koenig <koenig@sifive.com>
@sequencer sequencer mentioned this pull request Jun 20, 2023
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backported This PR has been backported Internal Internal change, does not affect users, will be included in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant