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

auto track ldmx-sw releases within CI testing #104

Open
tomeichlersmith opened this issue Sep 30, 2024 · 1 comment · May be fixed by #109
Open

auto track ldmx-sw releases within CI testing #104

tomeichlersmith opened this issue Sep 30, 2024 · 1 comment · May be fixed by #109

Comments

@tomeichlersmith
Copy link
Member

I've done something similar for updating the testing for denv: https://github.com/tomeichlersmith/denv/blob/main/.github/workflows/runner-dependabot.yml

The basic idea is

  • keep track of versions to be tested in some file that is not within the .github directory1
  • scheduled workflow that just looks to see if there was a release in the repo we are tracking and makes a PR on the version-tracking file if a new release has been made

I'd like to improve on this design a bit since instead of tracking multiple repos, I'd like to more finely test a single repo. With this in mind, I think an additional feature for the PR-creation is to bump patches while keeping major/minor releases.

Footnotes

  1. We have to keep the file outside of the .github directory since GitHub prevents actions from pushing changes to anything in that directory presumably to avoid actions changing their own code in a confusing or malicious way.

@tomeichlersmith
Copy link
Member Author

When doing this, I think I can also get around to refactoring the interop patches using patch files git diff > file && git apply file rather than an assortment of scripts.

@tomeichlersmith tomeichlersmith linked a pull request Feb 26, 2025 that will close this issue
5 tasks
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 a pull request may close this issue.

1 participant