^ Not sure what’s going on here, but the release s...
# pact-js-development
t
^ Not sure what’s going on here, but the release seems corrupt
y
Hey hey, I raised an issue for it here https://github.com/pact-foundation/pact-js-core/issues/456
it’s fine in draft, but when it gets converted to a published release, it’s missing the new lines, and not marking as latest
will sort 🙂
t
I recommend release-please if you’re reworking the pipeline
y
I’m only doing the minimal to provide the new lines and marking as latest, I didn’t want to change up the release pipeline too much from its original good state you put it in. Happy for you to raise a ticket to track for updating to release-please. I am off in the land of go, python and php at the moment.
❤️ 1
t
I don’t think it needs a ticket, it’s just if you’re implementing changes to the pipeline it’s a nice option as it does many of the things I had to build
y
unless its a drop in replacement, I’d have to go read docs, and it exceeds the scope of ensuring we have some new lines and mark it as latest, so I would want something to track it. I’d want to test it out e2e on my own fork, so I personally, if your asking me to do it while I’m there, I’d want a ticket.
If you want to do it, sans ticket, gopher it
I’ve already implemented the big raft changes to the pipeline in the prebuild pr, but had a couple of minor snags
t
No thanks