When exactly is publishCmd run?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, shell
- Domain
- release
Research direction
Start by tracing when publishCmd runs relative to the package.json version update and release commit, using the issue's semantic-release exec workflow as the scope. Confirm whether npmPublish=false changes that ordering, then document the supported timing and whether the requested Android and iOS version update can be included in the release commit.
Written by the indexing model from the issue text.
Description
I would like to run a command that uses the newly updated package.json version and write it into a file that is added to git to be included as part of the release commit, is it possible to do so with exec?
My use case is that I'm building a hybrid app where semantic-release would bump the package.json version, I would then like to use the new package.json version to update the native android & ios versions based on that and push that to git as part of the release commit, is that something I can accomplish with exec, or do I manually need to trigger my script after release as a separate commit?
I tried setting that as part of the publishCmd but it didn't work, it seems to be run either too early before the new package.json version is set or too late after the commit has already been made
PS: npmPublish is set to false
- Dominant language
- JavaScript
- Stars
- 164
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from semantic-release/exec
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
semantic-release/exec#535 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
semantic-release/exec#480 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
semantic-release/exec#459 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
semantic-release/exec#413 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
semantic-release/exec#412 · 1 comment ·
All issues in semantic-release/exec
Similar issues
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
DavidAnson/markdownlint-cli2#940 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100