Currently published version isn't compatible with the latest chai

[chaijs]

Currently published version isn't compatible with the latest chai

[keithamus]

Not yet. I'll get some time tonight to make sure you can publish by making git tags.

[keithamus]

Okay, sorry everyone for taking forever with this. I have opened #33 which fixes it 😅

[keithamus]

Aaand 1.3.0 is out! https://www.npmjs.com/package/chai-json-schema

[kevinroisin]

Interested in this as well.

[keithamus]

I just need to find the time to sit down and generate a token, sadly not something someone else can do. It's in my todo list, but gets pushed aside for other things including personal life, sadly.

[JrSchild]

Working on it. Will publish v 1.3.0 soon

[keithamus]

It looks as though - in the move to the chaijs org - this repo lost travis integration. I'm working on it to get it published right now.

[JrSchild]

Yes, it is already in master, I'll see if we can do a publish soon. @keithamus Is everything in place for us to push to npm?
For now you could use the latest ref in master in your package.json.

[evansiroky]

Any updates on publishing to npm?

[keithamus]

Sorry I didn't get round to this yet. Thanks for reminding me @evansiroky. I'll try to get some done on this tonight if I can.

[basharh]

Any update on this?

[honzajavorek]

Bump. David DM punishes me with red badge for having chai pinned on an ancient version 😞

[JrSchild]

@keithamus?

[keithamus]

Yeah sorry, this keeps falling off the bottom of my todo list. I will make sure to do something very soon.

[honzajavorek]

If there's still some work needed before release and it's not exclusively maintainer's work, write down what needs to be done and let us contribute it :)

If it's just about the burden of releasing, you could try https://github.com/semantic-release/semantic-release to simplify and automate the process.

[janbiasi]

Any updates at this point?

[kevinroisin]

Thanks!

[honzajavorek]

This still isn't fixed. Merging #33 didn't publish a new version, because the package.json contains the old version number - there's no bump.