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

Release 0.10.0 #304

Merged
merged 1 commit into from
Feb 6, 2021
Merged

Release 0.10.0 #304

merged 1 commit into from
Feb 6, 2021

Conversation

moodmosaic
Copy link
Member

@moodmosaic moodmosaic commented Feb 5, 2021

CHANGELOG.md Show resolved Hide resolved
CHANGELOG.md Show resolved Hide resolved
@moodmosaic
Copy link
Member Author

What's next @TysonMN (according to #215)? 👀

@TysonMN
Copy link
Member

TysonMN commented Feb 5, 2021

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 Version element has changed.

@moodmosaic
Copy link
Member Author

First we need to push a tag, then. I can do it during the weekend.

@TysonMN
Copy link
Member

TysonMN commented Feb 5, 2021

I think this automated process also creates a tag that matches the value of the new Version element.

@dharmaturtle
Copy link
Member

dharmaturtle commented Feb 5, 2021

brandedoutcast/publish-nuget, which we use, will automatically make the tag. We didn't flick the TAG_COMMIT and it's on by default. I believe the tag format is good.

@TysonMN
Copy link
Member

TysonMN commented Feb 5, 2021

(lol, beat you by five seconds!)

@ghost ghost added this to the 0.10.0 milestone Feb 5, 2021
@moodmosaic moodmosaic merged commit 5e98500 into hedgehogqa:master Feb 6, 2021
@moodmosaic
Copy link
Member Author

moodmosaic commented Feb 6, 2021

Looks like it worked 👍 https://www.nuget.org/packages/Hedgehog/0.10.0

@moodmosaic
Copy link
Member Author

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.

@ghost
Copy link

ghost commented Feb 6, 2021

@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.

@moodmosaic moodmosaic deleted the topic/release branch February 7, 2021 10:24
@moodmosaic
Copy link
Member Author

@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.

@moodmosaic
Copy link
Member Author

@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.

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

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

Successfully merging this pull request may close these issues.

Release 0.10.0
3 participants