Skip to content

fix: exclude-newer results in multiple build events#5882

Draft
pavelzw wants to merge 1 commit intoprefix-dev:mainfrom
pavelzw:pixi-build-retrigger
Draft

fix: exclude-newer results in multiple build events#5882
pavelzw wants to merge 1 commit intoprefix-dev:mainfrom
pavelzw:pixi-build-retrigger

Conversation

@pavelzw
Copy link
Copy Markdown
Collaborator

@pavelzw pavelzw commented Apr 13, 2026

Description

Fixes #5885

How Has This Been Tested?

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: {e.g., Claude, Codex, GitHub Copilot, ChatGPT, etc.}

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added sufficient tests to cover my changes.
  • I have verified that changes that would impact the JSON schema have been made in schema/model.py.

@pavelzw pavelzw force-pushed the pixi-build-retrigger branch from ee8d07a to 1f2de01 Compare April 13, 2026 12:15
@pavelzw pavelzw force-pushed the pixi-build-retrigger branch from 1f2de01 to 97ab25b Compare April 13, 2026 12:16
@pavelzw
Copy link
Copy Markdown
Collaborator Author

pavelzw commented Apr 13, 2026

after #5607 this won't be an issue anymore

@hunger
Copy link
Copy Markdown
Contributor

hunger commented Apr 13, 2026

Do you think it would be a good test case to add anyway?

@pavelzw
Copy link
Copy Markdown
Collaborator Author

pavelzw commented Apr 13, 2026

yes, will merge this after the v7 lockfile pr goes through

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.

pixi-build with exclude-newer results in multiple builds after consecutive pixi installs

2 participants