π The same declaration but different selectors or states should not be considered a conflict
1aron opened this issue Β· comments
π This issue has been resolved in version 2.0.0-rc.20 π
The release is available on:
- GitHub release
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
- npm package (@rc dist-tag)
Your semantic-release bot π¦π