Skip to content

Conversation

@Hofer-Julian
Copy link
Contributor

@Hofer-Julian Hofer-Julian commented Jan 20, 2026

Description

Release backends on every push on main to backends channel

EDIT: Only happens when relevant paths are touched

How Has This Been Tested?

I ran the following locally and it looked fine. But we'll only know for sure after merging:

pixi run generate-matrix | from json

AI Disclosure

  • This PR contains AI-generated content.
    • I have tested any AI-generated content in my PR.
    • I take responsibility for any AI-generated content in my PR.

Tools: Claude

Checklist:

  • I have performed a self-review of my own code

The recipe files had source paths pointing to pixi-build-backends/ instead
of the repository root where the crates/ directory and LICENSE file are
located.
@wolfv
Copy link
Member

wolfv commented Jan 20, 2026

Wouldn't it be better to only release when something changed in the backends?

Ok, that seems to be the case :)

@Hofer-Julian
Copy link
Contributor Author

Wouldn't it be better to only release when something changed in the backends?

Ok, that seems to be the case :)

Yeah, but to be fair, arguably we should also release if something changed in Pixi, since the backends depend on Pixi.

But then we would release a lot

@ruben-arts
Copy link
Contributor

Doing this on every merge to main is something I turned off in the backends repo because we're dealing with heavy queues.

What is the reason we would want this again?

@Hofer-Julian
Copy link
Contributor Author

Doing this on every merge to main is something I turned off in the backends repo because we're dealing with heavy queues.

What is the reason we would want this again?

So people can test latest changes easily.
This version is much more lightweight, so I feel confident in giving this approach another try

- "crates/pixi-build-rust/**"
- "crates/pixi-build-mojo/**"
- ".github/workflows/backends-release.yml"
pull_request:
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Remove that before merging.

Unless it's super fast, we should maybe also only release on tag

Copy link
Contributor

Choose a reason for hiding this comment

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

For easy testing you could make this labeled, e.g.:

on:
  pull_request:
    types: [ labeled ]

jobs:
  build:
    if: ${{ github.event.label.name == 'release:backends' }}

Just an idea that came to mind, not Merge blocking ;)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good idea!

@ruben-arts ruben-arts enabled auto-merge (squash) January 23, 2026 15:51
unit: false
- os: windows-latest
artifact: pixi-windows-x86_64
unit: false
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Why are unit tests not run on windows?

Copy link
Contributor

Choose a reason for hiding this comment

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

The original setup only ran it on ubuntu-latest. I don't see a reason to extend that to more OS's

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants