- Notifications
You must be signed in to change notification settings - Fork1.8k
feat: capture output of prepare plugin#3389
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
feat: capture output of prepare plugin#3389
Uh oh!
There was an error while loading.Please reload this page.
Conversation
could you expand on your use case? we've never had a request for this before, so i'm pretty hesitant to accept a change like this for a limited use case. understanding your goal might help us consider alternatives |
Understandable! My use case is that I would like to have a deep link to my published package in my github release notes. For example, lets say the npm plugin deploys a package to the registryhere, I would like to deep link to this in the changelog. I'm sure there is a better way, but right now im thinking if the prepare part of the plugin (an unoffical custom plugin) can set the UUID of the release version, I could tie into that to build the deep link |
Uh oh!
There was an error while loading.Please reload this page.
I would like a way to generate additional notes in my plugin that utilizes the prepare stage.
This way I can update my github plugin config like the following:
releaseNameTemplate:"<%= nextRelease.name %> (<%= nextRelease.prepareOutput.subscriberPackageVersionId %>)"if there is a different way I can tie into that I would appreciate knowing how. I have attempted to mutate the context but it seems that the context is not a global reference one it reaches the plugin.