Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Updating guide on `release:prepare` and `release:trigger`

See original GitHub issue

We normally don’t run release:trigger manually. What if we get rid of it?

Instead, we can guide them to add "release": "shipjs prepare" in their package.json. And for the CI services, they can trigger like the following:

yarn shipjs trigger
# or
npx shipjs trigger

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:5 (5 by maintainers)

Top GitHub Comments

2reactions

eunjae-leecommented, May 19, 2020

“yarn run prepare” doesn’t feel like I’m using a release tool.

Anyway this is not a big change but mostly the doc and some snippets in setup flow. So I’ll continue with release for now.

0reactions

tyankatsu0105commented, May 19, 2020

Umm… I can’t think too. How about "prepare": "shipjs prepare"?

Top Results From Across the Web

Maven Release plugin – Prepare a Release

Preparing a release goes through the following release phases by default: Check that there are no uncommitted changes in the sources; Check that ......

Maven release plugin – 8 tips & tricks - Five Agency

– Update POMs with release version; – Run all available tests; – Commit updated POMs to SCM; – Create new tag in SCM;...

Create a release trigger - Digital.ai Documentation

To see the triggers on a template, open a template or a release and select Triggers from the Show menu. Under Settings, Allow...

maven-release-plugin : How to better manage cascading ...

1) Release all projects in the level · 2) After all projects in the level are released, the next level's POMs should be...

Maven Release Plugin use in Jenkins Pipeline - Stack Overflow

Maven Release changes the version to 0.2.00-SNAPSHOT and commit; Jenkins Pipeline detect a change in GIT, so triggers a new build. You understood...