Skip to content

Conversation

savente93
Copy link
Contributor

Hi all, took a while, but here is the MVP PR. I've tested it on a dummy repository and there it works quite well (for the limited scope I tested it in). There are still some kinks to be worked out, in particular I'm hoping we can resolve most if not all of the limitations mentioned in the readme, but generally it's better to take small steps so I wanted to open a PR with the basic structure first. While the version logic might need some work yet, I think the basic structure is quite nice:

  1. each quarter the workflow should trigger a new release with the new release artifacts in this repo
  2. the action then pulls in that schedule, and does the filtering
  3. after that it opens a PR so people can inspect/adjust as necessary

Even though I've only worked on Pixi atm, I've also included a sketch of where to add other tools in case someone else has to look at it as well. Let me know what you think but for a first version, I think this is quite nice.

Cheers! 👋

The release_schedule workflow should create the artifacts on this
repository so other repositories can access it, and make sure we have a
paper trail
Action should create a PR with updated dependencies. Target branch and
tool to be used are configurable. Currently only pixi is supported but
it's good to make it possible to add other tools down the line
@savente93
Copy link
Contributor Author

The reason that the tests are failing is that this repo doesn't have a token with the right permissions. In addition I'm also pulling the artifact from my own repo where I did a release, so if this is accepted I'll change it over to pull the action from this repository, and the artifact will have to be released. I'm happy to help with all of this if anyone would like that

@savente93
Copy link
Contributor Author

Superseded by #5

@savente93 savente93 closed this Aug 14, 2025
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.

1 participant