Skip to content

Conversation

@MridulS
Copy link
Member

@MridulS MridulS commented Feb 10, 2025

No description provided.

Copy link
Member

Choose a reason for hiding this comment

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

Is this enough? The version is also stored in the METADATA file inside the wheel. So if you don't update that, does the resolve get into trouble?

Copy link
Member Author

Choose a reason for hiding this comment

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

I want to say yes, as the problem is just the version number in the pin in nightly.txt and we aren't comparing 2 scipp dev wheels, pip installs the wheel just fine too.

@MridulS MridulS enabled auto-merge (squash) February 10, 2025 14:16
Copy link
Member

@jl-wynen jl-wynen left a comment

Choose a reason for hiding this comment

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

Let's try it out

@MridulS MridulS merged commit 7dd1480 into main Feb 10, 2025
4 checks passed
@MridulS MridulS deleted the nightly_name branch February 10, 2025 14:30
MridulS added a commit to MridulS/scipp that referenced this pull request Feb 11, 2025
MridulS added a commit that referenced this pull request Feb 11, 2025
)

* MAINT: Use SETUPTOOLS_SCM_PRETEND_VERSION to set nightly version

* Revert " MAINT: Upload nightlies with dev0 to keep the pin stable downstream  (#3652)"

This reverts commit 7dd1480.

* Remove pull_request trigger from nightly release workflow
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.

3 participants