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

Version 0.17.1 #685

Merged
merged 4 commits into from
May 17, 2023
Merged

Version 0.17.1 #685

merged 4 commits into from
May 17, 2023

Conversation

Pliner
Copy link
Contributor

@Pliner Pliner commented May 16, 2023

Hi @tomchristie,

It is a PR for a new release, based on #661 and #640 as examples.

I am not sure whether any checklist is needed: 1) #669, #678 and #679 have already been merged 2) The date has been filled in.

Also, I am not able to create a draft of GH release, but I hope it is not a problem.

@Pliner Pliner marked this pull request as ready for review May 16, 2023 21:58
@tomchristie
Copy link
Member

Great, thanks!

The bullet points here are describing implementation changes, rather than the (user-facing) behaviour.
First up, let's see how we can describe each of those 3 changes properly...

(What do you think?)

This also prompts a suggested procedure improvement... we should start ensuring that pull requests update the release notes.
That will ensure that PR authorship is driven by describing behavioural changes rather than implementation changes, and will make the release process easier.

@tomchristie
Copy link
Member

I think we should also pull in #680, resolving #670 into this release.

How do we describe this? "Fix edge-case exception when removing requests from the connection pool." perhaps? It's not great, but it'd probably do.

@tomchristie
Copy link
Member

Okay, here's a release draft based on your CHANGELOG here...

https://github.com/encode/httpcore/releases/tag/untagged-b7d3a9dd34c002f475be

Does this all look correct?

@Pliner
Copy link
Contributor Author

Pliner commented May 17, 2023

@tomchristie Thanks for your suggestions regarding changelog. Unfortunately, I cannot access https://github.com/encode/httpcore/releases/tag/untagged-b7d3a9dd34c002f475be, probably it is accessible only for maintainers.

PS Sorry for the delayed reply, I prepared a reply right after my last commit, but forgot to press comment button 😞

CHANGELOG.md Outdated Show resolved Hide resolved
@tomchristie
Copy link
Member

Looks good, let's go on this.

(Also, I've sent you an invite to @encode/maintainers which you're welcome to either accept or decline.)

@tomchristie tomchristie merged commit bfe97bc into encode:master May 17, 2023
@Pliner
Copy link
Contributor Author

Pliner commented May 17, 2023

Looks good, let's go on this.

(Also, I've sent you an invite to @encode/maintainers which you're welcome to either accept or decline.)

Cool, thanks!

@Pliner Pliner deleted the release-0.17.1 branch May 17, 2023 13:06
@Pliner
Copy link
Contributor Author

Pliner commented May 17, 2023

@tomchristie Just to double check: could I publish https://github.com/encode/httpcore/releases/tag/untagged-b7d3a9dd34c002f475be (it looks like now I have enough permissions for this), or are you going to do it by yourself later on?

I looked at it, and it looks good.

@tomchristie
Copy link
Member

@Pliner so... let's also get #688 added in.

Once that's done, we can talk through publishing the release.
(The more folks who get to work through the process, the better.)

@Pliner
Copy link
Contributor Author

Pliner commented May 17, 2023

@Pliner so... let's also get #688 added in.

Once that's done, we can talk through publishing the release. (The more folks who get to work through the process, the better.)

I've added #688 to https://github.com/encode/httpcore/releases/tag/untagged-4c24a8601913f6ed346b

@tomchristie
Copy link
Member

tomchristie commented May 17, 2023

Okay, you're welcome to hit "publish" on the release if you'd like.

I'll show how the workflow proceeds after that.

@Pliner
Copy link
Contributor Author

Pliner commented May 17, 2023

Okay, you're welcome to hit "publish" on the release if you'd like.

I'll show how the workflow proceeds after that.

Thanks, done!

@tomchristie
Copy link
Member

Great, so...

Our publish workflow: https://github.com/encode/httpcore/actions/runs/5005203672

Has initiated this action: https://github.com/encode/httpcore/actions/runs/5005203672

Once someone from the @encode/operations team approves that action (which I've just done), the action runs, and should deploy the release to PyPI.

We should probably create an issue for a docs page or repository markdown document describing the contribution and release processes.

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.

2 participants