v1.13.0-0 does not contain the change from changelog about container-healthchecks HOT 11 CLOSED

During the build the tag v1.13.0 is checked out, so it should be there.

Not sure why it isn't.. I'll look into doing a v1.13.0-1 to see if it is in there.

from container-healthchecks.

i have try with latest and same result :/

from container-healthchecks.

@BobCashStory Could you check if the image tag v1.13.0-1 includes the change from healthchecks/healthchecks v1.13.0?

from container-healthchecks.

Still same in my side

from container-healthchecks.

@BobCashStory Then I can't really do anything for you here.
The image is checking out the v1.13.0 tag during build so..

Is that a toggle-able option or something that needs specific setup?

from container-healthchecks.

@galexrt no it's in the changelog, weird :/

from container-healthchecks.

@BobCashStory I have pushed a new version with healthchecks v1.14.0 release.

Could you check that Docker image, tag is v1.14.0-0. Should be built in the next 20-40 minutes.

from container-healthchecks.

Did it, nothing change, i'm sorry i don't understand it you wanna see it health.cashstory.com

from container-healthchecks.

@galexrt lol i just dicover you changed all env vars there .... 3e76392 now i understand why nothing work well on my side

from container-healthchecks.

@BobCashStory Ah sorry, I thought I created a GitHub release, especially mentioning that change. Healthchecks projects reads from env vars in its settings.py / config file since 1-2 releases ago.

So I removed my custom logic for configuring the local_settings.py file to make it less error prone.

from container-healthchecks.

Yep it look to work now ! Thanks

from container-healthchecks.