Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Netlify autodeploy stoped working #55

Closed
fox1t opened this issue Oct 2, 2019 · 1 comment · Fixed by #57
Closed

Netlify autodeploy stoped working #55

fox1t opened this issue Oct 2, 2019 · 1 comment · Fixed by #57
Assignees
Labels
bug Something isn't working released

Comments

@fox1t
Copy link
Member

fox1t commented Oct 2, 2019

💥 Regression Report

Netlify autodeploy feature was working previously and now suddenly stopped to build.
https://app.netlify.com/sites/hospitalrun/deploys/5d93ad309e2585000cb0da45

To Reproduce

Steps to reproduce the behavior: Run build-storybook in CI/CD environment.

Expected behavior

Autodeploy the storybook on Netlify.

Your Environment

CI/CD

@matteovivona matteovivona added the bug Something isn't working label Oct 2, 2019
irvelervel pushed a commit that referenced this issue Oct 4, 2019
Specifies in storybook's webpack config a different tsconfig file which doesn't create definitions
and also maps @hospitalrun/components path. Removes now useless gitignore rules.

closes #55
ghost pushed a commit that referenced this issue Oct 4, 2019
## [0.4.5](v0.4.4...v0.4.5) (2019-10-04)

### Bug Fixes

* **toolchain:** adds custom tsconfig for storybook build ([951c5c0](951c5c0)), closes [#55](#55)
* **toolchain:** fixes issue with storybook not properly building ([70ce357](70ce357)), closes [#55](#55)
* **toolchain:** fixes issue with storybook not properly building ([b6708ae](b6708ae)), closes [#55](#55)
* **toolchain:** reverts mapped path due to netlify crash ([4f2d1fc](4f2d1fc)), closes [#55](#55)
@ghost
Copy link

ghost commented Oct 4, 2019

🎉 This issue has been resolved in version 0.4.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

@ghost ghost added the released label Oct 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants