getting version during preversion step
I am using a package called babel-plugin-inline-package-json to pull out my version number during my build step. Currently using semantic-release the package version is always 0.0.0 instead of the correct version number. I setup semantic-release to trigger a build using the npm preversion command. I was under the impression that by the time semantic-release triggered preversion it would already have the new version inserted into the package.json, but I keep getting 0.0.0 instead. What would be the correct way to pull out the version number so I can get it during my build step?
semantic-release
asked Nov 20 at 20:40
Mike F
82216
add a comment |
I am using a package called babel-plugin-inline-package-json to pull out my version number during my build step. Currently using semantic-release the package version is always 0.0.0 instead of the correct version number. I setup semantic-release to trigger a build using the npm preversion command. I was under the impression that by the time semantic-release triggered preversion it would already have the new version inserted into the package.json, but I keep getting 0.0.0 instead. What would be the correct way to pull out the version number so I can get it during my build step?
semantic-release
asked Nov 20 at 20:40
Mike F
82216
for what it's worth, you can find something describing your situation there: github.com/semantic-release/semantic-release/blob/caribou/docs/…. I however am looking at how to implement that in my flow, and it's hard to find examples I find.
– Moustachiste
Nov 21 at 16:18
add a comment |
I am using a package called babel-plugin-inline-package-json to pull out my version number during my build step. Currently using semantic-release the package version is always 0.0.0 instead of the correct version number. I setup semantic-release to trigger a build using the npm preversion command. I was under the impression that by the time semantic-release triggered preversion it would already have the new version inserted into the package.json, but I keep getting 0.0.0 instead. What would be the correct way to pull out the version number so I can get it during my build step?
semantic-release
asked Nov 20 at 20:40
Mike F
82216
I am using a package called babel-plugin-inline-package-json to pull out my version number during my build step. Currently using semantic-release the package version is always 0.0.0 instead of the correct version number. I setup semantic-release to trigger a build using the npm preversion command. I was under the impression that by the time semantic-release triggered preversion it would already have the new version inserted into the package.json, but I keep getting 0.0.0 instead. What would be the correct way to pull out the version number so I can get it during my build step?
semantic-release
semantic-release
asked Nov 20 at 20:40
Mike F
82216
asked Nov 20 at 20:40
Mike F
82216
asked Nov 20 at 20:40
Mike F
82216
asked Nov 20 at 20:40
Mike F
82216
asked Nov 20 at 20:40
Mike F
82216
82216
for what it's worth, you can find something describing your situation there: github.com/semantic-release/semantic-release/blob/caribou/docs/…. I however am looking at how to implement that in my flow, and it's hard to find examples I find.
– Moustachiste
Nov 21 at 16:18
add a comment |
for what it's worth, you can find something describing your situation there: github.com/semantic-release/semantic-release/blob/caribou/docs/…. I however am looking at how to implement that in my flow, and it's hard to find examples I find.
– Moustachiste
Nov 21 at 16:18
for what it's worth, you can find something describing your situation there: github.com/semantic-release/semantic-release/blob/caribou/docs/…. I however am looking at how to implement that in my flow, and it's hard to find examples I find.
– Moustachiste
Nov 21 at 16:18
for what it's worth, you can find something describing your situation there: github.com/semantic-release/semantic-release/blob/caribou/docs/…. I however am looking at how to implement that in my flow, and it's hard to find examples I find.
– Moustachiste
Nov 21 at 16:18
add a comment |
1 Answer
1
active
oldest
votes
semantic-release doesn't trigger the npm preversion directly, it runs npm version then npm publish. The npm hook scripts (preversion, postversion, prepack, postpack, prepublish, prepublishOnly, postpublish, prepare) are triggered by npm itself.
As suggested by it's name the hook preversion run just before the version is updated. You need to use the postversion hook which run after the version is updated.
For more details see: How can I use a npm build script that requires the package.json’s version ?
answered Nov 24 at 19:39
Pierre Vanduynslager
11114
add a comment |
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',
autoActivateHeartbeat: false,
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401162%2fgetting-version-during-preversion-step%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
semantic-release doesn't trigger the npm preversion directly, it runs npm version then npm publish. The npm hook scripts (preversion, postversion, prepack, postpack, prepublish, prepublishOnly, postpublish, prepare) are triggered by npm itself.
As suggested by it's name the hook preversion run just before the version is updated. You need to use the postversion hook which run after the version is updated.
For more details see: How can I use a npm build script that requires the package.json’s version ?
answered Nov 24 at 19:39
Pierre Vanduynslager
11114
add a comment |
semantic-release doesn't trigger the npm preversion directly, it runs npm version then npm publish. The npm hook scripts (preversion, postversion, prepack, postpack, prepublish, prepublishOnly, postpublish, prepare) are triggered by npm itself.
As suggested by it's name the hook preversion run just before the version is updated. You need to use the postversion hook which run after the version is updated.
For more details see: How can I use a npm build script that requires the package.json’s version ?
answered Nov 24 at 19:39
Pierre Vanduynslager
11114
add a comment |
semantic-release doesn't trigger the npm preversion directly, it runs npm version then npm publish. The npm hook scripts (preversion, postversion, prepack, postpack, prepublish, prepublishOnly, postpublish, prepare) are triggered by npm itself.
As suggested by it's name the hook preversion run just before the version is updated. You need to use the postversion hook which run after the version is updated.
For more details see: How can I use a npm build script that requires the package.json’s version ?
answered Nov 24 at 19:39
Pierre Vanduynslager
11114
semantic-release doesn't trigger the npm preversion directly, it runs npm version then npm publish. The npm hook scripts (preversion, postversion, prepack, postpack, prepublish, prepublishOnly, postpublish, prepare) are triggered by npm itself.
As suggested by it's name the hook preversion run just before the version is updated. You need to use the postversion hook which run after the version is updated.
For more details see: How can I use a npm build script that requires the package.json’s version ?
answered Nov 24 at 19:39
Pierre Vanduynslager
11114
answered Nov 24 at 19:39
Pierre Vanduynslager
11114
answered Nov 24 at 19:39
Pierre Vanduynslager
11114
answered Nov 24 at 19:39
Pierre Vanduynslager
11114
11114
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401162%2fgetting-version-during-preversion-step%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
for what it's worth, you can find something describing your situation there: github.com/semantic-release/semantic-release/blob/caribou/docs/…. I however am looking at how to implement that in my flow, and it's hard to find examples I find.
– Moustachiste
Nov 21 at 16:18