Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

outputPath not being used? #100

Closed
alexw10 opened this issue Jan 16, 2024 · 1 comment
Closed

outputPath not being used? #100

alexw10 opened this issue Jan 16, 2024 · 1 comment

Comments

@alexw10
Copy link

alexw10 commented Jan 16, 2024

Really want to know if I am doing something wrong here but specifying outputPath seems to not be being used?

In my libraries project.json specifying the following:

"semantic-release": {
      "executor": "@theunderscorer/nx-semantic-release:semantic-release",
      "options": {
        "github": false,
        "changelog": true,
        "npm": false,
        "tagFormat": "rhythm-v${VERSION}",
        "outputPath": "UI/dist/libs/rhythm"
      }
 }

But when this is ran it is showing this:

[4:44:46 PM] [semantic-release] [[Function: nx-semantic-release]] › ℹ  Write version 16.2.1 to package.json in /var/local/agent-manager/vsts-agent-3/_work/2/s/UI/libs/rhythm

I would have expected the above to be UI/dist/libs/rhythm right which is where this should be releasing from?
am I misunderstanding something?

@alexw10
Copy link
Author

alexw10 commented Jan 16, 2024

Figured it out was not using the proper outputPath and didnt know had to look at code to discover this.
Would be nice if it error'd out with outputPath not found or something

@alexw10 alexw10 closed this as completed Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant