You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are about to use release-plan on one of our first internal repositories, publishing to our internal registry. So far so good.
Now, for some packages they also need to be pushed to app stores. With the rule of "when package x version number is bumped, we also wanna push that one to the stores". After looking into what create-release-plan-setup offered and explanations from Preston, we can do this functionality in plan-release.yml.
To encode the rule of "when package x version number is bumped", is actually after release-plan prepare is run to check .release-plan.json and see if package x is part of solution object.
It would be more enjoyable to add a hook into package.json of bespoken package. Something as:
plus Preston also mentioned some of the npm hooks that are also triggered (which are always more favorable to use, imho).
What about documentation for npm hooks that are triggered (by which command) plus custom hooks for release-plan to cover for situations where npm hooks aren't available?
The text was updated successfully, but these errors were encountered:
We are about to use
release-plan
on one of our first internal repositories, publishing to our internal registry. So far so good.Now, for some packages they also need to be pushed to app stores. With the rule of "when package x version number is bumped, we also wanna push that one to the stores". After looking into what
create-release-plan-setup
offered and explanations from Preston, we can do this functionality inplan-release.yml
.To encode the rule of "when package x version number is bumped", is actually after
release-plan prepare
is run to check.release-plan.json
and see if package x is part ofsolution
object.It would be more enjoyable to add a hook into
package.json
of bespoken package. Something as:plus Preston also mentioned some of the npm hooks that are also triggered (which are always more favorable to use, imho).
What about documentation for npm hooks that are triggered (by which command) plus custom hooks for release-plan to cover for situations where npm hooks aren't available?
The text was updated successfully, but these errors were encountered: