Skip to content

Conversation

Carreau
Copy link
Contributor

@Carreau Carreau commented Dec 1, 2020

It seem like setuptools scm can screw up and this should ensure we catch
that in CI before making the wheel.

@Carreau Carreau added this to the v2.6 milestone Dec 1, 2020
@codecov
Copy link

codecov bot commented Dec 2, 2020

Codecov Report

Merging #666 (c32a7a3) into master (34204b1) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #666   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           27        27           
  Lines        10093     10094    +1     
=========================================
+ Hits         10093     10094    +1     
Impacted Files Coverage Δ
zarr/__init__.py 100.00% <100.00%> (ø)

@Carreau
Copy link
Contributor Author

Carreau commented Dec 2, 2020

It seem like setuptools scm can screw up and this should ensure we catch
that in CI before making the wheel. We want to make sure to have a
runtime check for the version number as well as a check just after
building the wheel.

This seem to be due to `build` latest version, so i've pinned it for
now.
@Carreau
Copy link
Contributor Author

Carreau commented Dec 2, 2020

Ok, downgrading build to 0.4 seem to work for now, I'm going to merge and tag a 2.6.1, and work on a proper fix later.

@Carreau Carreau merged commit a5dfc3b into zarr-developers:master Dec 2, 2020
@Carreau Carreau deleted the triple-zero-check branch December 2, 2020 18:29
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.

2 participants