Skip to content

pixi@0.45.0: upgrade #6702

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

Closed
wants to merge 2 commits into from
Closed

pixi@0.45.0: upgrade #6702

wants to merge 2 commits into from

Conversation

DeeliN221
Copy link

  • Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
  • I have read the Contributing Guide

@DeeliN221
Copy link
Author

#6695

Copy link
Contributor

Your changes do not pass checks.

pixi

  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate
  • Autoupdate Hash Extraction

add \\ for white space
@DeeliN221
Copy link
Author

/verify

Copy link
Contributor

Your changes do not pass checks.

pixi

  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate
  • Autoupdate Hash Extraction

@aliesbelik
Copy link
Contributor

Duplicates #6558.

@DeeliN221
Copy link
Author

@aliesbelik what do you mean duplicates? The version number has changed and should we keep all future version updates in one PR?

@DeeliN221 DeeliN221 closed this by deleting the head repository Apr 15, 2025
@trim21
Copy link

trim21 commented Apr 17, 2025

@aliesbelik what do you mean duplicates? The version number has changed and should we keep all future version updates in one PR?

I think they mean we should get pixi merged into repo first, not update it before it added

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