-
Notifications
You must be signed in to change notification settings - Fork 30
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
Release 0.10.0 #304
Release 0.10.0 #304
Conversation
I think just completing the PR. If I recall correctly, that automation looks at the project file and publishes a NuGet package if the value of the |
First we need to push a tag, then. I can do it during the weekend. |
I think this automated process also creates a tag that matches the value of the new |
brandedoutcast/publish-nuget, which we use, will automatically make the tag. We didn't flick the |
(lol, beat you by five seconds!) |
Looks like it worked 👍 https://www.nuget.org/packages/Hedgehog/0.10.0 |
Also the tag was created 👍 @adam-becker, I had to create the release manually (from the tag). Also, I need to edit the release so it has some release notes inside. I'll get back to this during the weekend. |
@moodmosaic I generated the new documentation pages as well. If a tag were pushed as part of the release we could automate the documentation generation part, the only input to the script is the version number. |
@adam-becker, yes, I'm all in for including more stuff in the release pipeline, so there's less manual steps to be done afterwards. It's not like we're releasing everyday, so even if the stuff we add makes the CI build slow(er) I think it's okay. |
I've now just edited the v0.10.0 release notes (as per the CHANGELOG.md) https://github.com/hedgehogqa/fsharp-hedgehog/releases/tag/v0.10.0 |
v0.9.0...0bbc3fd
fixes #280
/cc @adam-becker @TysonMN @dharmaturtle @ThisFunctionalTom @cmeeren
🎉