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

Question: rc version release #87

Closed
danpacho opened this issue Apr 24, 2023 · 2 comments
Closed

Question: rc version release #87

danpacho opened this issue Apr 24, 2023 · 2 comments
Labels
question Further information is requested

Comments

@danpacho
Copy link

What if publishing package with this action for rc version, like version: "1.0.0-rc.0"?

Expected behavior is that npm publish --tag rc script is automatically adapted, because rc tag is included in version string.

And after automatically publishing process via this action, package can then be installed with the following command
npm install my-package@rc

@mcous mcous added the question Further information is requested label Apr 24, 2023
@mcous
Copy link
Member

mcous commented Apr 24, 2023

I would prefer this module to be a pretty thin wrapper around vanilla npm behavior, so I'm not interesting in doing anything clever with parsing the version string at this time.

This action will fall back to the publishConfig field in package.json, so if you're interested in using this action to publish pre-release versions to a non-latest tag in some automated fashion, I recommend you use that functionality.

For example:

{
  "name": "my-cool-package",
  "version": "1.0.0-rc.0",
  "publishConfig": {
    "tag": "rc"
  }
}

@mcous mcous closed this as not planned Won't fix, can't repro, duplicate, stale Apr 24, 2023
@danpacho
Copy link
Author

Thanks! 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants