-
Notifications
You must be signed in to change notification settings - Fork 40
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
Preset's header
option not being passed through?
#33
Comments
Assuming you're using the latest version of the plugin? Please use |
Hi @webpro. I am running version 14.11.6 of release-it and version 3.3.0 of the plugin (the latest). Thanks for the debug command line. I found some interesting stuff, in that it does appear that the plugin is receiving and passing the option along. First, here's where it picks up the config:
Later, it still has that
But the generated changelog still doesn't have the header prepended to it:
|
I have the same problem. This plug-in just inserts the changlog produced by the conventional-changelog into the file. For example, after setting the header configuration and taking effect, the effect obtained is not ideal. like this:
You can see me here for details: #18 |
This is now fixed, right? With a single page header as documented. |
Hi @webpro. I'm still experiencing this problem, with the current version 5.1.0 of this plugin (and version 15.4.1 of release-it). I've tried setting Update: Yes, this is working for me as documented; thanks! |
Thanks for this helpful plugin :-). I think I've set the
header
option for the preset in the correct place, but no (<h1>
) header is written to the changelog file. This happens regardless of whether this is the first release (with no changelog already) or whether there has already been a release.The text was updated successfully, but these errors were encountered: