Handling nextRelease version in semantic release











up vote
0
down vote

favorite












so I have been reading the docs and kind of got a glimpse of
what I should do, but no real grasp of how I can do it.



Here is my problem:
- I am using semantic release to publish my package to npm
- I also have contract testing in place with Pact.
- I would like my Pacts published after the release, if successful, with the same version as the new version



How can I do that easily?



I have looked at the docs, and understood that I could use the exec plugin, however, I find it not clear how I should configure semantic-release to behave exactly the same as now, only exposing the version as, at the very least, an env variable, and couldn't find examples of people doing that.



I could use hooks, but I am concerned that if a npm publish does not happen for some reasons, I would still get my pact published with the next version, which wouldn't exactly exist. Any suggestions here?



It seems I could also write my own JS script (see https://github.com/semantic-release/semantic-release/blob/3cc62f0318ff8917fcdc7cebe890da9dbaa7b3f9/docs/developer-guide/js-api.md) to do this as well as handling the version, but I am not certain what this example does and what it covers regarding the current behaviour.



I guess I could also write my own pact plugin too, but that's even more next level into having to understand how the internals of semantic-release work.



So I am after some examples/experience sharing, and maybe an easy-peasy solution to have that working in less than 30 minutes :)



Thanks



PS: sorry for posting here, but it seems the issues of semantic-release are not really made for support questions.










share|improve this question


























    up vote
    0
    down vote

    favorite












    so I have been reading the docs and kind of got a glimpse of
    what I should do, but no real grasp of how I can do it.



    Here is my problem:
    - I am using semantic release to publish my package to npm
    - I also have contract testing in place with Pact.
    - I would like my Pacts published after the release, if successful, with the same version as the new version



    How can I do that easily?



    I have looked at the docs, and understood that I could use the exec plugin, however, I find it not clear how I should configure semantic-release to behave exactly the same as now, only exposing the version as, at the very least, an env variable, and couldn't find examples of people doing that.



    I could use hooks, but I am concerned that if a npm publish does not happen for some reasons, I would still get my pact published with the next version, which wouldn't exactly exist. Any suggestions here?



    It seems I could also write my own JS script (see https://github.com/semantic-release/semantic-release/blob/3cc62f0318ff8917fcdc7cebe890da9dbaa7b3f9/docs/developer-guide/js-api.md) to do this as well as handling the version, but I am not certain what this example does and what it covers regarding the current behaviour.



    I guess I could also write my own pact plugin too, but that's even more next level into having to understand how the internals of semantic-release work.



    So I am after some examples/experience sharing, and maybe an easy-peasy solution to have that working in less than 30 minutes :)



    Thanks



    PS: sorry for posting here, but it seems the issues of semantic-release are not really made for support questions.










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      so I have been reading the docs and kind of got a glimpse of
      what I should do, but no real grasp of how I can do it.



      Here is my problem:
      - I am using semantic release to publish my package to npm
      - I also have contract testing in place with Pact.
      - I would like my Pacts published after the release, if successful, with the same version as the new version



      How can I do that easily?



      I have looked at the docs, and understood that I could use the exec plugin, however, I find it not clear how I should configure semantic-release to behave exactly the same as now, only exposing the version as, at the very least, an env variable, and couldn't find examples of people doing that.



      I could use hooks, but I am concerned that if a npm publish does not happen for some reasons, I would still get my pact published with the next version, which wouldn't exactly exist. Any suggestions here?



      It seems I could also write my own JS script (see https://github.com/semantic-release/semantic-release/blob/3cc62f0318ff8917fcdc7cebe890da9dbaa7b3f9/docs/developer-guide/js-api.md) to do this as well as handling the version, but I am not certain what this example does and what it covers regarding the current behaviour.



      I guess I could also write my own pact plugin too, but that's even more next level into having to understand how the internals of semantic-release work.



      So I am after some examples/experience sharing, and maybe an easy-peasy solution to have that working in less than 30 minutes :)



      Thanks



      PS: sorry for posting here, but it seems the issues of semantic-release are not really made for support questions.










      share|improve this question













      so I have been reading the docs and kind of got a glimpse of
      what I should do, but no real grasp of how I can do it.



      Here is my problem:
      - I am using semantic release to publish my package to npm
      - I also have contract testing in place with Pact.
      - I would like my Pacts published after the release, if successful, with the same version as the new version



      How can I do that easily?



      I have looked at the docs, and understood that I could use the exec plugin, however, I find it not clear how I should configure semantic-release to behave exactly the same as now, only exposing the version as, at the very least, an env variable, and couldn't find examples of people doing that.



      I could use hooks, but I am concerned that if a npm publish does not happen for some reasons, I would still get my pact published with the next version, which wouldn't exactly exist. Any suggestions here?



      It seems I could also write my own JS script (see https://github.com/semantic-release/semantic-release/blob/3cc62f0318ff8917fcdc7cebe890da9dbaa7b3f9/docs/developer-guide/js-api.md) to do this as well as handling the version, but I am not certain what this example does and what it covers regarding the current behaviour.



      I guess I could also write my own pact plugin too, but that's even more next level into having to understand how the internals of semantic-release work.



      So I am after some examples/experience sharing, and maybe an easy-peasy solution to have that working in less than 30 minutes :)



      Thanks



      PS: sorry for posting here, but it seems the issues of semantic-release are not really made for support questions.







      pact semantic-release






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked yesterday









      Moustachiste

      887




      887





























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53417010%2fhandling-nextrelease-version-in-semantic-release%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53417010%2fhandling-nextrelease-version-in-semantic-release%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown